Flow builder

The agent scenario, drawn as a flow that the whole team can read

In the Kallina builder, an agent becomes a scheme: what it asks, what it checks, what tool it calls, when it transfers and what happens after the call. Changes apply to subsequent conversations.

Flow builder
Active flow
Incoming call
Caller intent
Appointment
Question response
Transfer to operator
Interface example

What a flow is built from

Role and limits

Who the agent is, how it speaks, what it is allowed to promise and what it is not. The text is written once and applied throughout the entire flow.

  • Greeting and introduction.
  • Tone and length of the replies.
  • Prohibited topics.

The documents it responds from

Price lists, terms, frequently asked questions. The agent responds from them, not from general memory.

Actions during the call

Webhooks and integrations the agent calls while speaking: looks for a slot, checks an order, creates a lead.

Contact record
Synced
Call endedCRM
Result
Appointment moved
Call language
Romanian
Summary
The client asked for another day; the agent suggested Friday.
Next step
Confirmation SMS
Interface example

Handoff to a human

The conditions under which the call is transferred to an operator and the number or queue it reaches.

What leaves the call

The extracted fields, summary and result are sent to the CRM, into the table or to a webhook of yours.

Live transcription
In conversation
AgentGood day! How can I help you?
ClientI would like to move Thursday’s appointment.
AgentCertainly. Would Friday morning suit you?
ClientYes, Friday is fine.
Interface example

A small flow, read from top to bottom

Illustrative example: checking the status of a request submitted earlier.

1. Identification
The agent asks for the request number or the phone number used to submit it.
2. Tool
A webhook looks for the request in your system and returns its status.
3. Branching
If the request is ready, the agent says what comes next. If a document is missing, it says which one. If it cannot find it, it transfers.
4. After the call
The result and summary are written to that request, so a colleague can see that the person called.

Who works in the builder

  • Your team

    Change the texts, questions and knowledge base without a programmer.

  • Your programmer

    Connects webhooks to internal systems and receives call results via API.

  • Us

    At launch, we build the first flow together with you and test it on real calls.

Frequently asked questions

Do we need to know programming?

For texts, questions and the knowledge base, no. For a tool that reads from an internal system, a webhook is needed, which is made by a programmer or by us.

Can we test a flow before putting it on the real number?

Yes. The agent can be called or used from the browser before being connected to the public number.

What happens to ongoing calls when we modify the flow?

The change is applied to conversations that start after saving.

Can an agent have multiple flows?

An agent has a main path with branches. For very different roles, for example reception and campaigns, we recommend separate agents.

We design the first flow for your case

Bring a scenario that people handle by phone today.