Concepts
Runtime
How Diska executes a call from start to finish.
When a call arrives or is initiated, the runtime loads the published version of the Flow and executes nodes in sequence.
Call lifecycle
Created → Active → Completed / Failed / Cancelled
Channels
| Channel | Description |
|---|---|
browser_demo | Test call in the browser via WebRTC. |
phone | Real phone call (in preparation). |
whatsapp | Coming soon. |
web_chat | Coming soon. |
Execution phases
- Before conversation: pre-call actions (for example, load context).
- Greeting: the agent's initial contact.
- Conversation: AI listens, thinks and responds.
- Branch / Message / Action: logic, static messages or tools.
- End: ends the call with a farewell and a reason.
- After conversation: post-call actions (summaries, SMS, notes).
Call estimator
At each step the runtime decides:
- Whether to continue the conversation.
- Whether to collect variables.
- Whether to trigger an action.
- Whether to terminate.
The execution result is recorded in Histories, including transcriptions, tool calls and executed actions.