This article observes the parameters and setup for the Collect input from caller step within our call flow designer.
User level: Admin
Collect Input is a step available in CloudTalk's Call Flow Designer. Use it when callers need to enter data on their keypad that will be used in a follow-up step, such as an HTTP Request or dynamic routing on a Ring to step.
Add Collect Input to Your Call Flow
From the Dashboard, click Numbers.
In the My numbers tab, find the number you want to configure.
Click + Configure (or the flow name, if one exists) in the Call Flow column.
On the canvas, click the + button where you want the step.
In the step library, under Automation, select Collect Input.
Value Types (From Caller)
Accepted Input | Expected Input |
Strings [A-aZ-z0-9] | Number Strings [0-9] or Pattern Expressions |
Though character strings will be accepted, there may be better CloudTalk solutions available for companies that need long-form answers or text strings from customers.
Important: Do NOT prompt callers to include the pound/hash symbol (#). Pressing # ends the step immediately.
Configuration
The Collect Input config panel has two sections: a sound picker at the top and Collect info from caller settings below it.
Sound
The sound picker works the same as in the Greeting, IVR Menu, and Dial by Extension steps. You can create a new sound, upload one, use text-to-speech, or search your existing library. Use it to play a prompt telling callers what to enter (e.g., "Please enter your order number").
Collect info from caller settings
Note: Input from the caller can be finished by pressing #.
Seconds to wait on this step
A timeout is the default method of ending the step. The number of seconds you enter here determines how long the step waits before moving on. Make sure the timeout is longer than the greeting you've set, so callers have time to listen and respond.
Pattern
The Pattern field expects a regular expression (regex). If the regex is formatted incorrectly, it will return null or create an error during execution. The # character will not be recognized in a pattern; it will automatically end the input step.
Retry on invalid
Check this box to give the caller a chance to repeat the input if it doesn't match the expected pattern or if the timeout is reached. The maximum number of retries is 10. At the beginning of each retry, the greeting (if set) will be played again.
Using Collected Input in Other Steps
With HTTP Request
You can design a flow where callers enter information (like an order number) that is then sent via HTTP Request to another system, such as a CRM.
Add a Collect Input step followed by an HTTP Request step in your flow.
In the HTTP Request's Request Body, add a key-value pair. For the value, reference the caller input using:
{{input[123].value}}where the number in brackets is the input_id of the Collect Input step.
If you create both steps in the same session, you can enter a temporary ID in the brackets. The real ID will replace it after you click Save.
Set the paired Key to any string value expected by the receiving endpoint.
Check the box to Parse response if an HTTP response is needed to continue through the flow. If unchecked, the flow continues after the request is sent, regardless of whether a response was received.
With Ring to (dynamic routing)
Use collected input to dynamically route the call to an agent, group, or voicemail based on what the caller entered.
Add a Collect Input step followed by a Ring to step.
In the Ring to config panel, click Route dynamically via variable.
In the Route to (variable) field, enter:
{{input.step_id}}where step_id is the Step ID of the Collect Input step (e.g.,{{input.389008}}). To find the Step ID, click the three-dot menu (⋮) on the Collect Input card.
Tip: Save your flow first before referencing the Step ID. Before saving, steps have temporary negative IDs that won't work in the variable field. After saving, the Step ID becomes a permanent positive number.
Important: Always ensure the caller input being referenced is from the same number's flow. Do not try to use input collected in other call branches. Cross-referencing across branches is not supported.
Need help or have a question? Just reach out through our Support portal — we’re here for you.