Your message
never arrives.
TeamChat is the messaging app. HarborCloud runs its cloud connection. Customers are missing messages, and both companies need to investigate.
Relay connects two companies’ agents through Switch.
People approve what gets shared and changed.
Your message never arrives. Which company needs to fix it?
The problem between the teams
Engineers pass findings back and forth. Each answer creates another question. And their logs can contain customer information and private system details.
Relay gives the agents a shared incident to work through, while people control what leaves their company and what changes in it.
An illustrated walkthrough of the recorded incident.
TeamChat is the messaging app. HarborCloud runs its cloud connection. Customers are missing messages, and both companies need to investigate.
TeamChat’s agent checks its app. HarborCloud’s agent checks its cloud. The detailed diagnostics stay with their own teams.
Maya reviews the proposed finding before it reaches HarborCloud. The approved finding crosses through Switch. The private report stays behind.
Leo approves the cloud repair. All six cloud checks pass. But only 15 of 24 messages arrive. That result sends TeamChat’s agent back to the app.
Maya approves the remaining app recovery. The same delivery test now passes. The earlier failed message is recovered once, even if it is requested again.
Watch the recorded executionA customer sees one failure. The answer spans two companies.
Illustrative text. Delivery counts from the recorded local run.
Watch the agents work in Mattermost: private investigations, owner approvals, the failed delivery check, and the final recovery.
Switch carries the conversation between the agents and their owners. Relay adds the rules for what can cross the boundary, who can approve a repair, and how recovery gets checked.