The same Voka assistant that answers your phone can place calls for you: confirmation and reminder calls you start from the portal, a CSV, the API or n8n, plus callbacks and follow-ups.
Calls come from your Voka number, use the minutes on your plan and land in your dashboard with a recording, transcript and summary.
Dana confirmed her Thursday 2:30 appointment and asked to add a gloss treatment.
Three ways to start
Place a call however you already work
Whether you want to click a button, upload a spreadsheet or wire it into your own systems, the call is the same: your assistant, your number, your instructions.
01
No code
From the portal
Open the Outbound Calling page, pick an assistant and place a single call. Or upload a CSV and Voka places the calls one by one.
A to_number column, plus any columns you want
Your extra columns become variables, like name or appointment time
Calls go out one at a time, not all at once
02
For developers
From the Voka API
Send POST /api/v1/outbound-calls with an API key from your account. Place the call now or give it a future time.
Bearer key that starts with voka_live_
Optional external_id stops the same call going out twice
List calls and fetch transcripts from the same API
03
Workflows
From n8n, Zapier or Make
Use the Voka n8n node "Place Outbound Call", or an HTTP request / webhook step in Zapier or Make that calls the API.
n8n has a native Voka node
Zapier and Make use their HTTP / webhook step
Trigger it from a form, your CRM or a spreadsheet row
Outbound works best for your own customers and leads: short, useful calls that someone on your team would otherwise have to make.
Appointment confirmation calls
Call tomorrow’s bookings to confirm they are still coming. Pass the name and time as variables so the assistant says them.
“Hi Dana, this is Bloom Salon calling to confirm your 2:30 cut with Maria tomorrow.”
Reminder calls
For clients who ignore texts, a short reminder call from your Voka number. You trigger it from the portal, a CSV list, the API or your workflow; Voka does not send reminders on its own.
“Just a reminder that your cleaning is Thursday at 9. Call us back if you need to move it.”
Returning callback requests
When your Call Backs queue fills up after a busy day, have the assistant return the simple ones and pass the rest to you.
“You asked us to call you back about pricing for a deep clean. I can go through it now.”
Follow-ups
Check in after a visit or a quote. The transcript and summary tell you who wants a next step.
“Following up on the estimate we sent Monday. Any questions I can answer?”
“We have an opening” calls
A cancellation just freed up a slot. Call the people who wanted an earlier time, or clients you have not seen in a while.
“We just had a 4 pm open up today. Would you like it?”
Speed to lead, from your workflow
When a web form or CRM record comes in, your n8n or Zapier workflow calls the API and the assistant rings the lead while they are still interested.
Form submitted → your workflow → POST /api/v1/outbound-calls
For developers
One request places one call
Create an API key in the portal, then send the assistant, the number and anything you want it to know. Put {{placeholders}} in your assistant's instructions and fill them with variables.
assistant_idrequired
Which of your assistants makes the call.
torequired
The number to call, in E.164 format (+15551234567).
from
One of your active Voka numbers. Defaults to the assistant’s number.
scheduled_at
A future time to place the call. Leave it out to call right away.
variables
Values for the {{placeholders}} in your assistant’s instructions.
external_id
Your own ID for the call. Sending it twice returns 409, so retries cannot double-dial.
metadata
Anything you want handed back in the completion webhook.
Outbound calls show up in History next to your inbound calls, with the same recording, transcript and summary. When a call ends, Voka can tell your systems too.
Recording
Listen back to any outbound call from History, next to your inbound calls.
Transcript
The full conversation in text, in the dashboard or from the transcript endpoint.
AI summary and insights
A short summary of what happened, plus any custom insights you have set up.
Webhook or email
An outbound_call.completed POST with duration, cost, recording URL, conversation ID and your metadata. Or an email, or both. Sent once and not signed. A scheduled call can’t be cancelled.
Guardrails
Limits that are on by default
API keys that place calls can cost money, so every key starts with limits. They protect you from a broken workflow, not from calling rules.
$50
Daily spend cap per API key
The default. It caps what a runaway loop can spend in a day.
US + CA
Country allowlist
By default, calls can only go to US and Canadian numbers.
60/min
API rate limit
API requests per minute, so a runaway script gets stopped early.
409
Duplicate protection
Reuse an external_id and the second request is refused instead of dialed.
Consent and calling rules are yours
Voka places the calls you ask for. It does not check consent, scrub do-not-call lists or enforce quiet hours. Only call people who have agreed to hear from you, and follow the TCPA and any state rules that apply to your business.
FAQ
Outbound call questions
Can an AI receptionist make outbound calls?
Voka’s can. The same assistant that answers your phone can place calls, and you decide when: start them from the Outbound Calling page in the portal (one number, or a CSV list it works through one call at a time), from the Voka API with POST /api/v1/outbound-calls, or from the Voka n8n node. Zapier and Make work through an HTTP request or webhook step that calls the API. Voka does not place reminder or follow-up calls on its own schedule; every call starts from something you trigger.
Is outbound calling a separate cost?
No. Outbound calls use the same minutes as your plan, at the same rate. There is no separate outbound fee.
Can I try outbound calls on the free trial?
Yes. During the trial you can place immediate outbound calls from your trial number. Those minutes count toward the 100 trial minutes.
What number shows up on the caller ID?
Your Voka number. If you have more than one active Voka number you can choose which one with the from field; otherwise it uses the assistant’s number.
What happens if the call goes to voicemail?
Voka does not detect voicemail. Write your assistant’s instructions for it: for example, “If you reach voicemail, leave a short message with our number and hang up.” The recording and transcript show you what happened on each call.
Who is responsible for consent and calling rules?
You are. Voka places the calls you ask for; it does not check consent, do-not-call lists or quiet hours for you. Only call people who have agreed to hear from you, and follow the TCPA, state rules and do-not-call requirements that apply to your business.
Does Voka retry calls that are not answered?
No. Each request places one call. If you want a second attempt, send another request, for example from your n8n or Zapier workflow after checking the result.
Can I personalize what the assistant says on each call?
Yes. Put placeholders like {{customer_name}} or {{appointment_time}} in your assistant’s instructions, then pass the values in the variables field, or as extra columns in your CSV upload.
How do I know how a call went?
Every outbound call gets a recording, a transcript and an AI summary in your dashboard, alongside your inbound calls. You can also get an outbound_call.completed webhook, an email, or both when the call ends, and list calls through the API filtered by status, assistant or external_id. The webhook is sent once and is not signed, and a scheduled call can’t be cancelled.
Is this a dialer for cold-calling campaigns?
No. There is no campaign manager, lead list or auto-dialer. It is built for calls to your own customers and leads: confirmations, reminders, callbacks and follow-ups that you start from the portal, the API or your own workflow.
Answer the calls coming in. Make the ones going out.
One assistant, one number, one set of minutes. Set it up, place a test call to your own phone and hear it for yourself.