By Artem Korsakov ·
Clients rarely benefit from labels like "Stage 4.2." They need to understand whether the request has been accepted, whether documents are approved, and who should respond next. A client dashboard must answer these questions and display the information relevant to them.
Which order statuses does the client see?
For a hypothetical design service, you might display "Request Accepted," "Details Under Review," "In Progress," "Awaiting Your Decision," and "Ready." The names depend on the actual workflow. If a service does not involve delivery, there is no need to add a shipping stage merely for the sake of a familiar template.
Each status requires an explanation and an actionable step. For example, "Awaiting Your Decision" should be accompanied by the current file and the ability to leave a comment. If an employee's response is required to proceed, the screen must not imply that delays depend on the client.
A deadline is shown only when the company monitors its relevance. If an agreement has changed, the previous date remains in the history, and a new one appears with a note.
Подпись: Illustrative example for a design service. Several internal stages are combined into one client-friendly status. Procurement from a contractor remains internal and is not displayed in the dashboard.
What else to place near the status?
The composition of a small card might include:
- Order or ticket number and name;
- Current stage with a brief explanation;
- Date of the last update;
- Next step and its responsible party;
- Current documents;
- Method to ask a question about this work.
Internal notes, financial terms with contractors, and internal assessments should not automatically appear to the client. There must be a separate list of public fields, agreed upon with the process owner.
If there are multiple versions of a document, it is important to highlight the current one and preserve the context of previous decisions. A downloaded old file must not silently replace a new approval.
Where does the update come from?
The first version can be managed manually: an employee changes the client status in their interface. This is a viable option if the responsible person is assigned and the team can handle the volume of requests.
When connecting a CRM, you must describe the mapping of stages. One internal status may carry several different meanings for the client. Sometimes, multiple CRM stages are combined into one clear external stage.
In case of an exchange error, the dashboard must display saved information and the update time. Connection to the system should be tested separately: simply having a similar screen in a demo does not mean synchronization is working.
How to verify access?
Create two test clients and several orders. Each should see only records related to them and permitted files. Verify direct links to the card and document after logging out of the account.
If a client company includes multiple employees, decide in advance who sees all their orders. Inviting a new colleague and revoking access for a former employee require a clear procedure agreed upon by the owner. These issues are discussed in detail in the article on roles and access.
AI helps explain the status if facts are already collected.
The dashboard can offer an employee a draft response to the client's question "Why has the deadline shifted?" The assistant receives only permitted events for this order: approved dates, approval requests, and published comments. The output is a short explanation with links to these events. A manager checks it before publishing.
If there is no reason for the delay in the history, the response must state that the reason is being clarified. The phrase "delay due to supplier" is not acceptable simply because it sounds plausible. Internal correspondence, purchase prices, and other clients' orders are not included in this scenario.
Подпись: Illustrative example. AI sees only published events for this order. The manager checks the response before publication.
For searching through permitted materials, there are ready-made tools, such as File Search in Yandex AI Studio (a Russian cloud AI platform). Client segmentation and the list of available information are designed separately.
Acceptance example.
Take two hypothetical orders: one awaits a client's decision, the other is ready for delivery. For the first, the client sees an active file and a reply button; for the second, they see an agreed delivery method. Then, the employee changes the source data: the dashboard must show a new update date and the correct next step.
Now, disable the exchange. The screen retains the last received information with a note on its relevance; the promise of "real-time data" is not displayed. After restoration, changes arrive without a repeated request from the client.
Separately verify that an invited employee of the client sees only permitted orders, and revoked access no longer works. For the first version, a status, a document, and one client action are sufficient. Communication history, payments, and complex holding structures increase the volume and require independent testing.
How to measure usefulness?
Track questions about the workflow and actions a client was able to perform in the dashboard. Logging into the dashboard does not mean the task is resolved. Look at whether the person found the current file and understood the next step.
If information in the dashboard is updated with a delay, the client will continue to write to the manager. In this case, fix the update process first, then add new features.
View an example of a client dashboard. In trike_dev, you can evaluate a separate status screen with the necessary roles and data source. General budget factors are provided in the article on dashboard cost.
Related reading: Data Exchange Between Systems: How Not to Lose Requests During Failures; Automation Support: What is Needed After Launch.
Частые вопросы ### Is integration needed in the first version?
Not always. Manual updates may be suitable for testing scenarios. The volume and responsible person must be agreed upon in advance.
Can status be viewed without registration?
This is a separate access scenario. It is necessary to determine what information is available via the link and how documents are protected. This option cannot be automatically assumed to be suitable for all orders.