Message events give your team an operational record of SMS and email activity, including consent status at send time and blocked-send evidence.
What message events record
Cendaro records message events for SMS and email activity so owners, managers, and internal operators can understand what happened without relying on memory or screenshots.
- Channel, such as SMS or email.
- Direction, such as inbound or outbound.
- Body for message history and troubleshooting.
- Status, such as queued, sent, delivered, failed, received, or blocked.
- Consent status at send time, when available.
- Sent, delivered, failed, and created timestamps.
- Error codes, such as consent_blocked, when a send cannot proceed.
Blocked sends
When Cendaro blocks a message because the contact is unsubscribed or consent is missing for the message type, the event should be recorded with blocked status and consent_blocked as the error code.
This protects the workspace by making the block visible instead of silently failing or encouraging an unsafe workaround.
Message events versus audit logs
Message events can include the message body because they are part of the message history. Audit logs should avoid sensitive full message bodies and instead record the action, entity, actor, and before/after context where needed.
Where to review events
Team members usually review message history on the lead. Owners and internal operators can use compliance visibility surfaces, such as Admin HQ message events, to investigate delivery, blocked sends, and consent evidence.
Troubleshooting checklist
- 1Check whether the event direction was inbound or outbound.
- 2Review the status and error code.
- 3Compare the consent status at send time with the message purpose.
- 4Confirm whether the customer replied STOP or START.
- 5Use the event history before changing consent or retrying a message.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.