Skip to main content
This builds an outbound agent. It calls someone, says why, checks whether they are interested, and then does one of two useful things: books a meeting, or agrees a time to try again. Those two outcomes are the point. An outbound call that ends without either is a contact spent for nothing. Once it works, you point a campaign at it.

Before you start

1

A connected calendar

Needed for Appointment Scheduling. Google Calendar, Microsoft Outlook, Cal.com, GoHighLevel and Calendly are all offered. See Google Workspace or Outlook.
2

A phone number

For test calls and later for the campaign. See Numbers.
3

A sentence about what you sell

You will need it for the prompt. “AI voice agents that answer calls for small businesses” is enough.

1. Create the agent

Go to Agents, create one, and name it. On Basic Information, choose a Voice and Language. Leave the rest at defaults for now.

2. Write the opening lines

Initial Message is what the agent says the moment the call connects. On an outbound call this is the whole game. You have about one sentence before the person decides whether to stay on. Say who you are, and ask for permission:
Hi , this is the virtual assistant calling on behalf of . Do you have a quick minute?
Voicemail Message is what it leaves on an answering machine.
{first_name} is filled from your contact list or campaign. If it is missing the agent still works, so write the line to read acceptably either way.

3. Give it the two exits

The agent needs a way to end a call usefully. Add both skills under Choose Skills on Basic Information.

Appointment Scheduling

For the people who say yes. Event types come from your calendar, not from Fluents, so create the meeting type there first. See Appointment Scheduling.

Call Back Later

For the people who say “not now”. Both are required. Write the callback opener assuming the person has forgotten agreeing to it, because they usually have. The agent handles the actual time negotiation itself, including vague answers like “tomorrow afternoon”. See Call Back Later.

4. Write the prompt

Paste the example below into Agent Prompt and replace {company_name} and {product_or_service}. You can also start from the library, or use Generate Prompt. See Prompts.
Click Save.

5. Test it

Click Test Agent, then Start Phone Call and enter your own number. Listen for the things that actually lose outbound calls:
  • Does the opening line earn another ten seconds?
  • Does it ask one question at a time, or interrogate?
  • When you say “not interested”, does it thank you and stop, or push?
  • When you say “call me tomorrow afternoon”, does it pin down a real time and confirm it back?
Test the “not interested” path before the happy path. An agent that argues with people who said no is worse than no agent, and it is the path nobody rehearses.
The call then appears in Calls with the transcript.

6. Fix it from the recording

When something goes wrong, open the call and click Improve agent. Describe what should have happened and review the proposed prompt changes one at a time. See Testing an agent. Turn the bad call into a test case first, so you can prove the fix worked.

7. Point a campaign at it

Once the agent handles a call properly on its own, it is ready for a list. Set up your first campaign walks through a deliberately tiny one, two contacts, so you see the machinery before you trust it with real numbers.

Where to go next

  • Every agent setting: Agents
  • Capture what each call told you: Post-call
  • Stop calling people who asked you not to: DNC List