Quickstart Guide

This guide takes you from a new workspace to a tested outbound voice agent. It covers the smallest safe production path and links the deeper platform guides for telephony, webhooks, and compliance.

What you need

• An OP26X account with permission to create agents
• A verified test or production phone number
• A concise qualification goal, such as budget, timeline, and preferred location
• Approved source data for project pricing, availability, and compliance claims
• An HTTPS endpoint if you want to receive call events

Create the first agent

1. 01

   Open Agents and create a new agent

   Use a descriptive working name. Keep production agents separate from test agents so prompts, numbers, and integrations can be promoted deliberately.

2. 02

   Set the conversation goal

   Define the one outcome the call should achieve, the facts the agent may discuss, the questions it must ask, and the conditions that require human handoff.

3. 03

   Choose a voice and language

   Select the closest natural voice for the primary audience, then set the speaking style to concise and conversational.

4. 04

   Attach trusted knowledge

   Add only current, approved project documents. Remove superseded price sheets and availability exports before publishing.

5. 05

   Configure the first message

   Identify the business, state the reason for the call, and ask permission to continue. Avoid long introductions.

Test the conversation

1. Place a test call from an internal number and confirm the caller ID is expected.
2. Check the opening message, pronunciation, turn-taking, and interruption handling.
3. Test the happy path, one objection, one out-of-scope question, and one safety refusal.
4. Verify that a qualification result and a follow-up action appear on the call record.
5. Send a test webhook and confirm that your endpoint returns a 2xx response quickly.

Publish safely

1. 01

   Run the production checklist

   Confirm the prompt, knowledge, number, consent, event subscriptions, and escalation path.

2. 02

   Start with a small campaign

   Use a low concurrency limit and a narrow audience. Monitor answer rate, transfers, failed calls, and qualification quality before expanding.

3. 03

   Keep an auditable change trail

   Record which prompt and knowledge version handled each live call and who approved each material change.

Production checklist

• Caller identity, consent basis, and approved calling template are documented
• Knowledge contains no stale pricing, unsupported claims, or confidential data
• Human escalation has an owner and a tested destination
• Webhook processing is idempotent and observable
• A rollback path to the previous agent version is available