Give customers a useful place to manage their requests.

Repeated status questions often mean customers cannot see what they need. VT LAB builds customer portals around an agreed self-service journey: finding their information, supplying a document or following a request. Each action needs a defined owner and a meaningful outcome for the customer.

A clear self-service task

Access matched to each customer

Visible request status and next steps

Choose what customers can do

Begin with one recurring interaction that can be completed through the portal. Show the information needed to act, explain required documents and distinguish a saved draft from a submitted request. Status labels should reflect the actual service process rather than imply that work has been completed.

Keep records within their access boundaries

Define who can see, create and change each record, including customers with multiple contacts. Account access and data ownership shape the product. Connections to existing systems depend on available interfaces and permissions; a portal should not expose another customer’s information or create competing records.

Start with a real customer request

Bring the current conversation, documents involved, service stages and staff responsible for follow-up. We map the customer and staff steps, then verify the journey and access rules. Booking, payment or fulfilment functions are additional workflows whose business rules must be confirmed explicitly.

Give customers a useful place to manage their requests.

Choose what customers can do

Keep records within their access boundaries

Start with a real customer request

Which repeated question could become self-service?