> ## 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 # Notifications > Email agents automatically when a call scores low, misses a fatal parameter or gets a QA review, with their team lead in CC, using templates you design. A trigger sends an email when a call meets your conditions: after the AI scores it, or each time a QA reviews it. Use triggers for alerts such as a fatal miss, and to share QA feedback with the agent. In [Ringg Analytics](https://analytics.ringg.ai): **Sidebar → Notifications**. Owners, admins and QAs can open it. ![Notifications Setup tab listing the triggers Low score alert and Share QA reviews with the agent, marked On QA review, and the five System templates below](https://mintcdn.com/ringgai-0da73d20/CZ_hnbckkb2zP9lz/media/analytics-notifications/triggers.webp?fit=max\&auto=format\&n=CZ_hnbckkb2zP9lz\&q=85\&s=7bb72316840981c7343505c9a7cf9fe0) ## Add a trigger **1. Start a trigger** On **Setup**, click **Add trigger** and give it a **Trigger name**. Pick the **Use case**: the trigger only fires for calls in it, and its parameters become available as conditions. **2. Choose what starts it** Under **What starts it?**: * **The AI scores a call**: runs once the AI has scored and classified the call. * **A QA reviews a call**: runs each time a QA saves a change to their [review](/analytics-platform/review-calls/qa-reviews). Saving an unchanged review, or clearing it, sends nothing. **3. Set the conditions** Under **When should this fire?**, add conditions and groups. Within a group, pick whether all or any of them must match. **4. Pick the template and recipients** Choose a [template](#templates) under **What message should we send?**. Under **Who should receive it?**, pick **Agent on the interaction** or **Specific email addresses**, and tick **CC the agent's team lead** to copy their current team lead. > [!TIP] > > The trigger appears on **Setup**, and every email it sends shows on the **History** tab. ![Edit trigger form: name Share QA reviews with the agent, use case EMI collections, A QA reviews a call selected, the condition Parameters the QA Changed at least 1, message QA Review Shared, and a preview of the email with the QA score, AI score and the QA's comments](https://mintcdn.com/ringgai-0da73d20/CZ_hnbckkb2zP9lz/media/analytics-notifications/qa-trigger.webp?fit=max\&auto=format\&n=CZ_hnbckkb2zP9lz\&q=85\&s=b98f7267af06725e48921330d9e39029) ## Conditions | Condition | Available for | Means | | - | - | - | | **Overall Score** | Both | The call's official score, 0 to 100 | | **Max Severity** | Both | The most severe classification on the call | | **Source Type** | Both | Call, email or meeting | | **Fatal Parameter Count** | Both | Fatal parameters the call missed | | **Min Category Score** | Both | The lowest category score | | A parameter, by name | Both | Whether the AI gave it full marks (Yes / No), Yes / Maybe / No, or its share of points | | **QA Score** | QA reviews | The QA's score: their ratings, the AI's for parameters they didn't rate, 0 if marked fatal | | **QA Score minus AI Score** | QA reviews | Negative when the QA scored lower than the AI | | **QA Marked Fatal** | QA reviews | Yes or No | | **QA Fatal Parameter Count** | QA reviews | Fatal parameters missed under the QA's ratings | | **Parameters the QA Changed** | QA reviews | How many parameters the QA rated differently from the AI | | QA: a parameter, by name | QA reviews | That parameter under the QA's rating | QA conditions can't be used with **The AI scores a call**: there is no review yet at that point. ## Templates A template is the email a trigger sends: a subject and a body built from blocks, with a live preview using sample data. Five come with every workspace, marked **System**: **Fatal Classification Alert**, **Low Score Alert**, **Classification Summary**, **General Notification** and **QA Review Shared**. Click **New template** under **Templates** to add your own, or **Edit** on one to change it. Type `@` in a block to insert a variable: | Variable | Filled with | | - | - | | `agent_name`, `interaction_title`, `overall_score`, `max_severity`, `summary` | The call and its official score | | `qa_score`, `ai_score`, `qa_score_change_text` | The QA's score, the AI's, and the difference, for example "−14 points vs the AI" | | `qa_reviewer_name`, `qa_reviewed_at`, `qa_fatal_reason` | Who reviewed, when (India time), and why they marked it fatal | | `qa_parameters` | A list of the parameters the QA rated or commented on, each with the AI's rating, the QA's rating and the comment | QA variables are empty in emails sent by **The AI scores a call** triggers. ## Send one email by hand Owners, admins and QAs can email an agent from their [report card](/analytics-platform/coach-agents/report-cards) with **Email**, using any template. ## Next steps > **[QA reviews](/analytics-platform/review-calls/qa-reviews)** > > What a QA review contains. > **[Disputes](/analytics-platform/disputes/overview)** > > Dispute emails go out on their own, with the team lead in CC. > **[Metrics](/analytics-platform/set-up/metrics)** > > The parameters your conditions use. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.