Research: how AI sales agents count and bill a meeting
AI SDR vendors that document a counting rule count a meeting at booking or earlier (a booking event, a status a user sets, a label on a reply, or any meeting inside a window after the agent's outreach), and none of the large ones bills per meeting booked: they bill seats, credits, prospects, leads, calls, chats or actions. Firms that do bill per meeting draw the line later: of 13 whose terms we read, 9 tie the fee to a meeting that was held or attended, and 7 do not bill no-shows.
Facts below come from each company's own pages, read on 31 October 2026; a date in a source link is the date the page shows. Prices change, and the linked page is the reference. The page makes no claim about any company's results.
AI SDR vendors#
Read on 31 October 2026. Two AI SDR vendors that bill per meeting, Chase and SalesMonk, are in the next table.
Every counting rule documented above sits at booking or earlier. The one place found where a large vendor's money follows a meeting's outcome is Outreach's Deal Agent, charged a credit per completed meeting tied to an opportunity. Because billing runs on seats, credits and activity, the meeting count is a reported number rather than an invoiced one, and no billing dispute disciplines how it is counted.
How human sales teams are measured#
Human SDR teams are set quota on meetings held, then on the opportunities those meetings convert into. The Bridge Group's 2025 study of 351 B2B companies reports a median monthly SDR quota of 10 "Stage 0 held" meetings and 6 "Stage 1 converted" (The Bridge Group, 6 Feb 2025). Booked is not the unit.
Firms that bill per meeting#
Read on 31 October 2026. The large appointment-setting agencies checked sell retainers or say no more than "qualified"; these 13 firms publish at least one clause about what a billable meeting is.
What the 13 sets of terms show:
- Held is the common trigger. 9 tie the fee to a meeting that was held or attended (RevenueScale's agreement also says a meeting is complete once arranged). Social Bloom and SalesMonk bill at booking; for Throxy and Kavrn the trigger is not confirmed.
- No-shows. 7 do not bill them, though at Chase and Revenx only if the client reports or marks them.
- Criteria first. Nearly all agree criteria for a qualifying prospect before outreach; Throxy and Kavrn also have a person accept or validate each meeting.
- Length. One firm sets a minimum: 15 minutes (Eightfold Systems).
- Exclusions. None excludes existing customers or contacts in open deals; RevenueScale excludes only a contact already in an active sales conversation in the prior 60 days.
- Lead time. None limits how far ahead a meeting may be booked.
- Disputes. Five set a window to dispute or reject a meeting, from 24 hours to 7 days. At Social Bloom, Chase and RevenueScale, a no-show not reported in time is billed.
Three of these documents are on pages.dev hosts (Social Bloom, Eightfold Systems and CIENCE's pricing copy), which may be staging copies of the firms' own sites.
What the customer's own systems record#
- HubSpot. A meeting's outcome property,
hs_meeting_outcome, takes scheduled, completed, rescheduled, no show or canceled; the guide does not say it is set automatically, and the start and end properties hold the scheduled times (HubSpot Meetings API). Lifecycle stages mark a company with at least one closed deal (Customer) or one associated with a deal (Opportunity) (HubSpot, updated 17 Jul 2026). - Google Calendar. Each event carries a status (confirmed, tentative, cancelled), each attendee's response (needsAction, declined, tentative, accepted), creation and update times, organizer and creator, and links between moved instances of a recurring event (Google Calendar API).
- Google Meet. A conference record lists participants with their earliest start and latest end times (Google Meet API).
- Who booked it. HubSpot's documentation read names no field that records that an AI agent booked a meeting. The evidence sits in the vendor's own log (such as Reply.io's meetings list) and in the email thread that carried the link or the accepted time.
Against Attify's standard#
The Attify Audited Meeting Standard tests the vendor's own count where one exists, then checks in the customer's own CRM, calendar and conferencing records whether the meeting was held, whether the AI booked it, and whether a person had to step in. None of the AI SDR vendors' documented rules includes attendance; most of the per-meeting firms' terms do. So the standard tests each claim in the unit the vendor states it in (v0.6): a vendor that counts meetings booked is tested on its bookings, with the share held, cancelled and no-show beside them; one that bills held meetings is tested on attendance too.
Not known#
- How Salesforce's SDR agent counts a booked meeting. The Salesforce Help article read for this research was not recorded with its address, so its rule is not described here.
- Salesforce Event fields for a held meeting or a no-show: the object reference refused automated reading.
- Whether HubSpot's prospecting agent uses the 7-day sequences rule.
- Reply.io's prices; Conversica's prices and lead statuses; Regie.ai's attribution window; Apollo's meeting metric; Artisan's self-serve prices. Their pages refused automated reading or did not load.
- Throxy's attendance rule: its own page carries an unresolved editor's note.
- Whether the pages.dev documents match the firms' live sites.
- Pay-per-meeting terms at the large appointment-setting agencies, which do not publish them.
Vendors#
A company described here can send corrections with a link to its own documentation under the right of reply. Attify updates the page and the date it was read.
Questions
We pay per booked meeting. What definition of a booked meeting should the contract use?
- The terms read for this research point to a meeting that was held, with someone from the prospect's side attending who fits criteria agreed before outreach, no-shows and prospect cancellations not billed, and a dispute window long enough to check your own calendar. None of the terms read excludes existing customers or contacts in open deals, so a contract has to say so itself.
What is the difference between meeting booked, held and qualified for an AI SDR report?
- Booked means the meeting is on the calendar; held means it took place with someone from the prospect's side; qualified, in Attify's standard, means it led to a new sales opportunity within 30 days, while most per-meeting firms above use the word for a prospect who fits agreed criteria. Every AI SDR vendor that documents a rule counts at booking.
Do AI SDR vendors charge per meeting?
- Not per meeting booked, among the large vendors read for this research: they bill seats, credits, prospects, leads, calls, chats or actions. Per-meeting billing appears at smaller firms, and most of those that publish terms tie the fee to a meeting that was held.
Which HubSpot meeting properties tell me a meeting was held, not just booked?
- The meeting outcome property, hs_meeting_outcome: scheduled, completed, rescheduled, no show or canceled. HubSpot's guide does not say it is set automatically, so a missing 'completed' may only mean nobody updated it; calendar responses and conferencing join times are stronger evidence.
Which Salesforce Event fields show whether a meeting happened?
- This research could not confirm one: Salesforce's Event object reference refused automated reading, so no field is named here.