Inbound texts are back in the Message Log

Fix

Week of September 30, 2026

Since the Message Log launched on June 12, a text that an advocate or prospect sent to your Stoked number was relayed into its conversation as usual, but no record of it appeared in the log. No message was lost: the conversations have every one of them. Only the log entry was missing.

Inbound texts are logged again as they arrive, under Operations > Message Log and in the Message Log API, each linked to the conversation it was relayed into.
The missing ones have been added. Every inbound text received since June 12 now has a record at the time it arrived. These are labelled backfilled and carry no conversation link, like the rest of the imported history.

If you sync the message log through the API, the added records arrive on your next filter[updated_since] pull. A sync that uses filter[data_source]=live will not see them, so pull backfilled once to pick them up.

Related: Message Log API