Skip to content
ContractSpec
Start here

reference

Support conversation actions and ambiguous outcomes

Reply, note, assign, snooze, reopen and close are separate provider effects with durable custody and read-back reconciliation.

field.key.label
docs.customer-support.conversation-actions
field.version.label
field.type.label
field.title.label
Support conversation actions and ambiguous outcomes
field.tags.label
supportos,intercom,idempotency,reconciliation
field.owners.label
field.stability.label
public

Each action is claimed in durable custody under its idempotency key before any provider call. A repeated key with the same payload digest returns the stored outcome without a second effect; a different digest is an idempotency conflict.

Customer-visible actions (reply, close) require a verified approval bound to the exact payload digest and a basis part. An approval counts as authority only when it proves an independent human signer (isIndependentHumanApprover): the signer comes from SupportApprovalIdentityPort (approval evidence, never the caller) or else from the verdict, is a human, and is not the responder the effect is performed as. Signer refs are principal refs, so a provider responder (an Intercom admin_id) is compared through SupportResponderPrincipalPort; an action port that performs effects as a provider admin refuses approval-authorized effects when that mapping is unbound, names no principal or names the signer, and reports a failed lookup as DEPENDENCY_DEGRADED. support-resolution-v1 also checks, on approval and again before dispatch, that the signer matches the recorded approver and is not the proposer. Internal actions require that approval or a Connect admission bound to the digest. Before a customer-visible action is sent, the conversation is read back: a newer responder or customer part marks it superseded; another owner or a closed conversation marks it rejected.

A timeout, network failure, provider 5xx or malformed success after the request was sent yields uncertain. Reconciliation reads the conversation back; only a part absent before dispatch, with the same author, type and body digest and created no earlier than dispatch, proves acceptance. A local correlation is never acceptance evidence. Absence after the grace window stays uncertain until a human confirms it (not-executed). A reply never resolves the issue.