Ask Phone
The Ask Phone node requests a phone number from the customer and validates the format before proceeding. Use it when you need to collect a contact number and want to ensure it's properly formatted.
How It Works
The node sends your prompt message, waits for the customer to reply, and validates their input against a phone number pattern. If the format is invalid, it shows an error message and asks again. Once valid, the phone number is saved and the flow continues.
The prompt accepts {{variable_name}} placeholders. A variable that nothing has set when the node runs is not replaced — the customer sees {{variable_name}} as written and the node writes one warning notice on the conversation listing the unresolved names.
The node is available on the WhatsApp and web channels. Email flows do not offer it in the editor.

Validation
The node accepts 7 to 15 digits, optionally starting with a plus sign. No spaces, dashes, or parentheses — just digits.
What passes:
+593999123456(with country code)593999123456(country code, no plus)0991234567(local format)
What fails:
+1-555-123-4567(dashes not allowed)(555) 123-4567(parentheses and spaces not allowed)123456(too short — minimum 7 digits)
When validation fails, the node displays your configured error message and waits for another attempt.
When to Use It
Collecting contact information. You need a phone number to reach the customer later. The node validates the format and can save it as a Point of Contact on their borrower record.
Requesting an alternate number. The customer already has a primary phone on file, but you need a secondary contact. Save as a Point of Contact without marking it as the main phone.
Saving as Point of Contact
When the Point of Contact toggle is enabled, the phone number is saved directly to the customer's borrower record — not just as a conversation variable. This requires the borrower to already exist in the system; use Login or Create Entity first.
Setting the Main Phone toggle marks it as their primary contact number, which the system uses for notifications and campaigns.
For more on how contact information is stored and managed, see the Points of Contact API.
The Country Code Setting
The configuration UI shows a country code dropdown with options like +593 (Ecuador), +52 (Mexico), +1 (United States). At the time of writing this selector is not known to change what the node accepts or stores: customers can enter any phone format regardless of what you select, and the digits are saved as typed. This behavior is pending review; if your flow depends on the country code, test it on your channel before relying on it.
If you need a specific format, say so in your prompt message: "Please enter your phone number in international format (example: 593XXXXXXXXX)."
Verification
Points of Contact start unverified. If you need to confirm the customer actually controls the phone number, follow up with the POC Verification node.
Publish Gate
| Rule | Result |
|---|---|
| No prompt message | Blocks publishing: "Phone request message is required" |
| No validation error message | Warning: "Validation error message is not configured". The node still asks again on an invalid answer, but the customer gets no explanation of what was wrong |
Output Handles
| Handle | When it fires |
|---|---|
| Success | Valid phone entered and saved |
| Error | Borrower not found (when saving as Point of Contact), or system failure |