> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ringg.ai/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> To search or read these docs, connect the Ringg docs MCP server at https://docs.ringg.ai/mcp (no key needed; tools search_ringg_ai and query_docs_filesystem_ringg_ai) instead of browsing pages one by one. Setup for each client: https://docs.ringg.ai/resources/mcp-server/docs-mcp-server/mcp-for-ai-assistants.md
> The dashboard labels agents "Assistants"; these docs say "agent". Both mean the same object, identified by agent_id.
> API base URL: https://prod-api.ringg.ai/ca/api/v0. Send the workspace API key in the X-API-KEY header, from server-side code only.
> Placing a call dials a real phone number and spends credits. Confirm the number with the user before calling.
> To act on a Ringg workspace (place calls, edit agents, read transcripts), use the separate Ringg workspace MCP server at https://mcp.ringg.ai/mcp: https://docs.ringg.ai/resources/mcp-server/workspace-mcp-server/overview.md
# Multi-prompt agents
> Build a Ringg AI multi-prompt agent: when to use one, create it, find your way around the canvas, and read an example flow from greeting to transfer.
Choose a multi-prompt agent when a call has strict steps or branches, such as a keypad menu, OTP capture or an API lookup before the next question. For most calls, a [single-prompt agent](/documentation/build-agents/agents/agent-types#agent-types-by-build-style) with one sectioned prompt is simpler to build and maintain.
In the dashboard: **Sidebar → Assistants → Create agent → Multi Prompt**. The dashboard calls these agents **Multi Prompt** and lists them under the **Multi-node** filter on the Agents page (multi-node is the internal name).
Multi-prompt agents support voice and web calls, not WhatsApp: the **Multi Prompt** card is not shown on the **WhatsApp** tab, and **Convert to multi-prompt** is not offered for WhatsApp agents.
## Before you start
Optional: for Agent nodes that answer from your documents.
Optional: on-call tools for Agent nodes, pre-call and post-call tools for the agent.
## Create a multi-prompt agent
On the Agents page (listed under **Assistants** in the sidebar), click **Create agent**. The **Create Assistant** dialog opens.
On the **Outbound**, **Inbound** or **Webcall** tab, under **Create from scratch**, click **Multi Prompt** ("Create assistant from scratch for complex workflows.").
There is no form. The dashboard creates an agent named **Untitled Workflow** with a **Start** node and the custom variables `callee_name` and `mobile_number`, then opens the canvas. Whichever tab you start from, the new agent is an outbound agent.
You see "Workflow created successfully" and the canvas with a single **Start** node.
You can also turn an existing single-prompt agent into a multi-prompt one. See [Convert a single-prompt agent](/documentation/build-agents/agents/multi-prompt-agents/test-and-convert#convert-a-single-prompt-agent).
## The canvas
The editor has two parts. The canvas on the left holds the nodes and their connections. The panel on the right shows the settings of the selected node, or **Global Settings** when nothing is selected; drag the divider to resize it.
The video adds a node, opens a node's settings, then opens Global Settings.
* **Add a node:** click the dot on a node's output. A picker lists the node types you can add there ([connection rules](/documentation/build-agents/agents/multi-prompt-agents/node-types-and-connections#connection-rules)).
* **Drag to add:** drag from an output dot to empty canvas. A preview of the next node follows the cursor; press **Tab** to switch its type, then release to place it. Drag onto an existing node to connect the two.
* **Reuse an Agent node:** once the flow has an Agent node, **Agent** opens a submenu with **Blank agent** and **From existing** (copies another Agent node's setup).
* **Name a node:** click the name or the description at the top of its panel and type. **Enter** saves the name (**Cmd/Ctrl+Enter** for the description), **Esc** cancels. The name is what you see in the test summary, in the call's path in [Logs](/documentation/monitor/logs) and from the [MCP server](/resources/mcp-server/workspace-mcp-server/tool-reference), so name nodes by what they do: "Greet and confirm identity", "Eligible?".
* **Canvas controls:** **Zoom in**, **Zoom out**, **Fit to screen**, **Organize nodes** (auto-layout left to right) and **Hand tool (H)** for panning.
* **Delete:** each node has a delete action with a confirmation. To delete several, drag a box around them and press **Delete** or **Backspace**; **Delete selection** asks you to confirm. The **Start** node cannot be deleted.
Most node panels have their own **Save** button, which reads **Saved** once the node has no pending edits. Saved node changes go into the agent's draft; they reach callers only when you [publish](/documentation/build-agents/test-and-improve/drafts-and-versions#publish-changes-on-a-multi-prompt-agent).
## Example flow
A rescheduling call, built from the node types below. Edge labels are the router's conditions and the nodes' outputs.
```mermaid theme={null}
flowchart TD
S([Start]) --> A[Agent: greet and confirm identity]
A --> R{LLM Router}
R -->|Wants to reschedule| C[Collect: PIN code]
R -->|Not interested| E([End])
C -->|Captured| X[Action: book slot]
C -->|Failed| E
X -->|On success| K[Speak: confirm the new slot]
X -->|On failure| E
K --> E
```
## Troubleshooting
The last publish found problems in the flow. Click **Review issues** and open each issue to jump to the node or connection that needs fixing, then [publish again](/documentation/build-agents/test-and-improve/drafts-and-versions#publish-changes-on-a-multi-prompt-agent).
## Next steps
Drafts, publishing, versions and traffic split.
Pre-call, on-call and post-call tools.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
Most node panels have their own **Save** button, which reads **Saved** once the node has no pending edits. Saved node changes go into the agent's draft; they reach callers only when you [publish](/documentation/build-agents/test-and-improve/drafts-and-versions#publish-changes-on-a-multi-prompt-agent).
## Example flow
A rescheduling call, built from the node types below. Edge labels are the router's conditions and the nodes' outputs.
```mermaid theme={null}
flowchart TD
S([Start]) --> A[Agent: greet and confirm identity]
A --> R{LLM Router}
R -->|Wants to reschedule| C[Collect: PIN code]
R -->|Not interested| E([End])
C -->|Captured| X[Action: book slot]
C -->|Failed| E
X -->|On success| K[Speak: confirm the new slot]
X -->|On failure| E
K --> E
```
## Troubleshooting