Stork Delivery
A customer portal should remove a phone call
Choose portal features by the work customers can complete themselves and the information your team can reliably keep current.
The problem: a portal can move customer uncertainty onto another screen
A customer portal should make an ordinary task easier. If customers still need to call for the meaning of a status, confirm whether a document arrived, or discover that the displayed information is out of date, the portal has moved the uncertainty onto another screen.
Begin with a question your team repeatedly answers and can answer reliably from the systems it runs.
A practical approach
Choose a useful first task
Examples include checking an order's progress, downloading an approved document, submitting a service request, or updating contact information through a controlled process.
Pick one with a clear business owner and a dependable source of data. A portal cannot provide a trustworthy order status if the underlying operation has no agreed meaning for that status.
Describe what the customer should be able to finish without assistance. That is a more useful requirement than a list of dashboard widgets.
Explain the status
Use language a customer can understand. An internal code such as “released” may mean something very specific to the warehouse and something entirely different to the buyer.
Show what has happened, what comes next, and whether the customer needs to do anything. Include freshness information when updates are delayed.
If the system cannot confirm a fact, present the uncertainty clearly and provide a route to help. A precise-looking timestamp does not compensate for an unclear process.
Build account boundaries carefully
Work out who can see which company, location, project, or order. Customers may have several contacts with different responsibilities, and one person may represent more than one account.
Test access using separate customer identities, including direct attempts to open another customer's records. Do not rely on hiding a link in the interface as the access control.
Plan for invitations, departures, and lost access. Those are ordinary parts of operating a business portal.
Measure the completed task
Track whether people reach the intended outcome and where they stop. Compare support questions before and after release, allowing for changes in volume and customer mix.
A fall in calls is not automatically success if customers have simply given up. Look at completion and unresolved requests together.
The best custom portals are extensions of a working business process. They give customers enough reliable information and control to complete a task, while giving staff a clear view of the cases that still need help.
The result: a customer task completed without avoidable assistance
Choose one common support question and observe customers attempting the corresponding portal task. Check completion, abandoned attempts, unresolved requests, and related calls together. Use a second account to verify that another customer's records stay inaccessible. The first release should make the selected task understandable and finishable, with a clear support route when the information needed to complete it is unavailable.