Twilio Studio Flow Bug Fix – Drip Campaign & Session Handling
Budget: $10 – $30 USD
Twilio Studio Flow Bug Fix – Drip Campaign & Session Handling
I have a Twilio Studio Flow set up to run a text message drip campaign using the “Send & Wait for Reply” widget. The flow sends a series of five messages, and before each message is sent, it checks a variable (e.g., user_replied). If the variable is set to true, the drip campaign stops and the conversation continues on our two-way messaging platform. If it’s still false, the next message in the sequence is sent.
The variable is meant to change to true when the customer replies, which should stop the flow and hand off the conversation to our two-way system.
The problem:
We start the flow via the API Trigger, but when the customer replies, it goes through the Incoming Message Trigger. Twilio Studio treats these as two separate sessions, so it doesn’t associate the reply with the original flow. As a result, the variable doesn’t update in the original flow context, and the drip continues even after the customer has replied.
What I need:
I need someone to help resolve this session context issue in Twilio Studio so that:
1. The customer’s reply is correctly associated with the original API-triggered flow session.
2. Once a reply is received, the variable is set to true, and the drip campaign is stopped immediately.
3. All further messages are directed to our two-way messaging platform.
Let me know if you’ve dealt with this kind of session handling in Twilio Studio before.
I have a Twilio Studio Flow set up to run a text message drip campaign using the “Send & Wait for Reply” widget. The flow sends a series of five messages, and before each message is sent, it checks a variable (e.g., user_replied). If the variable is set to true, the drip campaign stops and the conversation continues on our two-way messaging platform. If it’s still false, the next message in the sequence is sent.
The variable is meant to change to true when the customer replies, which should stop the flow and hand off the conversation to our two-way system.
The problem:
We start the flow via the API Trigger, but when the customer replies, it goes through the Incoming Message Trigger. Twilio Studio treats these as two separate sessions, so it doesn’t associate the reply with the original flow. As a result, the variable doesn’t update in the original flow context, and the drip continues even after the customer has replied.
What I need:
I need someone to help resolve this session context issue in Twilio Studio so that:
1. The customer’s reply is correctly associated with the original API-triggered flow session.
2. Once a reply is received, the variable is set to true, and the drip campaign is stopped immediately.
3. All further messages are directed to our two-way messaging platform.
Let me know if you’ve dealt with this kind of session handling in Twilio Studio before.