A customer portal should help people complete tasks they otherwise need to contact your team about.
That could mean downloading a document, checking a request, updating information or approving the next stage of work.
The right feature list depends on your customers and the service you provide. A portal for an accounting practice has different requirements from one used by a wholesaler or a software provider.
Start with the customer’s task, then identify the information, permissions and staff workflow needed to support it.
Look at What Customers Already Ask For
Review recent enquiries before planning screens.
Look for repeated requests such as:
Group these by task and identify the systems your staff currently use to answer them.
This helps you assess whether a portal would make the process clearer or simply introduce another place to maintain information.
Choose a Starting Workflow
Avoid treating the portal as a place to display everything your business knows about a customer.
Select a workflow that customers need and your team can support.
Customers can see which onboarding documents are required, upload them and check whether staff have accepted them.
This gives the first scope a clear purpose.
The required features follow from that journey: account access, document requests, uploads, staff review and status information.
Our customer portal development service explains how these requirements can become a development scope.
1. Accounts and Appropriate Access
Customers need a way to access information intended for them.
Before choosing an account structure, answer:
A company account may need an administrator who manages colleagues. An individual customer account may not.
Permissions need to be enforced by the application handling the information. Hiding a link or button is insufficient.
2. A Clear Starting Screen
The opening screen should help customers understand what they can do next.
Depending on the service, it might show:
Each item should lead to an understandable action or explanation.
If the portal has little activity, provide a useful empty state. A customer should be able to tell whether there is nothing to do or whether information has failed to load.
3. Document Access and Uploads
Document handling can be useful when files are central to the service.
Plan the workflow around:
For example, “uploaded” and “accepted” mean different things.
A customer may need to know whether a file was received, whether it has been checked and whether another version is required.
Do not treat those stages as interchangeable.
4. Requests and Status Updates
Customers should understand what happens after submitting a request.
Useful information may include:
Define what each status means internally.
A “waiting” label is ambiguous unless it explains whether the customer, staff or another provider needs to act.
The staff workflow must support the status shown to customers. Otherwise, the portal may display information that is technically available but no longer accurate.
5. Profile and Account Changes
Decide which details customers can update themselves.
Some changes may be routine, while others affect billing, permissions or service delivery.
Questions include:
A visible confirmation should reflect what happened.
“Your change was saved” and “your change was submitted for approval” describe different outcomes.
6. Billing or Booking Information
Include these features when they support the customer’s main tasks.
Billing
Customers may need invoice access, payment status or a link to an approved payment workflow.
Establish which system maintains the financial record and how current the displayed information is.
Bookings
Customers may need to view appointments, request changes or cancel within defined rules.
Plan availability, approval, time zones and notifications.
An existing billing or booking platform may already provide suitable account features. Assess whether connecting to it would meet the need before rebuilding functionality.
Our API development and integration service covers connections between portals and existing systems.
7. Notifications and Preferences
Notifications can tell customers that something relevant has changed.
Choose events that justify interrupting them, such as:
Agree on channels, preferences and delivery responsibilities.
Keep important information accessible inside the portal where appropriate. A failed email should not make the underlying update impossible to find.
Also decide who investigates unsuccessful delivery.
8. Help and Human Support
Self-service will not resolve every situation.
Customers need a clear route to assistance when:
Explain how to contact the team and what response arrangement applies.
If a support form is used, decide whether it should attach the relevant request reference automatically so customers do not have to explain the same context again.
9. Mobile Usability and Accessibility
Customers may open the portal from a phone while completing another task.
Review the important journeys on appropriate devices and screen sizes.
Check:
Do not assume that a responsive layout alone makes every workflow usable.
Accessibility requirements and assessment methods should be part of the agreed scope.
10. Staff Tools Behind the Portal
A customer action often creates work for somebody inside the business.
Staff may need to:
Define these tasks alongside the customer experience.
For example, collecting documents is only part of the process. Someone needs to know what arrived, what requires review and what should happen next.
Decide Where Each Piece of Information Lives
A portal may display information from several systems.
Record the source for each important record:
| Information | Question to resolve |
|---|---|
| Customer details | Does the portal or CRM maintain the original? |
| Documents | Where are files stored and permissions managed? |
| Request status | Which team or system updates it? |
| Invoices | Which billing service provides the record? |
| Bookings | Which calendar or scheduling system controls availability? |
If two systems can change the same information, agree on how conflicts are handled.
Also define what customers see when a connection fails or the latest information is unavailable.
Choose Features With a Practical Matrix
The table below is an illustrative planning example.
| Feature | Include first when | Consider later when |
|---|---|---|
| Account access | FirstCustomers view restricted information | LaterThe first task is genuinely public |
| Document exchange | FirstDocuments drive the service | LaterFile exchange is uncommon |
| Request tracking | FirstStatus enquiries are frequent | LaterThere is no maintained status workflow |
| Billing information | FirstCustomers regularly need invoice access | LaterThe existing billing portal already meets the need |
| Booking changes | FirstScheduling is a core customer task | LaterBooking is outside the initial journey |
| Detailed reporting | FirstCustomers need it to make decisions | LaterIt adds little to the first task |
Use actual customer enquiries and staff workflows to make these decisions.
For a staged release, read our guide to prioritising MVP features.
Define What Success Looks Like
Choose observations related to the problem you are trying to improve.
Examples include:
Establish a starting point where possible and gather feedback after launch.
A lower number of emails is not automatically evidence of success. Customers may still be confused or unable to complete the process.
Prepare the Development Brief
Once you have selected the first workflow, document:
Our developer brief guide provides a structure you can use.
If a portal already exists, an application technical assessment can help establish what can be retained or improved.
Plan Ongoing Ownership
Before launch, agree who will manage users, maintain content and review submissions.
Technical maintenance, monitoring and further development also need an owner.
Our application maintenance service explains the support arrangements to discuss.
Discuss Your Customer Portal Requirements
DOT IT Services develops customer portals around defined customer tasks and staff workflows.
Tell us what customers regularly ask for, where the information is stored and which process you want to improve.
Written by DOT IT Services.