Communication Send Logs

Communication Send Logs allow administrators to review message delivery history, provider activity, delivery results, recipient information, and response details from communication providers.

Use this page to check whether emails, SMS messages, notifications, verification messages, invoices, or other communication messages were sent successfully.

Overview

The Send Logs page records communication activity generated by the Message Center, system events, templates, providers, and automated message processes. It helps administrators review delivery results and troubleshoot sending failures.

Area	Description
Search Filters	Filters send logs by provider, template, channel, status, and page size.
Log Summary	Displays total logs, current page information, and selected page size.
Send Log List	Displays matching send log records and delivery status information.

Search Filters

Search Filters help administrators narrow down communication logs. This is useful when investigating failed messages, reviewing provider usage, or checking a specific template�s delivery history.

Filter	Description
Provider	Filters logs by the communication provider used for sending, such as SMTP, SendGrid, or Twilio.
Template	Filters logs by the communication template used for the message.
Channel	Filters logs by channel, such as Email or SMS.
Status	Filters logs by delivery status, such as success, failed, pending, or other configured statuses.
Page Size	Controls how many log records are displayed per page.
Search	Applies the selected filters and refreshes the log list.

Summary Cards

The summary cards provide a quick overview of the current log result.

Card	Description
Total Logs	Shows the total number of logs matching the current filter conditions.
Current Page	Shows the current page number and total page count.
Page Size	Shows the number of records displayed per page.

Send Log List

The Send Log List displays the actual delivery history. Each row represents one message send attempt or communication record.

Column	Description
ID	The internal log ID.
Provider	The communication provider used to send the message.
Template	The template used for the message, if any.
Channel	The communication channel, such as Email or SMS.
To	The recipient email address, phone number, or destination value.
Subject	The subject of the message. This is usually used for email messages.
Status	The delivery result or processing status.
Sent	The date and time when the message was sent or attempted.
Created	The date and time when the log record was created.

Common Status Meanings

Status values may differ depending on your implementation and provider response. In general, the following meanings are commonly used.

Status	Meaning
Ready	The message has been prepared but not sent yet.
Pending	The message is waiting to be processed or provider confirmation is pending.
Sent	The message was sent from the system to the provider.
Success	The provider accepted or completed the message request successfully.
Failed	The message failed because of provider error, invalid configuration, invalid recipient, or another issue.
Error	An internal error or exception occurred during sending.

Recommended Workflow

Open Admin > Provider > Send Log.
Select a provider if you want to review messages sent by a specific provider.
Select a template if you want to review messages generated from a specific template.
Select a channel such as Email or SMS.
Select a status when checking failed or successful messages.
Choose a page size.
Click Search.
Review the Send Log List.
If a message failed, check the related provider and template settings.

Checking Failed Messages

When messages fail, use the Send Logs page to identify the affected provider, template, channel, recipient, subject, and sending time.

Set Status to Failed or Error.
Click Search.
Check which provider was used.
Check whether the recipient address or phone number is valid.
Review the related template and provider configuration.
Run a provider send test if needed.

Common Use Cases

Use Case	Recommended Action
Verify whether an email was sent	Filter by provider, channel Email, and recipient if available.
Find failed SMS messages	Filter by channel SMS and status Failed or Error.
Review template activity	Select the template and search the log list.
Check provider usage	Select a provider and review all matching send logs.
Audit recent communication activity	Review logs by status, provider, and created date if date filtering is available.

Relationship with Other Communication Features

Feature	Relationship
Provider	The provider controls how the message is sent. Incorrect provider settings can cause failed logs.
Template	The template controls the message subject and body. Incorrect templates may cause broken content or missing variables.
Message Center	Messages sent manually from the Message Center may generate send log records.
Event-Based Sending	Messages triggered by system events may also appear in send logs.

Troubleshooting

Problem	Possible Cause	Solution
No logs found	No messages have been sent, or the current filters are too restrictive.	Clear filters and search again.
Message failed	The provider may be inactive, misconfigured, or missing credentials.	Check provider settings and run a send test.
Email was sent but not received	The message may be blocked, sent to spam, or rejected by the recipient server.	Check provider response, sender verification, SPF, DKIM, DMARC, and spam folders.
SMS failed	The phone number may be invalid, the account token may be wrong, or the vendor may reject the request.	Check phone number format, provider credentials, and vendor response.
Wrong template content was sent	The wrong template may have been selected or mapped to the event.	Review template settings and event/template mapping.
Variables were not replaced	The template may contain unsupported or misspelled variables.	Use variables supported by the related sending process.

Important Notes

Send logs are used for review and troubleshooting.
A log record does not always guarantee that the recipient read the message.
Provider acceptance and final delivery are not always the same.
Some providers may accept a request but later reject delivery.
Failed messages should be checked together with provider configuration.
Logs may include recipient information, so access should be limited to authorized administrators.

Best Practices

Review failed logs regularly.
Keep provider configuration up to date.
Use tested templates for production messages.
Monitor sending failures after changing SMTP, SendGrid, Twilio, or other provider settings.
Use filters to narrow down logs instead of reviewing all records at once.
Protect send log access because logs may contain email addresses, phone numbers, and message subjects.

Communication Send Logs are essential for confirming delivery activity and troubleshooting message failures. When a user reports that they did not receive a message, this page should be one of the first places to check.