| 5 minutes read | Level: Beginner | Last Updated: October 2025 |
Wait for the contact to respond
The Wait for Response node is used whenever the flow needs to pause and collect an answer from the end user. It ensures the conversation continues only after the contact replies, making it useful for registrations, surveys, quizzes, and feedback collection.
Once the response is received, it can be validated, stored in a variable, and reused later in the same flow or across different flows.
Note: the contact variable can be used across flows, but the result variable is limited to the same flow.
Why use Wait for Response?
The Wait for Response node is essential whenever a flow needs input from the contact. Common use cases include:
- Gathering registration details (e.g., name, age, email).
- Conducting surveys or quizzes.
- Collecting feedback or applications.
- Capturing media, files, or location details.
How to configure
1. Insert a Wait for Response node in your flow.
2. Select a Response Type from the dropdown.
3. Give a Result Name (this becomes your variable).
4. (Optional) Check Continue when there is no response to nudge the users to respond.
5. Save the node(click on Ok).
Response Types
Text-based responses
1. has any of the words
This option accepts the input if it contains any of the words defined in the response criteria. Multiple words can be added, separated by commas. For example, if the criteria include Yes, Y, Ya, Yup, then any of these responses will be treated as valid. Also, if the field is left blank, any text response from the user will be accepted.
2. has all of the words
To accept the input if the input matches exactly what is defined in the response criteria.
3. has a phrase
To accept the input if the input is present in the response criteria.
4. has only the phrase
Accepts only if the response matches exactly what is defined in the response criteria.
Numeric responses
1. Has a number
Accepts any numeric input, This will accept any number as a valid response. Any non numeric input will be treated as invalid response.
2. has a number between
Accepts input if it is numeric and falls within the defined range. This option will accept numbers only given in the range. any number out of range will be treated as invalid response. Example: Criteria = 18-60, so only numbers within 18 and 60 range will be accepted.
3. has a number equal to
Accepts input only if it exactly matches the defined number. This will accept only the number given in the criteria as a valid response. Any other response will be treated as invalid response. Example: Criteria = 5, so only 5 will be valid.
Contact details
1. has a phone number
Accepts input if the response is a valid phone number.It accepts mobile and landline numbers.
Supported formats include:
- 10 digit Mobile number (XXXXXXXXXX).
- 10 digit Mobile number with 0 prefix (0XXXXXXXXXX).
- 10 digit Mobile number with country code prefix (+91 XXXXXXXXXX).
- landline number with (XXX XXXXXXX).
- landline number with 0 and state code (0XXX XXXXXXX).
- landline number with with country code prefix (+91 XXX XXXXXXX).
2. has an email
Accepts input if the response is a valid email address. Examples: abc@xyz.xyz, abc@xyz.xyz, abc@xyz
Media responses
1. has media
Accepts input if the response is a media file (jpeg, png, mp4). Users can store both the URL and caption of the media file.
- To store the media file - create a result variable(in the given example below, picture is given as result name)
Now users can use the media file URL received and its caption.
In this example, the syntax will be.
- for media file URL @results.picture.url
- for media file caption @results.picture.caption
2. has audio
Accepts input if the response is an audio file.
3. has video
Accepts input if the response is a video file (mp4 video files).
4. has image
Accepts input if the response is an image file (jpeg, png).
5. has file
Accepts input if the response is a document (pdf, doc).
Location
1. has location
Accepts input if the response is a location
- User can get the value of location with Has Location in contact response and save it in the form of longitude and latitude.
- In the given example, result name is given as ‘location’.
- Now user can save or use the location details received in longitude and latitude forms in the flow like other variables.
To get the detailed location details using webhook - refer to this document
Matches Regex
This option is used to validate a response against a specific format using a regular expression (regex). It is especially useful when inputs need to follow strict patterns, such as dates, ID numbers, or custom codes.
Example: To ensure a date of birth is entered in the format DD/MM/YYYY, use the following regex: ^(0[1-9]|[12][0-9]|3[01])/(0[1-9]|1[0-2])/[0-9]4$
Valid responses include - 05/09/1995, 31/12/2000
Handling no response
If a contact does not respond, you can configure the flow to continue after a set wait time. Example: Send a reminder after 2 hours of inactivity.
Click on ‘Continue if there is no response for’ and choose the time gap after which a nudge will be sent to the end user. In the example given below, a reminder is sent to the end user every hour (up to 3 times) if no response is received.