# What each AI agent platform counts as an outcome

> How AI support, sales and receptionist platforms define the outcome they report and bill: a resolution, a booked meeting, a booked appointment, from their own documentation.

Published 2026-11-12 · Reviewed 2026-11-12. Canonical: https://attify.app/guides/what-platforms-count-as-an-outcome

Each AI agent vendor defines its own outcome, and the definitions differ in when they count (at booking, after a quiet period), what voids them (which handoffs, which repeat contacts) and whether anyone confirms them. In support, documented windows run up to 72 hours; AI sales vendors count meetings at booking; AI receptionist vendors mostly publish no booking definition at all.

Three comparison pages list each vendor's definition and billing unit from its own documentation, with the date it was read:

| Job | What vendors count | Read the comparison |
|---|---|---|
| Customer support | A resolution: usually a conversation the customer did not escalate, after a quiet period (72 hours at several vendors); some ask the customer, most do not | [How support AI vendors define and bill a resolution](https://attify.app/compare/support-ai-agent-outcome-definitions) |
| Sales meetings | A meeting booked: a booking event, a status set by hand, a reply label, or any meeting within a window after a touch | [How AI SDR vendors define a meeting](https://attify.app/compare/ai-sdr-meeting-definitions) |
| Appointments | Usually undefined; most vendors bill per call, minute, caller or location rather than per booking | [How AI receptionist vendors define a booking](https://attify.app/compare/ai-receptionist-booking-definitions) |

## Three questions to ask any vendor

1. **When is it counted?** At booking, after a quiet period (how long), or after something confirms it.
2. **What voids it?** A customer coming back (within what window, on which channels), a person stepping in (any person, or only some handoffs), a cancellation or a no-show.
3. **Who decides?** A rule over records, the vendor's own model, or the customer's answer.

Then test the answer on your own data: see the guides for [support](https://attify.app/guides/measure-ai-support-agent-resolution-rate), [sales meetings](https://attify.app/guides/check-ai-sdr-meetings-happened) and [bookings](https://attify.app/guides/measure-ai-receptionist-bookings).

## How Attify's standards relate

Each standard tests the vendor's own count as set, then asks what happened next. Where the data holds no vendor count, it reconstructs the claim with the most generous rule a careful vendor would use, so the gap cannot be shrunk by pointing at something the claim left out. Standards: [support resolution](https://attify.app/standards/support-resolution), [sales meetings](https://attify.app/standards/sales-meetings), [bookings](https://attify.app/standards/bookings).

## Questions

### Why don't vendors use the same definition?

There is no industry standard for an AI agent's outcome, and each vendor's definition also sets its bill or its headline number. Attify publishes one standard per job type so claims can be tested under one rule.

### Which definition is the strictest?

Among the support vendors whose documentation states a window, none waits 7 days, and none voids a resolution for every kind of handoff. Read each comparison for the details; Attify makes no claim about which vendor performs better.

## Sources

- Attify: [Research: how AI support vendors define and bill a resolution](https://attify.app/research/support-resolution-definitions), read 2026-11-09
- Attify: [Research: how AI sales agents count and bill a meeting](https://attify.app/research/sales-meetings), read 2026-11-09
- Attify: [Research: how AI receptionists count and bill a booking](https://attify.app/research/bookings), read 2026-11-09
