Account and progress views
Show the relevant customer record, job stage or request history, with clear labels and a date where freshness matters.
CUSTOMER PORTAL DEVELOPMENT
Customer portals built around real tasks.
A customer portal gives people a private place to find information they return to regularly. We plan the account area around specific tasks, such as checking a job, finding a document or updating details.
WHEN IT FITS
Give the account a useful purpose.
A portal is worth considering when customers repeatedly ask for information already held by the business. For an occasional enquiry, a clear public page or email may be simpler. We agree which tasks need an account, where the underlying information lives and who keeps it current.
WHAT THIS CAN INCLUDE
Information matched to the customer.
Each feature and its access rules are defined in the project scope.
Private document access
Define who can upload, view and download each file, how access is withdrawn and which records must be retained.
Requests and updates
Let customers submit agreed details or requests, with validation, a receipt state and a clear route to staff help.
Team administration
Give authorised staff the controls they need to support accounts and maintain records, with changes tracked where required.
ACCESS & HANDOVER
Set the boundaries before the screens.
We agree account roles, record ownership, sign-in and recovery before building the main journeys. Testing needs to cover different customer accounts, staff permissions, expired access and mobile tasks. Sensitive information and retention requirements must be identified during scoping.
The handover defines account administration, support, hosting, data export and recovery responsibilities. Connections to existing systems depend on their supported interfaces. Explore business systems, our published project scopes, or the guide to when a portal is more useful than email.
COMMON QUESTIONS
Questions before adding a login.
Do we need to replace our current website?
Not necessarily. A portal can be a separate account area linked from the public website, subject to the existing platform and sign-in requirements.
Can customers see one another's records?
They should only access the records their role permits. The scope must define those rules, and verification must include attempts to access records belonging to other accounts before release.
Can it use information from our existing system?
Where that system offers a suitable interface and the necessary permissions. We agree which system owns each record and how delayed or failed updates are handled.
Does a portal include payments, messaging or e-signatures?
Only when specified. These features introduce their own providers, permissions and operating costs and are assessed separately from a document or progress portal.
LET'S TALK
What do customers keep asking for?
Describe the information or task you want them to access for themselves.