Objective

Conversation timeouts control how long a conversation stays in a state before it automatically moves to the next one. This article helps you review the current timeouts per channel and change them, including whether conversations pass through an inactive state before they close.

Product

Conversation Orchestrator

Environment

Twilio Console

Procedure

1. In the Twilio Console, select Orchestration in the left sidebar.
2. Select Conversation Orchestrator, then Conversation configurations.
3. Select the name of the configuration you want to change.
4. Scroll to the Conversation lifecycle and timeouts section of the Overview tab and review the table of Channel type, "Inactive" timeout, and "Closed" timeout.
5. Select Edit.
6. In the Edit lifecycle defaults panel, choose a Conversation lifecycle:
7. Basic, conversations start in the open state and transition straight to closed.
8. Include "inactive" state, an inactive conversation has no streaming communication data but can be reopened.
9. Under Configure timeouts, set the timeout duration for each channel: SMS/MMS, Voice (calls), RCS, and WhatsApp.
10. Select Save changes. A confirmation message reads Lifecycle timeouts updated.

Additional Information

• Conversations always start in the open state, and once a conversation is closed it cannot be reopened.
• When you set an inactive timeout for a channel, a closed timeout is also required, and the closed timeout must be greater than the inactive timeout.
• Timeouts are set per channel. In a multi-channel conversation, the longest timeout always applies.

This content was generated by AI and reviewed, edited, and verified by a human.