Concepts
Prompt Builder
Drive an agent with a single system instruction instead of a visual Flow.
Diska agents run in one of two editing modes. The Flow Builder models the conversation as a graph of nodes; the Prompt Builder drives the whole conversation from a single system instruction. A blank agent (created without a template) opens in the Prompt Builder — it is the fastest way to get a working agent.
What you configure
| Setting | Effect on the call |
|---|---|
| System instruction | The persona, objective, tone and limits — the model follows it for the entire call. |
| Greeting | How the call opens: the agent speaks your configured message first, or waits for the caller to speak. |
| Voice | The voice the agent speaks with, resolved server-side from the published version. |
| Language | The language the agent speaks and is transcribed in. |
| Personality and objections | Appended to the instruction as dedicated sections. |
| Knowledge bases | Attached bases are searchable mid-call; see Knowledge Base. |
| Actions | Bookings, SMS and custom API calls the model may trigger during or after the call. |
The prompt editor autosaves as you type. Changes accumulate in a draft; live calls always use the published version, so nothing you edit affects callers until you publish.
Writing a good instruction
- State who the agent is, what it must achieve on this call, and what it must never do.
- Keep it in the language the agent speaks.
- Prefer short, imperative rules over long prose — the model follows lists better than paragraphs.
- Do not paste knowledge documents into the prompt; attach a knowledge base instead, so retrieval stays scoped and up to date.
Testing
Use the Test panel for a real browser voice call (draft or published version), or the Chat tab for a quick text exchange. See Test the agent.
If the conversation needs branching, data collection with validation, or different behavior per step, switch to the Flow Builder — the Prompt Builder trades that control for speed.