Use chat health, service state, and capability evidence before sending.
How it works
Use chat health, service state, and capability evidence before sending. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.
Set it up
- Choose the sending identity, conversation, channel, and environment.
- Check capability, consent, current state, and channel policy.
- Use an idempotent request and verify the resulting event history.
What to expect
- The operation is traceable by stable request and resource identifiers.
- Acceptance, provider delivery, and customer interaction remain separate states.
- Retries and reordered events do not duplicate the customer action.
[!TIP] Keep API keys, signing secrets, customer addresses, and message bodies out of source and logs.