> ## 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

# Post-call tools

> Run Ringg AI tools after a call ends: when each post-call tool fires, what data it can read, and how callback scheduling calls the person back.

## Post-call tools

You don't pick when a post-call tool runs: Ringg derives its trigger point from the data it references.

| Trigger point | Runs when | Tool can read |
| - | - | - |
| `call_completed` | The call ends | `custom_args`, `call_data`, `tool_output` |
| `platform_analysis` | Platform analysis is done | Also `platform_analysis` |
| `client_analysis` | Advanced Analysis is done | Also `platform_analysis` and `client_analysis` |

A tool that reads `call_data.recording_url` waits until the recording is ready. When the call never connected, it runs without waiting and the URL is empty.

### Callback scheduling

The **Post-call** tab also has a **Callback scheduling** row with **Enable** or **Disable** and **Configure**, which calls the person back.

* **Triggers**: **Callee requested callback** (always on) and **No response from callee** (fewer than 2 messages from the caller), each with a delay as `hh:mm` (default `24:00`). Custom triggers test a [call data](/documentation/build-agents/customize-agent-behaviour/tools/api-tools#parameter-sources) or [Advanced Analysis](/documentation/build-agents/customize-agent-behaviour/advanced-analysis) field with the [condition operators](/documentation/build-agents/customize-agent-behaviour/tools/function-tools-and-conditions#conditions).
* **Schedule callback instructions** (required): how the agent decides when to offer and confirm a callback.
* **Callback message** (required): spoken when the callback connects, such as "Hi, calling you back as requested."
* **Maximum callback attempts**: 1 or more, default 3.

Callbacks show in [Logs](/documentation/monitor/logs#call-types) with the **Callback** call type.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.