AI Admissions Agent Billing Models: A UK Buyer's Guide

How AI admissions agents are billed: five models and their hybrids

AI admissions agents are billed in one of five ways: a flat licence, a charge per conversation or resolution, a charge per seat, a usage meter (messages, credits or tokens), or a charge per outcome. Most real contracts mix two of these and add fixed lines for setup, integrations and extra channels.

The model matters less than the definition behind it. "Per conversation" can mean a visitor opening the chat window, a thread with at least one answer, or a thread that ended without a human.

This guide is for the person in a UK university, college or independent provider who has to compare quotes. If you are still building the case internally, start with the business case in five slides. For criteria beyond cost, see the evaluation grid for choosing an AI agent.

The five billing models

Flat licence or subscription

You pay a fixed amount per period for a defined scope: a number of sites, languages or campuses. It rewards heavy use, because the extra conversation costs you nothing, and it makes budgeting simple.

The risk is paying for capacity you do not use, and discovering that "unlimited" carries a fair-use clause. Ask what the fair-use limit is, in writing, and what happens when you reach it.

Per conversation or per resolution

You pay for each conversation, or only for those the agent resolves without a person. It looks fair because cost follows value, and it lowers the entry barrier for a pilot.

The risk sits in the definition. If a resolution is whatever the applicant did not escalate, a visitor who gives up counts as a success. If handovers to an adviser are billed as well, the agent is paid twice for the cases it could not handle.

Per seat or per user

You pay for each named adviser or staff member who uses the platform. It suits tools where the human team does the work, such as an inbox or a CRM add-on.

For an agent that talks to prospective students, seats measure your team size, not the work done. They can still be reasonable when the agent mainly supports advisers, but you should check that applicants are not counted as users.

Usage-based: messages, credits or tokens

You pay for a metered quantity. It tracks the supplier's own cost most closely, so it tends to be honest about what runs underneath.

The risk is unpredictability. A single long conversation consumes more than a short one, and a credit system can hide the real unit behind a conversion table. Ask for the meter in plain terms: what, exactly, consumes a credit?

Per outcome

You pay for a defined result, such as a booked open day, a completed enquiry form or a qualified record in your CRM. It aligns interests, and it is attractive when a team is nervous about spend.

The risk is disputes: does a booking count if the applicant does not attend, are duplicates filtered, and who audits the count?

Hybrids

Most quotes combine a base licence with an included allowance and an overage rate. That is a sensible structure when the allowance is generous enough to cover a normal year, and a poor one when the allowance is set low so that overage becomes the real bill.

Comparison of the models

The fixed lines around the meter

The meter is only part of the invoice. Ask for every other line to be itemised before comparing totals.

• Setup and onboarding. Content ingestion, configuration, testing and staff training.
• Integrations. Connection to your CRM, events or booking tool and any consent platform. Ask whether each is a one-off fee or recurring.
• Channels. A website agent and a messaging-channel module are often separate lines, each with its own consent rules.
• Languages. Some suppliers charge per language. Others include all of them.
• Campuses or sites. Check whether a second campus or a partner college is a new licence.
• Model cost. Ask who carries the cost of the underlying language model. If it is passed through, ask how, and whether a change in the supplier's model costs changes your bill during the term.

Questions every buyer should ask about the billable unit

These questions turn a label into a testable definition. Put them in writing, and have the answers attached to the contract.

1. What is the billable unit, and what starts and stops it?
2. Is a conversation that ends in a handover to an adviser counted, and is it counted twice?
3. Are repeat visits by the same person one conversation or several?
4. How are bots, scrapers and spam filtered, and who pays for traffic you did not want?
5. What happens at peaks? Is there a hard cap, an automatic overage charge or a warning first?
6. Is the allowance annual or monthly, and does unused volume carry over?
7. Is the rate locked for the term, and what limits an increase at renewal?
8. Can you export conversations, configuration and content if you leave, and in what format?

Seasonality: your year is not flat

An undergraduate recruitment year in the UK has sharp peaks. Enquiries rise around open days, the UCAS main application date and the weeks of Clearing in the summer, then fall away. A model that bills by volume will concentrate cost in those weeks, while a flat licence spreads it.

Model the peak, not the average. Check whether an unexpected burst, such as a social media post that sends traffic to the chat, triggers overage that you cannot cap.

How to model twelve months of cost

Use this structure: expected conversations multiplied by the billable rule, plus the fixed lines, plus a contingency for overage. Do it for a low, a central and a high scenario, and write the assumptions down.

1. Estimate conversations. Start from your own site analytics and enquiry counts, not from a vendor's benchmark. Split them by season: quiet months, open day months, Clearing.
2. Apply the billable rule literally. Remove what the contract excludes, such as spam or sessions with no message. Add what it includes, such as handovers.
3. Add fixed lines. Setup, integrations, channels, languages, campuses and support.
4. Add the overage case. What does the high scenario cost if the allowance is exceeded for two months?
5. Add the exit case. What would leaving cost you in work and in data you cannot retrieve?

A worked example, in plain terms. Imagine a college expecting a modest base of conversations most of the year, a multiple of that during open day weeks and a steep rise in Clearing. Under a per-conversation model, the invoice follows that shape and the Clearing weeks carry most of the variable cost. Under a flat licence with a fair-use cap, the invoice is flat, unless Clearing breaches the cap. Under a hybrid, the base covers ordinary months and overage appears only in the peak.

None of these is cheaper in itself. Run the three scenarios against each quote and compare the spread, not just the central case.

Red flags

• The unit of billing cannot be defined in a single sentence.
• Handovers to a person are billed as extra conversations.
• There is no cap, no alert and no way to set a monthly ceiling.
• "Unlimited" appears without a written fair-use limit.
• The rate can change mid-term, or the renewal has no limit on increases.
• Credits are sold with no table showing what consumes them.
• Channels, languages or integrations are quoted as "to be agreed later".
• There is no export of conversations and configuration on exit.
• The supplier will not say who carries the cost of the underlying model.

UK context: what shapes the contract

Your procurement route matters. Universities and many colleges buy under internal thresholds or a framework, and a usage-billed contract can be harder to approve than a fixed one because the final value is not known at signature. State your maximum spend in the tender so that bids are comparable.

Three bodies set the context. The Office for Students expects information given to prospective students to be accurate, so an agent that is cheap but improvises about courses is a regulatory risk. QAA is the reference for quality standards in provision. The ICO oversees UK data protection rules, which means a lawful basis for processing chat data, a privacy notice and a processing agreement with the supplier.

If you recruit in the EU or buy from a supplier based there, the EU AI Act may also apply to the way the agent is described and used. Ask the supplier for its position in writing. The guide to AI chatbots for student recruitment and the comparison of AI agents place billing within the full buying decision.

What about Skolbot?

Skolbot Chat is a website chatbot that answers from the institution's own content, qualifies prospective students, books open days and appointments, and pushes the record to your CRM. A messaging-channel module is optional. The commercial terms are quoted on request after scoping, so that the quote reflects your sites, languages and integrations. Use the questions above with us as you would with any supplier.