The counterpart to inbound recording. Sends through providers the platform drives itself are written into the same conversation store, marked already-read (you wrote it), with the destination number normalised so a text-back can be matched to a missed call.
Also called: sent message doesn't show · no messages yet · outbound history
- 1Upserted on the provider message id, ignoring duplicates
- 2read_at is stamped immediately — outbound is never unread
- 3SMS destinations are normalised so the callback engine can see a text recovery
- 4Best-effort by design: failing to record a sent message must never fail the send, because the message has already gone
A builder could send a customer a message and their conversation would still read "No messages yet", because only the connected CRM's copy was ever displayed and the message had not gone through it. The history was also only as durable as that integration — disconnect it and the record of what had been said went with it. Everything the platform sends is now written to the customer's thread as well, so the history survives on its own.
- Sent messages missing from the customer record
- Conversation history tied to a third-party integration
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →