Skip to content
Internal toolsPublished on 2 min read

How to design a customer portal around cases and requests

Decide what customers can track themselves, when a notification helps and how to separate documents across organisations.

A workspace with a web application on multiple screens

In short

  • Review a week of calls and emails.
  • An internal code may not tell a customer what to do.
  • Check a customer with two organisations, a departed contact and a direct download URL.
  • Next steps

Find the recurring customer question

Review a week of calls and emails. Do people need a status, a document or a next action? Choose one complete workflow, such as uploading a document and seeing that it arrived.

Write statuses for the people reading them

An internal code may not tell a customer what to do. Give each visible status a clear meaning and next action. Send a notification when a change matters and retain the message so support sees the same information.

Test access boundaries

Check a customer with two organisations, a departed contact and a direct download URL. Invitations should expire and access should be revocable. Search, exports and files need the same organisation boundaries as the dashboard.

Next steps

Creagrid / actie

Practical checklist

  • Describe the problem and intended outcome.

  • Involve the people who use the process every day.

  • Test the riskiest assumption with a small prototype.

  • Define tests, ownership and maintenance up front.

From insight to software

A digital product that genuinely fits your organisation?

We bring process, users and technology together in one feasible product plan.Discuss your challenge
Book a call

Choose a time

Creagrid team member · 15 minutes on Microsoft Teams

Open the calendar on a separate page