Introduction

Some results are already recorded somewhere else. A deal closed in the CRM, a ticket resolved in the service desk, an invoice paid in the ERP — the system of record knows, and asking a rule or an AI judge to work it out again from the session is a weaker answer.

Automation verification reads the result from that system instead. Like a rule, it adds no model cost.

When to use it

Where to find it

AI Governance > Outcomes & ROI > open or create an outcome > 2. Measure outcome > Add agent.

Define the outcome

Step 1: Name the outcome

Name the result, not the activity — Deal closed, not Lead handled.

Step 2: Add an agent and choose Automation

Under 2. Measure outcome, click Add agent, pick the agent, and set How it is verified to Automation.

Step 3: Pick the Recorded by automation

Recorded by lists automations built on the outcome callable interface. Pick the one that reports when this outcome happened.

Step 4: Decide where the value comes from

Turn on Also record the outcome value from this automation if the system of record knows what each occurrence was worth — the deal amount, the invoice total. When it is on, What it is worth is locked to the automation setting the value, and the agent's row reads "Recorded by an automation". Otherwise set What it is worth on the agent: A set amount for every counted session, or An automation prices it.

Step 5: Save

Verify it counts correctly

Before reporting anything, compare a short window of counted outcomes against the system of record by hand. The automation is now the definition of the outcome, so check both directions: occurrences it should have counted, and ones it should not.

Known limitations

1. Only as good as the automation — If the automation misses or duplicates records, the count does too.

2. It needs an automation on the outcome callable interface — Without one, there is nothing to pick under Recorded by.

Related

• Outcomes & ROI Overview

• Define an Outcome (Deterministic)

• Add a Source