reference
Support resolution workflow (support-resolution-v1)
Recovers a case from conversation evidence, proposes a cited response, dispatches under approval and records the actual resolution outcome.
- Recover reads the provider conversation (Intercom stays authoritative) and records the customer issue parts as evidence. One responder is custodian.
- Propose prepares a reply or internal note with citations to conversation parts, knowledge or engineering work, plus the agreed resolution criterion. Conversation-part citations must reference parts actually observed.
- Approve is required for every customer-visible reply. The approval binds the exact action payload digest; changing the text needs a new approval. Its verified signer must be a human, not the proposer, not the responder and equal to
approvedByRef; hosts takeapprovedByReffrom the approval evidence, never from the caller. A host that records a provider admin id asresponderRefbindsSupportResponderPrincipalPort: an unmapped responder is refused and the mapped principal may not approve. Internal notes need that approval or a Connect admission (standing mandate). - Dispatch is refused for agent or unidentified principals, re-verifies the recorded approval and its signer before the effect, and executes the conversation action. Timeouts or malformed success leave the response
response-uncertainuntil read-back reconciliation; a newer human or bot reply marks the proposalsuperseded. Absence after the grace window needs a humanresponse.confirm-absentbefore a new proposal. - Outcome is recorded separately from the reply.
resolvedrequires the criterion's evidence: customer confirmation part, a fixed engineering work item plus an accepted notification, or an accepted answer. A new customer message after resolution reopens the workflow.