Customer & partner portals
Giving customers the answer without a phone call
Most support volume is people asking for information you already hold. A portal is worth building when the questions are predictable and the answers are already in a system.
In short
A customer portal earns its cost when a predictable, repeated question can be answered from data already held in a system. Order status, invoice history, delivery documents, account balances, service tickets. It is a poor investment when the questions vary too much to anticipate, when the underlying data is not reliable enough to expose, or when the real problem is that the answer itself is bad — a portal showing a customer that their order is three weeks late does not fix the lateness.
When it applies
Signals this is the work
If more than one of these is true today, the problem is usually further along than it looks from the outside.
Support answers the same question all day
"Where is my order", "send me that invoice", "what is my balance" — all answerable from existing data.
Documents are emailed on request
Someone finds a PDF and attaches it, repeatedly, for information the customer could retrieve.
Partners cannot see their own pipeline
Resellers or distributors phone in for stock, pricing or order status.
Enquiries arrive out of hours
Volume exists outside your opening hours and waits until morning.
Account managers do data entry
Senior people spend their time on retrieval that a login would handle.
How we do it
The sequence
- 01
Count the questions first
What is actually asked, how often, and whether the answer exists in a system today. That is the business case, and sometimes it says no.
- 02
Check the data is fit to show
Exposing data to customers raises the standard. Inconsistencies that were tolerable internally become support tickets.
- 03
Design access properly
Who sees what, how accounts are created and revoked, and what happens when someone leaves the customer. Retrofitting authorization is expensive.
- 04
Start with the highest-volume question
One thing done well beats a portal with eleven half-features nobody uses.
- 05
Keep one authoritative source
The portal reads from the system of record. It does not become a second place where truth lives.
- 06
Measure deflection honestly
Whether contact volume actually fell. If it did not, the portal answered a question nobody was asking.
What we will not do
The refusals
- Build a portal to hide a process problem the customer is right to complain about.
- Expose data that is not accurate enough to survive being looked at.
- Duplicate the system of record inside the portal.
- Ship self-service with no path to a human.
Questions
Before you ask
Tell us what isn't working.
One process, one system, one decision you are stuck on. We will come back with how we would approach it, what it would take, and whether it needs building at all.