Thread lifecycle
Updated: Oct 8, 2026
Copy for LLM
A thread is either idle (no owner) or owned (a specific responder holds it). This page explains how threads move between those two states.
Note: Standby visibility, the escalation partner, and thread control require the business to have accepted the Meta Business Agents and Platform Terms of Service. See Terms of Service requirement.
Idle and owned
- Idle — the thread has no owner. The next inbound message from the WhatsApp user is routed by entry point to the configured primary, which becomes the new owner.
- Owned — a responder holds the thread. Inbound messages from the WhatsApp user are delivered to the current owner, regardless of the entry point. The exceptions are the changes of intent below — a CTWA ad click and a template postback — which reset the thread and re-route it by entry point even though it had an owner.
Claiming ownership
When a WhatsApp user sends an inbound message on an idle thread, the platform routes it by entry point and assigns ownership at that moment — before any responder responds. Receiving the message is what makes you the owner; you do not have to reply to claim the thread. The new owner is expected to reply to the WhatsApp user with a Service message.
The responder that becomes the owner is the configured primary for the resulting entry point, or — where the business selected Route to Sender for that entry point — the responder that sent the template being replied to. See Resolving the primary.
Terminology
The following terms describe the three ways a thread’s owner can change. They are defined here and used consistently across all Conversation Routing documentation.
| Term | Meaning |
|---|---|
Reset | The thread’s current owner is cleared. |
Re-route | An inbound message is routed by entry point to the current primary for that entry point, which may be a different responder than the previous owner. |
Ownership change | The thread’s owner becomes a different responder, either through a re-route or through thread control. |
A reset and a re-route are distinct events, and the gap between them depends on the cause:
- After 24 hours of inactivity, the thread resets and stays idle. The following inbound message is then re-routed.
- A CTWA ad click or a template postback does both at once. The same message resets the thread and is itself re-routed, so the thread does not sit idle in between.
What returns a thread to idle
| Cause | Effect |
|---|---|
24 hours of WhatsApp user inactivity | The thread resets to idle. The next inbound message is re-routed by entry point. |
The current owner calls release | The owner releases the thread back to idle. The next inbound message is re-routed by entry point. |
A CTWA ad click and a template postback also clear the current owner, but they do not leave the thread idle — the same message is re-routed immediately and the resulting responder becomes the owner. See What changes the owner.
Note: The 24-hour idle window and the 24-hour entry-point lookback window are both 24 hours, but they are not the same. The idle window determines when a thread loses its owner. The lookback determines which entry point applies to the next message. See Entry points and routing.
What does not change ownership
| Action | Effect |
|---|---|
WhatsApp user sends a quoted reply or a regular incoming message | No reset. The message is delivered to the current thread owner. |
Any responder sends an outbound marketing, utility, or authentication message | No reset and no ownership change. The thread state is unaffected, and the sender does not need to own the thread. See Sending without ownership. |
What changes the owner
| Action | Effect |
|---|---|
WhatsApp user clicks a CTWA ad | The thread is re-routed through the Click to WhatsApp entry point, and the responder that receives the message becomes the new owner. |
WhatsApp user sends a template postback (a quick-reply button tap, a list selection, or a Flow reply on a marketing or utility template) | The thread is re-routed by the resulting entry point, and the responder that receives the message becomes the new owner. Applies to marketing and utility templates only; authentication templates do not change ownership. |
Thread control | The owner can pass control to another responder, or the escalation partner can take control. Either action makes a different responder the owner. See Thread control. |
In the two re-route cases above, the new owner is the configured primary for the resulting entry point, or the template sender where the business selected Route to Sender. See Claiming ownership.
A
release is not an ownership change: it clears the owner and leaves the thread idle rather than handing it to a different responder. See What returns a thread to idle.Sending without ownership
Whether you can send to a WhatsApp user depends on the message type, not only on whether you hold the thread.
Service messages require ownership. A Service message from a responder that does not own the thread is rejected with an API error — the send fails rather than silently doing nothing. This includes an idle thread: having no owner does not make the thread open to send into. The one exception is the account’s designated escalation partner, whose Service message is an implicit take.
Marketing, utility, and authentication templates do not require ownership. Any responder on the account can send them regardless of which responder currently owns the thread, and sending one neither resets the thread nor changes its owner. A proactive template send is therefore never blocked by another responder holding the thread.
See also
- Overview — key concepts and the numbered walkthrough.
- Entry points and routing — how the platform decides which responder receives a message.
- Thread control — transfer, release, or take thread ownership.