Telephony

NueForm Telephony lets you collect form responses through natural phone conversations. Callers interact with an AI-powered voice agent that reads questions, interprets answers, and validates responses in real time.

Overview

Instead of filling out a form on a screen, respondents can call a phone number linked to your form. The AI voice agent — powered by our proprietary NueSpeak Apex TTS engine — guides them through each question conversationally.

Key capabilities:

• Inbound calls — Respondents call your dedicated number
• Outbound calls — Automatically dial respondents from your number
• Smart correction — Callers can go back and fix any previous answer by name
• Mandatory confirmation — Sensitive fields (names, emails, phones, addresses) are spelled back for verification
• DTMF support — Callers can press number keys for rating scales, multiple choice, and yes/no questions
• Real-time validation — Answers are validated against the same rules as your web form

Getting Started

Provisioning a Phone Number

1. Navigate to Telephony in the sidebar.
2. Click Add Number and select Inbound or Outbound.
3. Choose your country and area code.
4. The number is provisioned instantly and ready to link to a form.

Linking a Number to a Form

1. Open Telephony and find your number.
2. Click Assign Form and select the form you want to use.
3. Inbound calls to that number will now walk callers through your form.

Custom Voice

You can customize the voice your callers hear:

• Design a voice — Use the Voice Designer to create a unique AI voice from a text description.
• Record a voice — Upload a short audio sample (minimum 10 seconds) and our NueSpeak Apex engine will clone the voice characteristics.
• Upload audio — Provide a pre-recorded voice sample file (WAV, MP3, or M4A).

Voice settings are configured per phone number in the Telephony dashboard.

Pricing

Call usage is metered and billed through your subscription. You can monitor usage and costs in the Billing section.

Supported Question Types

The following question types are fully supported over phone:

Unsupported Question Types

These types require visual interaction and are skipped during phone calls:

• File Upload
• Signature
• Drawing
• Payment
• Save & Continue

Require Confirmation Toggle

Any supported question type can have Require Confirmation enabled in the question settings. When toggled on, the AI agent will always spell back or read back the caller's answer and ask for verification before moving on — even for types that don't normally require confirmation.

How Calls Work

Inbound Flow

1. Caller dials your number.
2. A brief greeting plays (customizable).
3. The AI agent reads each question aloud.
4. The caller responds by speaking or pressing keys.
5. The agent validates the answer and moves to the next question.
6. At the end, responses are saved as a standard form submission.

Outbound Flow

1. You initiate a call from the Telephony dashboard or API.
2. The system dials the respondent.
3. An optional screening question verifies the recipient.
4. The same question-by-question flow proceeds.
5. Responses are saved upon completion.

Corrections

Callers can correct any previous answer at any time:

• "Go back" — Returns to the previous question.
• "I need to change my first name" — Jumps directly to the first name field.
• "Change my first name to Azad and my rating to 5" — Corrects multiple fields in one request.

After corrections, the call automatically returns to where the caller left off.

Validation

All form validations apply during phone calls:

• Required fields cannot be skipped (unless the form allows it).
• Email format is validated (must contain @ and a domain).
• Phone format must contain valid digits.
• Number ranges (min/max) are enforced.
• Custom regex patterns set in the form builder apply.
• Custom validation messages are read aloud when validation fails.

Call Recordings

Calls are recorded in dual-channel format (agent and caller on separate tracks). Recordings are retained for 90 days and accessible from the form's response detail view.

Best Practices

1. Keep questions concise — Shorter questions are easier to understand over the phone.
2. Use Contact Info for name/email/phone — Sub-fields are handled individually with built-in spelling confirmation.
3. Enable Require Confirmation for critical data — Custom toggle forces verification on any question.
4. Test your form — Make a test call to verify the flow before sharing the number.
5. Consider DTMF — For rating/choice questions, callers can press number keys for faster input.