Skip to content

Outbound voice AI

Outbound AI calling for sales follow-up.

Assistable’s outbound AI agents qualify leads, reactivate contacts and book appointments. Start calls from HighLevel workflows or run campaigns with calling windows, pacing, retries and human handoff.

Plans start with quarterly commitments. See the current usage rates.

Turn follow-up into a conversation.

Explore the capabilities and controls behind this part of your deployment.

Start follow-up from HighLevel

Add the Make an AI Call action to a HighLevel workflow, select the assistant and choose the trigger. Use it for new inquiries, scheduled follow-up or eligible contacts you want to reconnect with.

  • Form, tag or scheduled workflow triggers
  • Your assistant’s qualification instructions
  • Connected booking tools and call transfers

A/B test assistants on live traffic

Split a campaign across assistants by traffic percent; splits must sum to 100 before start. Assignment is deficit-based per dial, so realized traffic converges on the configured split even if you edit it mid-campaign. Per-assistant rollups show dialed and answered counts side by side.

  • Splits validated to sum to 100% before start
  • Deficit-based assignment, not random
  • Per-assistant answered and dialed rollups

Calling windows, pacing, and retries

Set a local time-of-day window with days of the week; overnight windows wrap midnight. Cap concurrent calls and calls per minute per campaign. No-answer, busy, and failed outcomes requeue with a configurable delay until max attempts, and retries wait for the window too.

  • Timezone-aware windows, including overnight wrap
  • Retries honor calling windows
  • Per-campaign concurrency and calls-per-minute caps
  • Configurable max attempts and retry delay

Respect contact preferences

Campaigns check do-not-disturb settings and your blacklist before dialing. Configure calling windows and retry limits for the contacts you are authorized to reach, and review opt-outs alongside campaign outcomes.

  • DND contacts skipped automatically
  • Blacklist checked on every outbound dial
  • Wallet at zero pauses the campaign with a stated reason

Enroll from your CRM or a CSV

Enroll by picking contacts, by the same core filters as your contacts list (tags, status, search, has-phone), or by uploading a CSV that matches existing contacts by phone and creates the rest. A unique constraint dedupes enrollments; filters take up to 25,000 contacts at once.

  • Same tag, status, search, and has-phone filters as contacts
  • CSV import matches contacts by phone, creates the rest
  • Up to 25,000 contacts per filter enrollment
  • One row per contact per campaign, database-enforced

Review the results of your follow-up

See answer rates, transfers, appointments, lead outcomes and cost at campaign level. Inspect individual conversations and destination records to understand which contacts need another step.

  • Campaign and per-contact outcomes
  • Appointments, transfers and opt-outs
  • CSV export for your team

At scale

Built for the agent lifecycle.

01

Deploy

Create a campaign, pick assistants and numbers, enroll a list, and press start. Pre-start checks refuse to launch until splits sum to 100, every assistant is voice-ready, and a dialable outbound number exists.

02

Test

Run a small list first: enroll a handful of contacts, cap concurrency, and read per-contact outcome rows. A/B splits let you trial two prompts on the same list and compare answered calls per assistant.

03

Scale

Top-up runs every minute to your concurrency cap, spreading dials across a number pool if you use one. Filter enrollment takes up to 25,000 contacts at once; a per-tick dial budget keeps the engine stable.

04

Observe

Live KPIs update as calls end: answer rate, transfers, appointments, hot leads, opt-outs, spend, and dials per hour. Export the outcome CSV or generate an AI summary of what worked and what to do next.

Under the hood

The details your team needs.

ENGINE
Minutely cron tick; optimistic claim-first updates make overlapping ticks safe
SPLITS
A/B traffic across assistants; deficit-based assignment converges on the configured split
WINDOWS
Local time-of-day windows with day-of-week selection; overnight windows wrap midnight
RETRIES
No-answer, busy, and failed requeue with a configurable delay until max attempts
GATES
DND, blacklist, and E.164 checks per dial; wallet at zero pauses the campaign with a reason
RECONCILE
Call webhook writes outcomes at hangup; a minutely sweep and 30-minute stale fail catch the rest
TARGETING
Enroll by contact ids, the contacts-list filter (tags, status, search), or CSV upload; deduped per campaign

See how it works.

Start a call from HighLevel
Configure the Make an AI Call action and its workflow trigger.
Configure appointment tools
Attach availability, booking, notes and contact-update tools.
Assistable on the HighLevel marketplace
View the published calling, scheduling, agency and workflow features.

Your questions

Before you get started.

Can Assistable make outbound calls from HighLevel?

Yes. Add the Make an AI Call action to a HighLevel workflow, enter the assistant ID and configure a trigger such as a form submission, tag or scheduled time. The assistant needs a linked phone number and a funded account. Test the workflow on a contact before enabling it for your lead flow.

Can outbound agents qualify leads and book appointments?

Yes. Configure the agent’s qualification questions and attach connected-calendar tools to check availability and create a booking. The agent can also transfer a call to your team. Booking availability depends on the calendar connection, account type and configured tools.

Is Assistable suitable for database reactivation?

Assistable supports outbound follow-up to existing contacts through campaigns and HighLevel workflows. Select eligible contacts, configure the agent’s instructions, and use calling windows, pacing, retry limits and contact preference checks. Review the outcomes before expanding the campaign.

What do I need before a campaign can start?

At least one assistant with a traffic split summing to 100%, each assistant provisioned for voice, and an outbound number: either a number assigned per assistant or a shared number pool. The start endpoint validates all of this and returns a specific error for anything missing.

How are retries and do-not-call handled?

No-answer, busy, and failed calls requeue with your configured delay until max attempts is reached, and only dial inside the calling window. DND contacts are skipped before dialing, the account blacklist is checked on every call, and opt-outs and DNC blocks are counted in campaign analytics.

What does an outbound campaign cost?

Plans start with quarterly commitments. Your proposal confirms included usage and additional charges. Voice usage includes the chosen orchestration, text-to-speech and language-model components, plus applicable telephony and add-ons. Review the /pricing rate sheet together with your plan and setup costs.

Can I split traffic between two agent scripts?

Yes. Assign a traffic percent per assistant; splits must sum to 100 before start. Assignment is deficit-based per dial, so the realized split converges on your configuration even if you edit it mid-campaign, and per-assistant analytics show dialed and answered counts side by side.

“I'm generating a ton of leads every day and I don't want to hire an appointment setter. Assistable calls those leads and schedules the appointments and it does a great job.”
Adam LuckeyAssistable customer
4.6 on Trustpilot128.8K installs40M+ AI conversations

Let’s talk about your deployment.

Bring your workflow. We’ll work through the requirements together.

Talk to sales