Skip to main content
About the Resource Center

Callback phone number creation tips

When you create a flow in Architect, it is most helpful to configure it to retrieve as many digits as possible from a caller to help convert the information into a global phone number. Most often, prompting the caller will help ensure the desired number is collected. The flow author, through prompt cues, ensures the number of digits entered by the caller does not exceed the length of the dialing code and the subscriber number. Then, the author can set up a phone number data type that retrieves the customer-entered number and creates a new phone number, converting it to a global number. 

Converting customer-entered numbers into global phone numbers anywhere a phone number is used provides significant benefits, including:

  • Accurate runtime handling of phone numbers occurs for playback
  • The correct phone number is called during a callback attempt

If, for example, the “+” does not exist in the customer-entered phone number string, the string is treated as a local phone number and runtime behavior results may be limited. The “+” tells the system that the next 1 to 3 digits that follow it indicate the phone number’s dialing code which, when extracted, will create a global phone number.

The following scenarios offer insight to the flow author of ways Call.Ani can be used in the Phone Number data type to construct the acquisition of the most usable phone number string.

Note: These examples apply to “tel” phone numbers.