A message moves through a pipeline from the moment it is created to the moment the carrier reports what happened to it. Its status is a snapshot of where it currently is.
Before it is sent
- Pending — the message exists but is not yet being processed.
- Ready — the message is prepared and waiting to be handed to the sender.
- Queued — the message is in the sending queue.
- Sender — the message has been assigned to a sender resource.
While it is going out
- Sending — the message is being transmitted.
- Accepted — the carrier has accepted the message.
- Sent — the message has left Furcata.
Final outcomes for a text message
- Delivered — the carrier confirmed delivery.
- Undelivered — the carrier could not deliver the message.
- Failed — the message could not be sent.
- Received — the message arrived from a contact.
- Read — the recipient opened the message, where the channel reports it.
Outcomes for a call
- Initiated — the call is starting.
- Ringing — the destination is ringing.
- In progress — the call is connected.
- Completed — the call finished normally.
- Busy — the destination was engaged.
- No answer — the call was not picked up.
- Canceled — the call was stopped before it connected.
States that are not about the carrier
- Unsubscribed — the contact opted out, so the message was not sent.
- Archived — the conversation was archived.
- Unknown — the pipeline reported a state it does not recognise.
A message also records its direction: outbound for messages you send, inbound for messages contacts send to you. Delivery details reported by the carrier are read-only, because they are written by the sending pipeline rather than by you.
Where to look
Aggregate figures live on the dashboard. To understand one specific message, open the conversation with that contact and read the status on the message itself.