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

# Results and corrections

> After a QA resolves a dispute, the agent sees the final score, each parameter's result and the QA's remarks. A QA can correct a resolved dispute later.

When a QA resolves a dispute, the result shows on the call for the agent, their team lead and reviewers, and an email goes out. If the decision has to change later, a QA corrects it; every version is kept.

In [Ringg Analytics](https://analytics.ringg.ai): **Sidebar → Interactions →** open the call.

## What the agent sees

![Final score · Appeal reviewed by QA card showing 100, AI scored 92 (+8) · Overturned; the Appeal card marked Resolved with who submitted and who resolved it; both disputed parameters, Greeted the customer by name No to Yes and Closed with a recap 2 to 5, marked Changed with the QA's remarks; and the original AI score of 92 below](https://mintcdn.com/ringgai-0da73d20/BhQtV3gvIrxE9J2L/media/disputes-results/result.webp?fit=max\&auto=format\&n=BhQtV3gvIrxE9J2L\&q=85\&s=5d14e7dff6a4d46c156e0dae61a92bbb)

| Part | Shows |
| - | - |
| "Final score · Appeal reviewed by QA" | The official score, the AI's score and the difference, and the outcome: **AI score upheld**, **Partially overturned** or **Overturned** |
| **Appeal** card | Status, who submitted it and when, who resolved it and when |
| Disputed parameters | The AI's rating, the QA's, **Changed** or **Unchanged**, and the QA's remark |
| The AI's score | The original AI scoring, unchanged, for comparison |

The agent and their current team lead get an email: "Appeal reviewed: … — final score N%", with each disputed parameter's result and the QA's note.

The official score then counts everywhere: **Interactions**, **Summary**, **Agents**, [report cards](/analytics-platform/coach-agents/report-cards), [notification](/analytics-platform/set-up/notifications) conditions and exports.

## Appeal history

**Appeal history** at the bottom of the call lists every step: **Appealed**, **Review started**, **Released**, **Reassigned**, **Resolved** and **Corrected**, by whom and when, with each version's final score. Everyone who can see the call can read it, and it is never deleted.

## Corrections

Use a correction when a resolved decision turns out wrong, for example after a team lead escalates it offline and the escalation is accepted.

**1. Open the resolved call**

As a QA, admin or owner, open the call and click **Correct the final score (offline dispute accepted)**.

**2. Re-rate and give a reason**

Change the ratings that need it and write why you are correcting. The reason is required.

**3. Save**

Click **Review correction**, then **Save correction**.

> [!TIP]
>
> The call shows the new final score and **Corrected · v2**, with your reason. The agent and their team lead get an email: "Score corrected: … — now N%".

![Final score 86, AI scored 71 (+15) · Overturned · corrected (v2); the Appeal card marked Resolved and Corrected · v2; both disputed parameters marked Changed; the correction reason; and the Correct the final score (offline dispute accepted) button](https://mintcdn.com/ringgai-0da73d20/BhQtV3gvIrxE9J2L/media/disputes-corrections/corrected.webp?fit=max\&auto=format\&n=BhQtV3gvIrxE9J2L\&q=85\&s=52b3ed4218ef3ae86a9692780d4bc116)

If two reviewers correct the same appeal at once, the second save is refused, so nobody overwrites a correction they haven't seen.

## Next steps

> **[Settings and reports](/analytics-platform/disputes/settings-and-reports)**
>
> See overturn rates by parameter.

> **[Report cards](/analytics-platform/coach-agents/report-cards)**
>
> Where resolved disputes show for an agent.

> **[Overview](/analytics-platform/disputes/overview)**
>
> The rules for disputes.


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