Admin HQ Compliance includes Message Events for internal review of SMS and email activity. Operators can see channel, direction, status, consent status at send, and creation time before investigating delivery or consent issues.
Open Message Events
From Admin HQ, open Compliance or go to /admin/compliance. The Message Events section is the internal operator table for reviewing recent SMS and email activity across workspaces.
Use this surface for launch review, support triage, and compliance evidence. The business workspace remains the place where users reply to customers and manage lead conversations.
What the table shows
- Channel, such as SMS or email.
- Direction, such as inbound or outbound.
- Status, such as received, queued, sent, delivered, failed, or blocked.
- Consent status at send, when Cendaro recorded consent context before an outbound send.
- Created date, which shows when the event record was written.
Direction and status
Inbound events show messages received from customers or providers. Outbound events show attempts Cendaro made to send SMS or email.
A blocked status means Cendaro prevented the send before delivery because the consent guard or unsubscribe state did not allow the selected message purpose. A failed status means the send was attempted but the provider or delivery path failed.
Consent status at send
Consent status at send is a snapshot of the consent decision when an outbound message was evaluated. It is useful when a workspace asks why a reply, follow-up, or marketing message was allowed or blocked.
If the value is missing, compare the event with the related Consent Logs record and the lead source before concluding that consent proof exists.
When to investigate
- A workspace reports that a customer reply was not visible or a business reply was blocked.
- A message has failed or blocked status and the owner needs a clear explanation.
- A STOP or START keyword was received and the consent record should have changed.
- A support or privacy review needs evidence of inbound or outbound communication activity.
- A delivery provider incident may have affected SMS or email traffic.
Keep audit logs separate
Message Events can contain message body evidence. Audit Logs should remain minimal and should not duplicate full customer conversations.
When reviewing an action, use Audit Logs to understand who or what triggered a workflow, then use Message Events to understand the communication result.
Safe operating habits
- 1Confirm the workspace and lead context before responding to an operator or customer-support question.
- 2Check direction first so inbound customer replies are not confused with outbound business sends.
- 3Compare blocked outbound events with Consent Logs before changing any consent record.
- 4Do not override unsubscribe evidence unless START or another valid consent proof supports it.
- 5Avoid exporting or pasting message bodies unless a support, privacy, or legal workflow requires it.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.