Show what is happening to the customer's case, using the right source.
When customers need to phone about every step, a focused status portal can make follow-up clearer. ImbaHub can develop a customer view connected to agreed case information in your business system. We start with what each status means, rather than a timeline that promises more than the organisation can confirm.
- Business source
The responsible process decides a stage was reached.
- Saved state
The integration associates the event with the right case and version.
- Customer view
The customer sees a clear status and a relevant next step.
A notification does not replace a correctly stored and displayed status.
The system accepted the request. Should the customer see the work as complete?
No. Acceptance and completed processing are different states. Show only what the source can actually confirm.
Choose one case workflow and its authoritative source
Begin with a case type that has a clear owner and identifier. Establish which system decides status and what the customer may see. Internal notes and internal work stages do not automatically belong in the customer view.
Fictional example: a service company wants to show received, scheduling, in progress and closed. Received means a request was recorded, rather than an appointment being confirmed. In progress means a defined work stage, rather than a guarantee of completion today. The business approves these meanings.
Separate current information from a delivery commitment
The portal needs a useful last-update indication and a route for questions about stale information. A fetch timestamp is not necessarily when the case changed. An unavailable source must not result in an invented new status.
Agree how paused, cancelled and reopened cases appear. Use estimated dates only when an approved source actually supplies a forecast with the intended meaning. An attractive progress indicator does not justify a fabricated completion percentage.
| Element | Decision before development | Evidence from a test |
|---|---|---|
| Source | Which system owns current status? | Compare the same test case in source and portal |
| Meaning | What actually happened at this step? | Received is not described as booked |
| Customer access | Who may read which case? | Another test customer is denied |
| Freshness | What appears when an update is unavailable? | An outage creates no false success |
| Notification | Which change should notify the customer? | The message corresponds to saved state |
Connect notifications to a verified state
Email or another notification is a separate delivery route from status storage. Define the transitions that trigger a message, repeat handling and the owner who sees delivery failures. Sending a message does not prove the customer read it.
Important changes must also make sense in the portal itself. If updates happen without navigation, relevant feedback should work with assistive technology without repeated background checks interrupting reading. Test the actual behaviour in the chosen solution.
Commission a first view with operating ownership
An initial delivery can cover one case type, one source, customer access, current status and one limited notification route. Replies to staff, attachments and payment need separate scoping. We do not promise a ready-made connection to a named system without reviewing its conditions.
Handover includes a status map, failure handling, access, operating responsibilities and test evidence. We propose scope and price after examining the source. Show an anonymised workflow and the repeated progress questions customers need answered.
Sources and further reading
Questions, answered
Can the portal show an exact delivery date?
Only when the business has a verified source and an appropriate explanation of that date. An integration does not create a reliable forecast by itself.
Is a case portal included in Imba CMS?
This page describes a separate development and integration scope. Features and connections are agreed against actual needs and technical conditions.