emable Voice

AI calls that finish the next step. Approved, checked, written back.

An email API sends your messages; emable Voice places your calls: you bring the purpose and content of the call, emable Voice brings the number, the voice and the control layer. The AI says it is an AI first, every call has a recorded purpose and consent, a person or a person's rule approves it, and everything is logged.

Product film without sound. Fictional people and data.

A callback request waits in the CRM. A person approves the call, the AI says it is an AI, re-checks the offer and keeps to the approved script. The outcome is written back through allowed operations only, and every step is audited. Seven workflows, calls in English, Czech and German.

The problem

Your system knows the next step. Nobody gets to it in time.

Callback requests, approved recommendations, unfinished offers and service reports wait in the CRM. Calling them by hand is costly, uneven and hard to measure.

Generic voicebots can hold a conversation. They do not know your product, your permissions or the follow-up your system needs.

Open signalsToday, 08:30
  • Callback requestedPetra NovákováOffer 24812 daysNone
  • Next best action approvedKarel SvobodaHome cover review6 daysNone
  • Offer left unfinishedLucie BenešováStep 4 of 69 daysNone
  • Cover ends with leasingOndřej MalýEnds 31 Jan30 days leftNot planned
  • Fault reportedBuilding B, flat 12Leaking sinkSince 21:40Office closed
A generic voicebot does not know
  • your product
  • who may be contacted, and why
  • what to write back

How it works

From a key to calls that report back. Three steps, every one logged.

Your AI agent places the calls, emable Voice keeps them inside your rules. Want to hear it first? “Call me” in the app rings you in the browser, in a test workspace where nothing is dialled.

  1. Create a key and paste

    Create a key in emable and paste one ready text into your AI agent. The agent sets your company name itself and can place calls. Before calls go to real phones, you confirm your Czech company ID, your e-mail and your own phone. No documents.

    You and your agent
  2. Set your defaults and level

    A person sets the purpose, voice and consent basis once. The language follows the number's country. Then the person picks the agent's level.

    A person on your team
  3. Calls run and report back

    For each call the agent sends only the number and what the call is about. The AI says it is an AI first, and the outcome comes back with its audit trail.

    emable Voice

One call, step by step

Levels

Each agent gets a level. Only a person raises it.

Every agent starts at level 1. A person on your team decides how far each agent may go. An agent can never raise its own level.

Level 1
Ask me first

Every call waits for a person's approval. This is the default.

Level 2
Within my rules

Calls that fit your hours, purposes and daily limit go out. The rest wait for approval.

Level 3
Calls and SMS within my rules

Like level 2, for calls and SMS.

Four layers

Two we buy, one we own. One stays yours.

The phone network and the voice runtime are bought and kept behind adapters, so either can change. emable Voice owns the rules, the queue, the checks, the handover, the write-back and the measurement. Your CRM stays the source of truth.

The value is the completed task in your own system. Minutes and SMS are consumption, shown on a transparent bill.

Yours
Your CRM and people

Source of truth, allowed actions, handover to an advisor or manager

We own
emable Voice

Scripts, permissions, queue, limits, pre-action check, AI disclosure, handover, write-back, audit, metering

We buy
Voice runtime

Listening, interruptions, speech. Several engines behind one adapter.

We buy
Carrier

Phone numbers, SMS and the connection to the phone network

Use cases

Seven workflows, one way of working. Pick the one closest to yours.

Use case 1 of 7 · Offer callback

A client asks to be called about an offer.

The advisor approves. The AI fills in missing details or books a meeting, and the result is attached to the offer.

Channel
Outbound call, SMS
For
Brokers and distribution networks
Writes back
Offer fields, meeting, task for the advisor
Talk about this workflow

Use case 2 of 7 · Next best action

An approved recommendation gets followed up.

An advisor approves an opportunity your system suggests. The AI calls or texts, books a meeting or records the refusal and its reason.

Channel
Outbound call or SMS
For
Advisor networks with a recommendation engine
Writes back
Meeting, or refusal with reason and follow-up date
Talk about this workflow

Use case 3 of 7 · Unfinished offer

A saved offer stops halfway.

After an eligibility check, a reminder SMS goes out. If the client wants help, the AI calls and brings them back to the right step.

