Introduction

Talkif turns a written description of a conversation into a phone agent that can hold that conversation with real people, on real phone lines, in real time. You describe who the agent is and what it should achieve; Talkif handles the telephony, the speech recognition, the language model, the voice, and the billing — and gives you back a transcript, a recording, and an exact cost for every call.

It’s built for teams who need calls answered or placed at scale — appointment reminders, lead qualification, support triage, surveys, order confirmations — without building a voice stack of their own.

The four things every call depends on

Everything in Talkif reduces to four objects. Once you can name them, the rest of the product is just ways to create, connect, and observe them.

A call always runs the flow’s published version; every second of it is paid from credits.

A flow does nothing on its own. A number with no flow rejects inbound calls. A call cannot start below the $1.00 minimum balance. Most “why isn’t this working?” questions are one of those three sentences.

Agents, prompts and providers — the part worth understanding first

A flow is not a script. The agent decides each reply itself, from two prompts:

• The System Prompt is the call’s persona — who the agent is, its tone, its hard limits. It lives on the entry agent (the Main Agent) only and stays in force for the whole call, even after the conversation moves to other agents.
• The Agent Prompt is that agent’s job — what to find out, what to do, when to move on. Every agent has one; it applies only while the conversation is on that agent.

A single-agent flow is one Main Agent with both prompts. A multi-agent flow splits the work — “greet and qualify”, then “book the slot”, then “confirm and close” — with each agent carrying only the instructions for its step. That keeps prompts short, which is the single biggest lever on how well a voice agent performs.

Prompts are dynamic

Both prompts are templates, resolved when the call starts — not when you publish. Anything Talkif knows about the call can be dropped in with {{…}}:

You are calling {{default contact.firstName "the customer"}} from {{contact.company}}.
Today is {{formatDate system.date "long"}}; it is {{system.time}} in the caller's timezone.
{{#ifExists contact.notes}}Background from our CRM: {{contact.notes}}{{/ifExists}}

Helpers cover the usual gaps: default for missing values, formatDate, join for lists, #ifExists / #if with eq, and, includes for conditional lines. The full reference is in Write prompts.

Three providers do the actual work on every turn:

The available vendors and models are listed live from the platform — see Models and voices. Choosing them is covered in Choose models and voices.

Two ways to work with Talkif

Where Talkif runs

Talkif runs in two regions — EU (Frankfurt) and US (Virginia) — and serves both api.talkif.ai and call media from whichever is closer to the caller. You don’t pick a region per call; you may care about it when bringing your own carrier, where the SIP edge is chosen from your carrier’s location — see Bring your own SIP trunk.

Where to go next

Then, by what you’re doing