Message logs show the practical history of inbound, outbound, delivered, failed, and blocked communication so teams can understand what happened on a lead.
What message logs show
Message logs are the readable communication history attached to a lead. They help owners, managers, and team members see what was received, sent, blocked, delivered, or failed.
- Inbound customer SMS or email replies.
- Outbound replies sent by your team.
- Messages generated from reminders or follow-up actions.
- Blocked send attempts when consent does not allow the message.
- Delivery and failure status when the provider reports it.
Common statuses
- Received means the customer or provider sent Cendaro an inbound message.
- Queued means the outbound message is being prepared or handed to the provider.
- Sent means the message was accepted for delivery.
- Delivered means the provider confirmed delivery when that signal is available.
- Failed means the provider or Cendaro could not complete the send.
- Blocked means Cendaro stopped the send because consent or message purpose was not valid.
How logs help the team
Use message logs before retrying a send, changing consent, or asking a customer to repeat themselves. The log should tell the team whether the customer replied, whether a send was blocked, and whether delivery evidence exists.
Logs versus audit logs
Message logs are for communication history and may include message content. Audit logs are for operational accountability and should avoid full sensitive message bodies.
Troubleshooting checklist
- 1Open the lead and review the most recent messages.
- 2Check the channel, direction, and status.
- 3If blocked, review consent status and message purpose.
- 4If failed, review the provider error when available.
- 5If the customer says they replied, confirm the inbound phone number or email matches the lead.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.