Channel
SMS, then a call
For
Insurance and comparison platforms
Writes back
Reminder sent, call outcome, return to the offer step
Talk about this workflow

Use case 4 of 7 · End of leasing or renewal

Cover tied to a leasing contract is about to end.

With a verified service reason, the AI arranges a consultation and a new comparison with a person. It does not sell on its own.

Channel
Outbound call
For
Distribution networks and leasing partners
Writes back
Consultation booked, comparison request for the advisor
Talk about this workflow

Use case 5 of 7 · Maintenance intake

A tenant calls to report a fault.

The AI answers, also outside office hours, takes a structured report, passes it to the property manager and confirms the visit by SMS.

Channel
Inbound call, SMS
For
Property managers
Writes back
Fault ticket, urgency, confirmed visit
Talk about this workflow

Use case 6 of 7 · CRM sales task

An approved sales task gets done.

A task is approved in the CRM. The AI makes the contact, records the result and creates the next task for the salesperson.

Channel
Outbound call
For
Sales teams working in a CRM
Writes back
Call note, next task, follow-up date
Talk about this workflow

Use case 7 of 7 · Viewing booking

A new-build enquiry turns into a viewing.

Someone asks to be contacted about a new flat. The AI qualifies the interest, books a viewing and hands over to the sales agent.

Channel
Outbound call
For
Developers and new-build sales teams
Writes back
Qualified lead, viewing slot, handover to the agent
Talk about this workflow

Governance

Rules come first. The call follows them.

Every contact runs inside limits you set. Each step is logged, so you can show who approved what, what the AI said and what it changed.

  • AI disclosureEvery call opens with an approved AI disclosure, so the client knows from the first sentence that an AI is speaking. If you record a call, the AI says that too. Recordings are deleted after 7 days.
  • Approval and purposeNo contact without a valid purpose and the approval of a person or of a rule a person set. The AI stays within the approved script.
  • Do-not-contact and call hoursOpt-outs, blocked numbers and allowed hours are checked before every attempt.
  • Checked again before the callCase status, price and consent are checked again just before the call or SMS goes out.
  • Recipient verificationCaller ID is not proof of identity. The person is verified before any sensitive detail.
  • Human handoverWhen unsure or out of scope, it ends the call politely and hands the case to the advisor or manager with a summary.
  • Allowed writes and audit trailOnly the operations you allow are written to your CRM. Every step is logged.
  • SMS previewEvery SMS shows its text, segment count and cost before it is sent.
Audit trail · Case 248116 events
  1. Signal receivedCallback requested on the offer pageSignal
  2. Pre-call checksConsent, call hours, do-not-contactPassed
  3. Approved by Martin KrálPurpose: offer callback, script v3Approved
  4. AI disclosurePlayed at the start of the callDone
  5. Re-check before quotingOffer 2481 still validPassed
  6. Recipient verifiedDate of birth matches the casePassed
  7. Write: update_offerMileage 12,000 kmAllowed
  8. Handover to Martin KrálClient asked about a discount: out of scopeHanded over
  9. SMS confirmationPreviewed, then sentSent

Showing 9 of 16 events

SMS previewTo Petra Nováková · number hidden

Hello Ms Nováková, your meeting with Martin Král is confirmed for Thu 20 Nov at 14:00. Reply STOP to opt out.

Characters
109
Segments
2 Unicode, accents
Cost
2 × your SMS rate
EditApprove and send
What it will not do
  • Sign insurance or investment contracts on its own
  • Run mass calling or marketing campaigns
  • Call a number just because it is public
  • Treat caller ID as proof of identity

Integrations and languages

Fits the systems you already run. In the languages your clients speak.

Engine A Engine B Engine C Adapter emableVoice

Provider-neutral runtime

Several voice engines, one adapter.

The engine that listens and speaks can change without rewriting your workflow, its rules or its integration.

+420 2•• ••• 101Broker network · callbacks +49 30 •••• ••77Insurer A · renewals +420 5•• ••• 330Property manager · fault line

Numbers per customer

Your own numbers, for one purpose each.

Each customer has its own phone numbers, held for that customer and purpose. Inbound calls and SMS land in the right place.

