Call scenarios

Call scenarios ready to launch, adapted to your company

A scenario tells the agent why it is calling (or why it is answering), what it may say and what it writes into your system at the end. Pick one below, listen to it in the widget, then we adapt it to your company.

Casa Pernuței (magazin online) call ended · outbound call · +40 3xx xxx 407

01:58

your agentBună ziua! Sunt Ioana, asistentul virtual al magazinului Casa Pernuței. Vorbesc cu doamna Cristina Dobre?

callerDa, eu sunt.

your agentVă sun pentru comanda de ieri, ca să o confirmăm înainte să plece coletul. Vă rețin doar puțin. Apelul este înregistrat.

callerA, da, spuneți.

your agentAveți două perne ortopedice și o husă de saltea, 160 pe 200. Totalul de plată la livrare este 412 lei, cu transportul inclus. E corect?

callerDa, așa e.

your agentAdresa pe care o am este strada Florilor 21, Ploiești. Mai trebuie adăugat ceva, bloc, scară, apartament?

callerDa, bloc C2, scara B, apartamentul 9. Am uitat să le scriu.

your agentAm notat: strada Florilor 21, bloc C2, scara B, apartamentul 9, Ploiești.

callerExact.

your agentCurierul vă sună înainte. Numărul de pe comandă, 07xx xxx 362, e cel bun?

callerDa, pe ăsta.

your agentPerfect. Coletul pleacă azi și ajunge, de obicei, în una, două zile lucrătoare. Pregătiți, vă rog, 412 lei pentru curier.

callerSe poate plăti cu cardul la curier?

your agentDa, curierul are terminal de card, puteți plăti cum preferați.

callerSuper. Mulțumesc că ați sunat.

your agentEu vă mulțumesc! V-am trimis și un SMS cu detaliile. O zi frumoasă!

Comandă #20517: CONFIRMATĂ ✓ · notă în ERP ✓ · SMS ✓
Adresă: Corectată: bl. C2, sc. B, ap. 9
Livrare: Pleacă azi · 1-2 zile lucrătoare

Simulated call with a fictional business and data.

Scenarios you can launch

Scenarios in production, each with its own dialogue

Each page shows the call flow step by step, what the agent confirms, what it does not do and what stays with your people. The dialogues in the widget are simulated, with fictional companies and data.

Cash-on-delivery order confirmation

The agent calls the customer, confirms address, products and amount, then writes the result to your ERP. It retries at set times; unanswered calls are free.

Anatomy of a scenario

How a call scenario is built

Every scenario has the same five parts. What differs from one company to another is what goes into them.

1. The goal One sentence: what must have happened by the end of the call. "The order is confirmed." "The patient has an appointment." "The case has a list of missing documents." If the goal cannot be said in one sentence, the scenario is split in two.

2. The dialogue How the agent introduces itself, what it asks, in what order and in which words. The texts are written in your company's voice, without jargon and with short sentences. The agent replies almost instantly, so the conversation flows.

3. The rules What it may and may not do. What information it can give, which documents it answers from, when it politely ends the call, when it hands over to a person. This is also where calling windows, the redial cadence and the "do not call me again" request, which is respected, come in.

4. The outcome Every call ends with a clear outcome, written where you already work: ERP, CRM, calendar. The recording, transcript and summary stay in the portal, so you can check any call.

5. The after-call message If the call needs something in writing, the agent sends an SMS, WhatsApp message or email: the confirmation, the list of documents, the clinic's address. The person has it all in writing, not just in memory.

Call direction

Inbound or outbound calls: what changes

The same platform does both, but the scenarios are built differently.

Criterion	What you are tracking	Inbound calls
Who starts the conversation	The customer. The agent answers, introduces itself and finds out the reason.	The agent. It confirms it is speaking to the right person and says straight away why it is calling.
The hardest part	Quickly understanding what the person wants, however they put it.	Not to intrude: a suitable time, a short call, respect for a refusal.
Extra rules	What it must not promise, when to transfer or take a message.	Calling windows, redial cadence, avoiding duplicate calls.
When nobody answers	Not applicable: the agent answers 24/7.	The call is not charged. The agent tries again at the set times.
Examples	Flower shop orders, clinic appointments, reception (pages in Romanian: flower shop, clinic, reception)	Cash-on-delivery confirmation, document recovery (in Romanian: document recovery)

300+ scenarios

We start from a template, not from scratch

The platform has more than 300 call scenarios, which we use as templates. They are not closed products: we adapt them to your company, your texts and your systems.

Cannot find your field on the pages here? The practical rule is simple: if a call can be described as a goal, a dialogue, rules and an outcome, it can be built. We will tell you honestly if something is not worth automating.

Frequently asked questions

What is a call scenario?

A complete plan for a phone conversation, with a goal, dialogue, rules, an outcome and an after-call message. The agent follows it but speaks naturally and does not read out a script.

Can I ask for a scenario that is not on the site?

Yes. Tell us what must happen at the end of the call. We start from a similar template and adapt it. If something does not suit a voice agent, we tell you from the outset.

How long until a scenario goes live?

In our test, the technical setup of an agent took about 55 seconds. We then agree the texts and rules together, and the time depends on how clear you are about what you want.

Can the agent handle both inbound and outbound calls?

Yes, both. The scenarios differ: for inbound calls, understanding the request matters most; for outbound calls, the cadence and respect for the person called matter most.

What happens to calls nobody answers?

For outbound calls, if nobody answers, the call is not charged. Voicemail is charged as a normal minute. Details are on the pricing page.