Custom AI · Direction 00Outbound voice · Gemini Live · Telegram & telephony
An AI agent that makes the calls.
Custom AI Call dials your leads, talks to them by voice and follows a script you drew as a graph. Every detour returns to the script, every call leaves a transcript, and only the person on the line hangs up.
Web
ccustom.ai/call
Panel
call.ccustom.ai
contact@ccustom.ai
The problem
A phone call is the step that moves things — and the step nobody has time for
01
Missed calls
A lead who is not called back the same hour calls the next place. Callbacks queue behind whatever the person at the desk is doing.
02
The cost of an operator
Salary, taxes, training, turnover, a supervisor — for work that is forty near-identical conversations a day, each read from a script.
03
No-shows
A booking that is not confirmed the day before is a chair that stays empty. A reminder by text is ignored; a voice asking “are we on?” is answered.
What it is
An outbound AI voice agent, with the script as a drawing
VOICE
Speaks and listens at once
Gemini Live native audio: no speech-to-text-to-speech chain. It stops when the person starts, and its first phrase typically comes under three seconds after “hello”.
SCRIPT
A graph, compiled to a prompt
Blocks for what the agent says and asks, arrows for the answers. The prompt is compiled from the graph — there is no second copy to drift from what you see.
RULES
Laws in code, not in prose
Consent gate, honesty on a direct question, hard limits, quiet hours, transcript always, only the person hangs up. The engine refuses to dial when one is broken.
Direction 00 inside Custom AI
The app already runs the business. Call is its outbound layer.
Custom AI is one app for calendar, clients, finance, self-booking and a live voice assistant, adapted to more than thirty verticals. Call adds the direction that goes out: the same clients, the same calendar, the same voice — now dialing.
How it works
Four steps, one panel
01
Leads in
CSV, Google Sheets, a webhook, or your CRM. Consent and do-not-call status travel with each row and are checked before every dial.
02
Script as a graph
Blocks for what the agent says and asks, arrows for what the person answers. Or describe the call in chat and the setup agent draws it.
03
The agent calls
Inside the call window, under the daily and hourly caps. It speaks, listens, meets objections and returns to the script from where it left off.
04
Outcome, follow-up, CRM
Result, collected fields and the transcript land in the panel. The follow-up goes by Telegram, WhatsApp, SMS or email; the CRM row is updated.
The script graphsales template · 11 blocks · 13 arrows
A script you can see
Block types
Eight kinds of block, one kind of arrow
start
Start
The first phrase after the person's “hello”. Exactly one per script.
say
Say
The agent says a line and moves on along the single arrow out.
ask
Ask
A question. Each expected answer is its own labelled arrow; an unclear answer is re-asked in other words.
branch
Branch
A fork on intent with no line of its own — who is on the line, yes or no, which of three.
objection
Objection
Trigger phrases, an answer, and an arrow back into the script. Reachable from anywhere in the call.
goal
Goal
The outcome is reached — consent, a booking, a date. It is recorded with the fields collected.
transfer
Transfer
Hand over to a person: the agent warns, then calls the transfer tool.
end
End
The agent says goodbye in one phrase and goes quiet. The person hangs up.
Directions and templates
Seven reasons to call, each with a graph to start from
| Direction | What the call does | Tone | Collects |
|---|---|---|---|
| Sales | Cold or warm call with an offer and a close on the next step. | warm-confident | role · consent · channel |
| Appointment booking | Invite the client, agree on a time, confirm the booking. | friendly-brief | date · time · booking |
| Win-back | The client has not visited in a while — remind them and give a reason. | warm-personal | reason · date |
| Confirmation | Confirm a booking, an order or a delivery. Short and clear. | brief-polite | confirmed · date · time |
| Survey / NPS | A few questions after a visit or purchase: score and comment. | neutral-curious | nps · feedback |
| Payment reminder | A calm reminder about an overdue balance and a date agreement. | calm-firm | pay_date · promise_date |
| Support callback | Call back on a ticket, clarify, resolve or hand over. | patient-helpful | issue · details · resolved |
| Custom flow | An empty graph — draw the conversation from scratch or ask the setup agent. | — | — |
The AI setup agent
Say what to change; watch it change
Make the greeting shorter and add a price objection.
Two changes. The greeting drops the company clause; a new objection block catches “expensive / no budget / how much” and returns to the interest question.
- update_node start say: "Hi, this is {agent}. Owner or front desk?"
- add_node obj_price type: objection · triggers: ["expensive","no budget","how much"]
- add_edge obj_price → q_interest
Undo the first one.
Done — the greeting is back to the template text. The objection block stays.
- Operations, not rewrites. The agent returns a list of add / update / delete on nodes and edges. The panel applies them one by one.
- Every change is visible and undoable. It cannot erase half a script by accident; the start block cannot be deleted at all.
- The same validator runs after. One start, no dead ends, no unreachable blocks, every objection returns.
- It reads the graph as you see it — numbered steps, the same numbers the compiled prompt uses.
Agent settings
Who calls, how, and how much
| Setting | Default |
|---|---|
| Name, gender, voice | Kali · female · Aoede |
| Language, tone | uk · warm-confident |
| Honesty mode | reactive | proactive |
| Hang-up policy | client_only |
| Facts / never-say lists | whitelist · blacklist |
| Fillers, questions in a row | on · max 2 |
| Limit | Default |
|---|---|
| Calls per day / per hour, per line | 40 · 12 |
| Attempts per lead, cooldown | 3 · 24 h |
| Concurrency, max call length | 1 · 600 s |
| Quiet hours | 20:00 → 10:00 · Europe/Kyiv |
| Call window | 10:00 → 19:00 · Mon–Fri |
| Recording | off |
House laws
Six rules the engine enforces, not the prompt
- Consent is code, not intention.
No number is dialed except through the compliance gate. Consent, DNC, quiet hours and number health are checked there; the test mode uses the same door.
- Honesty on a direct question.
“Is this a robot?” — yes, an AI assistant, first word. Calling itself human is impossible; the prompt does not assemble without the rule.
- Limits are hard.
Day, hour, attempts, cooldown, quiet hours. Going over is a refusal to dial, not a line in a log.
- A transcript is always written.
Even when the call dies on the first second. Every outcome is derived from it.
- Only the person hangs up.
After the goodbye the agent goes quiet. No tool and no rule ends the call; a dead-line timer and a maximum length are the only fuses.
- Every detour returns to the script.
An objection, “later”, “text me” — each branch ends with a choice of two actions or a return to where the talk broke off.
Live call and transcript
You watch the call as it runs
- The transcript runs while the line is open. Who is speaking, which block the agent is in, what was collected so far.
- Step mode. One call at a time, started on your button — for the first day with a new script.
- Outcome is derived from the transcript after the call: goal or not, fields, objections met, the reason it ended.
- Take over. A transfer block hands the line to an operator; the owner can close a line by hand from the panel.
Campaigns and leads
A queue you can read, and every attempt with its reason
| Lead | Consent | Attempts | Last result | Next |
|---|---|---|---|---|
| Studio Nika · +380 ··· 41 | web form · 03.09 | 1 / 3 | goal · consent · link sent by Telegram | done |
| Dr. Melnyk · +380 ··· 07 | CRM · 28.08 | 2 / 3 | later · callback 14:30 | 14:30 |
| Auto Plus · +380 ··· 19 | CSV · 01.09 | 1 / 3 | objection “busy” · returned to Later | tomorrow · 10:00 |
| Lingua School · +380 ··· 88 | — | 0 / 3 | not dialed: no consent flag | blocked |
| Bakery No. 3 · +380 ··· 52 | sheet · 30.08 | 3 / 3 | no answer × 3 | closed |
| O. Kovalenko · +380 ··· 63 | DNC | — | asked not to be called · 02.09 · on the list | never |
Illustrative rows. Import, dedupe by phone, consent flags, DNC list; a queue per campaign; the reason for every attempt and every refusal to dial.
Analytics
The funnel, the cost of a result, the objections that came up
Shape is illustrative. Your numbers come from your calls.
- Cost per result. Minutes of voice and line divided by goals reached — per campaign, per script, per day.
- Minutes per outcome. How long a goal takes, how long a “no” takes; where calls are being lost.
- Objections that came up most — and whether the block for each one returned the call to the script.
- Line health. Answer rate per number, so a tired line rests before it burns.
Integrations
Your lines, your leads, your CRM
Telephony
Leads and CRM
Follow-up
Your own engine
Self-hosted engine
The engine on your server, the panel in the cloud
Security and compliance
What stays where, and who can see it
- Audio and transcripts stay on the engine. Self-hosted: on your server. Hosted: in your project's storage, exportable and deletable on request.
- Secrets are never printed. Logs, the panel and alerts carry the variable's name, not its value.
- Roles. Owner, operator, viewer. Every change to a script or a limit is logged with who and when.
- Retention is a setting, per workspace; the default keeps transcripts 90 days.
- Consent and DNC are enforced in code. A lead without a consent flag is not dialed; “don't call again” is written to the list during the call.
- EU AI Act, art. 50. Proactive honesty mode opens the call with the disclosure; reactive mode answers when asked. The setting is shown on every campaign.
- Recording is off by default and, where enabled, announced in the greeting.
- Every outbound call has a timeout and a named failure. If Gemini, Telegram or the trunk is down, the panel says which.
For whom
Anywhere a call moves things and a person is too expensive to make forty a day
- Call centres — the first pass over a list: qualification, callback time, transfer of the warm ones to an operator.
- Salons and clinics — confirmations the day before, win-back of clients who stopped coming, the post-visit question.
- Schools and courses — calling back every application, trial-lesson booking, reminders before the group starts.
- Logistics and dispatch — confirming a delivery window, a driver's ETA to the consignee, a status the customer asked for.
- E-commerce — order confirmation, an abandoned cart with a question rather than a coupon, the review call.
- Collections — a calm reminder, a date agreed and written down, a transfer when the sum is disputed.
Pricing approach
Monthly for the panel and the agent, per-minute for the voice and the line
01
Start
One business, one line, one script at a time.
per-minute + monthly
quoted for your volume
- 1 agent, 1 active campaign
- All templates and the graph editor
- Telegram calls or one telephony provider
- CSV and Sheets, follow-up by Telegram
02
Team
Several people, several campaigns, a CRM to keep in step.
per-minute + monthly
quoted for your volume
- Up to 5 agents, parallel campaigns
- AI setup agent with history
- Any telephony, lines with rotation
- Bitrix24, HubSpot, amoCRM; WhatsApp, SMS, email
03
Call-centre
Volume, your own numbers and your own server.
per-minute + monthly
quoted for your volume
- Unlimited agents and campaigns
- Self-hosted engine, paired by key
- SIP trunk, number pool, rotation
- Retention and export to your terms
Roadmap
What is here, and what is next
Now · Q3 2026
Outbound, one panel
Script graph and setup agent, seven direction templates, Telegram calls and telephony providers, campaigns, live transcript, outcomes, analytics, self-hosted engine.
Q4 2026
Inbound, WhatsApp voice, multi-agent
The same agent answers the line it calls from. Voice calls over WhatsApp Business. Several agents on one campaign with a shared queue and a supervisor view.
2027
Deeper into the app
Campaigns started from a client filter in Custom AI; outcomes written straight to the client card; voice follow-up on a booking that was not confirmed.
Custom AI · Direction 00
Hear it call.
Send a line about what you sell and whom you call. We set up a script from a template and call you — you will hear the agent, see the transcript and get the outcome, as your clients would.
contact@ccustom.ai
Panel
call.ccustom.ai
Web
ccustom.ai/call