What the page shows
At the top, a line of figures counts the messages of the chosen period by state, for example “42 sent · 3 queued · 1 failed”. Needs you comes first. It holds the messages that didn’t reach the customer, or of which nobody knows whether they did: “3 messages didn’t reach the customer”. Each card says what happened and what to do, with a button when there is one: Send again or Open order. Messages skipped in the same bulk run are grouped on one card, “5 skipped in one run”. Below it is the Message log, newest first, by day. A bulk run is one row for the batch with its counts, for example “30 sent · 1 failed · 1 skipped”; click it to see the messages in it, and Show … more for the rest. Each row shows the Time, the Customer, the Purpose, the Channel, Sent by and the State. Show more at the bottom loads older messages.Filters
Clear filters resets them. Refresh reloads the page.
States
For how e-mail moves through these, and what Unknown means, see
What happens to an e-mail you send. An SMS becomes Delivered when the provider
reports it to Omnilinker; if no report arrives it stays Sent.
Open a message
Click a row to open the Message details panel:- From and To: the sender and the address or number.
- As sent: the text that went out, with the subject, the template it came from or “Written by hand”, and any attachments. If the customer’s data was erased, the text is gone too: “The text was erased with the customer’s data.”
- Delivery: each step with its time: Queued, Sending, Sent, Delivered, Failed, Bounced, Marked as spam and so on. A waiting SMS says “Waits until …: no SMS at night.” and a failure shows the code the channel answered.
- Why we could send it: the rule that allowed the message, for example “A service message about the order: no marketing consent needed.” A message that was refused says which rule refused it. If the customer has withdrawn a consent since, it says so.
- Conversation: the conversation the message belongs to, and the order.
- What to do: the fix for a message that went wrong.
What to do with a message that didn’t go
Send again is offered on Failed and Unknown messages, and needs the Send messages to customers permission.
Omnilinker asks Why send it again? (saved with the message) and records who sent it again and why. Send it again only
when you are sure the first one didn’t arrive: the customer would otherwise get it twice.
A customer who was erased from Omnilinker shows as “Erased customer”.