Sending log — what happened to a message

Communication → Message history in the side menu. Old links to the tab in Settings now redirect here.

History shows what was sent by email or SMS, usually to a customer. In-app notifications for employees (the bell in the upper-right corner) are under Communication → Notifications and do not appear in this list.

Everyone who is signed in can see their own bell notifications, even without the Notifications permission—use the bell → View all notifications. Message history and customer-message statistics require that permission.

Step by step

Check what happened to a specific message

1. Side menu → Communication → Message history. The Sent list opens.
2. Narrow the list:
   • EMAIL and SMS tiles above the table—channel (click again to remove the filter),
   • Status—a list of ten options (see the table below),
   • From and To—date range,
   • Search recipient / subject... field.

   Active filters appear as markers above the table; remove them with ×.

3. Find the row by Message (number #… and email subject or title), Type (for example, Order), Recipient, Status, and Created columns. If there is an ⓘ beside the status, hover over the marker—the tooltip explains why the message was skipped or what went wrong. The first column contains squares: channel, status, and, if there was more than one attempt, the attempt count (tooltip Number of attempts). Separate squares appear for recorded opens and clicks.
4. Click the row or choose Delivery details from its row menu. The Delivery details tab opens, with the message number. At the top are the message type and subject, then four fields: Channel, To (address or person), Created, and Status, with a sentence explaining what the status means. If the message concerns an order, document, or issue, buttons appear: Open order #…, Open document #…, Open issue #….
5. Expand an entry under Sending attempts to see a timeline of events, the full error text for a failed attempt, and Attachments, if any.
6. If the status is Skipped, the reason appears below the status at the top and in a yellow box in the attempt (for example, Disabled in preferences) with an explanation of what to do. For Recipient blocked, it says: “The recipient is on the blocked list. To send, remove them under Settings → Email and SMS → Blocked recipients.”

Not sent yet means the message was created but sending has not started. If you open an old link to a bell notification, instead of a status you see whether it was read and a blue box: it is an in-app notification, not an email.

Send a message again

1. On the Sent list, open the row menu. Send again appears only for Failed, Rejected by recipient mailbox, Temporary error — we’ll retry, Paused — sending limit, and Skipped statuses. It does not appear for a delivered message.
2. Click Send again. The same button is in the details, separately beside each attempt.
3. Confirmation: “Send again ✓” and a refreshed list. If the server refuses, a red message explains why.
4. Sending again does not require 2FA confirmation—intentionally, because this is routine. The Notifications permission is sufficient.

Do not click repeatedly. Each click creates a new attempt, and the rate limit will reject it anyway.

A message to a customer whose order data was removed by retention cannot be resent manually either. The server refuses, and the screen shows: “The buyer’s data for this order has been deleted — messages to the buyer are not sent.” No new attempt is created, and the sending window stays open.

Check overall activity

1. Side menu → Communication → Message statistics.
2. Choose a period from the list in the upper-right corner: 24h, 7 days, 30 days—7 days is the default. These three options are untranslated.
3. Read the tiles: All sending attempts, Sent (sent and delivered), Skipped, Failed (failed, rejected by mailbox, reported as spam), and breakdowns By channel and By result. Every item has a count, percentage share, and bar.
4. It counts the same messages as Message history: company emails and SMS, plus Noxti emails about the company sent to its people. In-app notifications do not count. Opens and clicks are not measured yet, so the screen does not show them.

Statuses

The difference between Sent and Delivered matters when talking to a customer: the first means “we handed it to the server,” the second means “it arrived.”

Skipped messages have a reason

A skipped message always has a reason: user preferences, subscription, exclusion list, or sender warm-up.

Check here first when someone says they did not receive a notification—very often they turned it off themselves (Notifications — the bell, email, and “Do not disturb” mode).

Emails from Noxti

The list also includes emails Noxti sends about your company to its people: a password for a new user and a new password after reset, a user-added notice, failed-login warning, and account-lock notice. They have a Noxti marker in the type column. They are sent from Noxti's system mailbox, not yours, so they do not have Send again.

If Noxti could not send one, it appears as Skipped with No Noxti mailbox or No template as the reason—contact us. Emails sent before this change was introduced do not appear in the list.

A new user says they did not receive a password? The account is created only when the mail server accepts the message. Check the recipient address and status in the list, and ask the user to check spam.

A trail for every attempt

You can see every attempt for a message and its events: queued, sent, error, bounce, complaint, delivery, open, and click. The default is three attempts.

Content disappears after about a month

The rendered message content is retained for about 30 days, then cleared. The log entry remains—you can see that the message was sent and the result, but no longer what it said.

This is data protection, not a fault. If you may need the content in a dispute, preserve it beforehand.

Resending

There is a resend action with safeguards against accidental duplication, as well as manual sending. Both are rate-limited.

Statistics

A separate screen (Communication → Message statistics) shows the number of messages, breakdowns by channel and status, and open, click, and bounce rates—by default for the last week.

Watch the bounce rate closely. An increase can precede automatic account disablement (Email warnings — bounces, automatic disabling, expiring certificate).

Permissions

The log requires the Notifications permission. Saving does not require 2FA confirmation, intentionally, because resending is a routine operation.