What a customer portal is, and when your business needs one

A customer portal lets each customer check, download, approve and pay for their own things. The signs you need one, and what the first version should do.

A customer portal is a private, logged-in part of your website where each customer sees and does their own things. They check an order or a job, download a document, approve a quote, pay an invoice, book a slot or update their details, without ringing or emailing your team. A business needs one when a steady share of its calls and emails are customers asking for information it already holds, and when that information sits in one system the portal can read from.

If you came here looking for a login page, you will need the website of the company you deal with. We are writing for the owner or operations lead of an established Irish business who is deciding whether to build a portal for their own customers.

What a portal is in plain terms

Think of the questions your office answers every day. Where is my order? Can you send me that certificate again? Has my booking gone through? Did you get my payment? Each one takes a member of staff away from other work to look something up and send it back.

A portal moves those lookups to the customer. They sign in, see their own records and act on them. Your team stops being the go-between for information the business already has.

The word "private" carries the weight here. A portal is different from a public page with a contact form. Each customer sees their own records and nobody else's, and that one fact shapes most of the decisions behind it.

The signs you need one

There is no single trigger. These patterns tend to show up together in businesses that are ready.

The same questions arrive every day

If your team could list the ten questions customers ask most, and most of them are "what is the status of" or "can you send me", a portal can answer them. Count them for a fortnight. The count is usually higher than anyone expected.

Documents go out by email, again and again

Invoices, certificates, reports, signed agreements and delivery notes get emailed, lost and requested again. A portal keeps them in one place for each customer, for as long as the business holds them.

Approvals wait on someone's inbox

Quotes, proofs and changes sit in an email thread until a customer replies. A portal gives the approval a button and a record of who approved what, and when.

Customers want to act outside office hours

Bookings, payments and changes to details come in at night and at weekends. A portal lets the customer do them then, and your team picks up anything that needs a person in the morning.

Your records are already in decent shape

This is the sign people skip. A portal shows customers what your systems hold. If job statuses are kept in a spreadsheet that one person updates on Fridays, the portal will show stale information and the calls will continue. Sometimes the right first project is the system behind the portal.

What the first version should do

A first version should do a small number of things completely. Pick the two or three requests that take up the most staff time, and make the portal handle them from start to finish.

For a service business that might be job status, documents and invoice payment. For a business that takes bookings, it might be booking, changes and reminders. The test is simple. After launch, a customer with one of those requests should never need to ring.

What the first version should not do

It should not try to copy every screen your staff use. Customers need a short, clear view of their own affairs; the internal system can stay as detailed as your team needs.

It should not ask customers to type in information you already hold. If they have to re-enter their address and account number to check an order, they will pick up the phone instead.

It should not launch half-connected. A portal that shows an order status but cannot show the delivery date teaches customers that the portal is unreliable, and that habit is hard to undo.

What it has to connect to

A portal is only as useful as the systems it reads from and writes to. Before anyone designs a screen, list where each piece of information lives today.

That usually means your CRM or customer records, your job or order system, your accounting software for invoices and payments, wherever documents are stored, and a payment provider if customers pay through the portal. Each connection needs a clear answer on which system is the source of truth. If a customer updates their phone number in the portal, it should change in your customer record too, so staff do not work from an old one.

This is also where most of the work sits. The screens are the visible part, and the connections behind them decide whether the portal saves your team time or creates a second set of records to keep in step.

Access and privacy

Getting access right is the part of a portal you cannot fix later. There are a few things that have to be true from the first day.

  1. Each customer sees only their own records. The check happens on the server for every request, so changing a number in the web address can never show someone else's order or invoice.
  2. Accounts match how your customers are organised. A company customer may need several people with different rights, such as one who approves and one who only views. A household may need one person acting for another.
  3. Staff sign in separately. Your team uses its own sign-in with its own permissions, kept apart from customer accounts, so a staff view is never one setting away from a customer view.
  4. Every important action is recorded. Approvals, payments and changes to details carry a record of who did what and when.
  5. Access ends when it should. People leave companies and relationships change, so there is a way to remove or hand over access cleanly.

Customer data in a portal is personal data, so the portal should collect only what it needs and keep it only as long as the business has a reason to.

A portal in use

In one youth sport coaching business, the customer is a parent and the record belongs to a child. You can read the full study on parent-managed coaching records.

We built records that bring the coaching information together (session records, attendance and assessments) under parent-managed accounts. Parents control the accounts for their children, and those accounts govern access to the coaching record. When the child reaches adulthood, the account transfers to them. Scheduled jobs handle messaging, and the records connect to subscription billing for each player.

The detail that matters for anyone planning a portal is the account boundary. Who can see a record, who acts on someone else's behalf, and what happens when that changes all had to be settled in the design, before the screens. The same questions apply to a company customer with several staff, or a family with one person managing the bookings.

A portal can also be narrower than a full account area. A customer might only need a secure link to review and sign a proposal, with a full record of what they agreed. Our study of proposals signed online with an audit trail covers that case.

That is how we approach every customer portal we build. We start with the requests your team handles every day and the systems that already hold the answers.

What to ask whoever builds your portal

These questions will show quickly whether a supplier has thought past the login screen.

  • Which of our current customer requests will the first version handle completely?
  • Which of our systems will it read from and write to, and which one is the source of truth for each piece of information?
  • How does the portal make sure each customer sees only their own records, and how will you test that?
  • How do staff sign in, and how are their permissions kept apart from customer accounts?
  • How do we add, change and remove people's access, including for company customers with several users?
  • What is recorded when a customer approves, pays or changes something?

If your team spends its days answering questions your systems could answer for themselves, you can start a project with us.

The studyCoaching records under parent-managed accounts, for a youth sport coaching business.

Coaching records, accounts and billing.

Coaching records, accounts and billing.Session records, attendance, assessments and parent consent feed a workspace record. Pseudonymised information supplies the plan draft. Scheduled jobs connect the workspace to messaging and per-player billing. Parents manage accounts, with transfer at adulthood.
Coaching records, accounts and billing.Session records, attendance, assessments and parent consent feed a workspace record. Pseudonymised information supplies the plan draft. Scheduled jobs connect the workspace to messaging and per-player billing. Parents manage accounts, with transfer at adulthood.
Key
The system in words

Session records, attendance, assessments and parent consent feed a workspace record. Pseudonymised information supplies the plan draft. Scheduled jobs connect the workspace to messaging and per-player billing. Parents manage accounts, with transfer at adulthood.

Coaching records, parent accounts and subscription billing, connected in one system.

When a player reaches adulthood, the account transfers to them.

Read the study

Your team spends its days answering questions your systems could answer.

Tell us what the business needs to do. We reply within two working days.