Phone or browser

In the browser today. Our own phone line is in testing.

Today a call runs as a voice session in the browser. Calls over our own phone line are built and in testing, with the same rules and the same write-back.

Your CRM read write Adapter or MCP

CRM adapters and MCP

Reads the case, writes only what you allow.

An adapter connects to your CRM or core system. Where your system offers MCP, we can connect through it. Your CRM stays the source of truth.

For developers

Your agent can call: one API key, one endpoint, a number to forward to.

We give you the number and the voice. What the call is about is up to you, like email.

Every call still opens with the AI disclosure, runs within your rules and is audited.

curl YOUR_VOICE_API_URL/v1/calls \
  -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" \
  -d '{ "to": { "e164": "+420700000000" }, "language": "en",
        "instructions": "You are calling to confirm the appointment tomorrow at 10:00.",
        "consentReference": "crm-consent-4821", "idempotencyKey": "visit-4821" }'

Languages

English, Czech and German.

Each language goes live on a workflow only after we test it on a real phone line: names, addresses, numbers and interruptions.

Voices: you choose the voice. Standard voices are included, premium voices are priced per minute on top.

  • EN

    “Hello, I'm an AI assistant calling for your advisor.”

  • CS

    „Dobrý den, jsem AI asistent a volám jménem vašeho poradce.“

  • DE

    „Guten Tag, ich bin ein KI-Assistent und rufe im Auftrag Ihres Beraters an.“

How we start

Start with one workflow. Measure it, then decide.

We begin with one paid validation of one workflow, on your system and under your rules.

  1. Step 1 · Scope

    One workflow, its signal and its rules

    We agree the signal, the purpose, the script, who may be contacted and what counts as done.

  2. Step 2 · Adapter

    Connect your CRM

    What we read, which operations we may write, and where a handover lands.

  3. Step 3 · Controlled pilot

    Approved contacts, agreed limits

    A limited pilot with approved contacts and agreed volumes. Every step is audited.

  4. Step 4 · Measured result

    Decide on evidence

    You see completed tasks, handovers and consumption, then decide on the next step. Another workflow, product or country is a new, separately agreed package.

Talk to us

Under a minute

Which workflow would you start with?

A person on our team replies with a proposed scope.

Questions

Before we start. The short answers.

Questions

Eight answers

Does the person know they are talking to an AI?

Yes. Every call opens with an approved AI disclosure, so the client knows from the first sentence that an AI is speaking. If you record a call, the AI says that too. Recordings are deleted after 7 days.

Talk this through with us
Can emable Voice call a list of numbers?

No. Every contact starts from a signal your system already has, such as a callback request, an approved next best action or a renewal. No contact happens without a valid purpose and the approval of a person or of a rule a person set. It does not run mass calling or marketing campaigns, and it does not call a number just because it is public.

Talk this through with us
What happens when the AI is unsure?

It ends the call politely and hands the case to the advisor or manager with a summary. The AI stays within the approved script, so a question outside it goes to a person.

Talk this through with us
What does it write to our CRM?

Only the operations you allow, and every step is logged. An adapter connects to your CRM or core system; where your system offers MCP, we can connect through it. Your CRM stays the source of truth.

Talk this through with us
What if the case changed after approval?

Case status, price and consent are checked again just before the call or SMS goes out. Opt-outs, blocked numbers and allowed hours are checked before every attempt. If something has changed, the contact is cancelled or moved.

Talk this through with us
Which languages, and does it call real phones today?

Calls run in English, Czech and German. Each language goes live on a workflow only after we test it on a real phone line. Today a call runs as a voice session in the browser. Calls over our own phone line are built and in testing.

Talk this through with us
Does it sell insurance or investments on its own?

No. It does not sign insurance or investment contracts on its own. It finishes the next step your system already knows, for example booking a meeting with the advisor, and hands anything out of scope to a person.

Talk this through with us
How do we start, and what does it cost?

We begin with one paid validation of one workflow, on your system and under your rules: scope, adapter, controlled pilot, measured result. Minutes and SMS are consumption, shown on a transparent bill. Another workflow, product or country is a new, separately agreed package.

Talk this through with us