How to Increase Average Ticket Value in Your Booking Flow

Every other upsell channel — ads, emails, front-desk suggestions — has to win the customer's attention first. The booking flow doesn't. The person moving through it has already decided to buy, has picked a time, and is about to enter a card. Purchase intent will never be higher.

There's a second reason: relative framing. A $25 add-on pitched by itself in an email is a new purchase decision. The same add-on next to a $150 service the customer just selected reads as a small increment on a decision already made.

The highest-impact change is the simplest: show relevant add-ons on the same screen where the customer selects their service, not buried in a separate category or appointment type they'd have to book on their own.

An add-on hidden behind an extra click competes for attention it will never get — customers in a booking flow are heading toward checkout, not browsing. One sitting next to the service they just chose asks a single question: “want this too, while you're here?” Committed buyers often answer yes.

In the standard Acuity embed, add-ons exist but how they appear is largely dictated by the fixed flow — you generally can't control which add-ons show against which service, in what order, or with what supporting content. A custom scheduler makes add-on placement a design decision you own.

Bundling changes the unit of purchase. A customer who came for one service is offered a curated combination at a modest discount — an incentive, and a signal that these services belong together.

The critical word is show. A bundle whose savings are implied (“package pricing available!”) converts far worse than one that displays the math: individual prices, bundle price, amount saved. If the customer has to compute the benefit, most won't.

If you run promotional pricing on bundles, promotions tracking ties each promotion to its booking and revenue impact.

A service menu assumes the customer knows what to book. Many don't — especially in wellness, diagnostics, med spa, and fitness businesses where services have technical names and overlapping purposes. Those customers book the cheapest safe-looking option or leave to “do more research.”

An intent-based flow inverts the menu: it starts by asking what the customer wants to achieve, then recommends the service — or combination — that fits. This does two things for average ticket at once:

• It naturally recommends multi-service combinations when the customer's goal calls for them — something a static menu never does.
• It catches the customers who don't know what to book — the segment most likely to under-buy or abandon when faced with a raw list of names and prices.

This is the hardest tactic to retrofit onto a standard embed, because it isn't a form tweak — it's a different flow shape. It's a core feature of the custom booking experience we build on Acuity, where the same recommendation engine can run site-wide, not just on the booking page.

Your highest-value services usually carry the most hesitation: they cost more, and they're the least understood. The customer's honest question is “what exactly am I getting?” — and if the booking flow can't answer it, they trade down to something familiar.

Putting education inside the flow — a short video, a sample of the report they'll receive, a plain-language description of the appointment — answers the question at the moment it's asked. The customer never has to leave the flow to research, so they never get the chance to not come back.

Preparation guidelines belong here too: prep instructions specific to the selected services, shown before confirmation, remove a quiet source of hesitation and reduce day-of surprises.

It's tempting to believe hiding the running total keeps customers adding. The opposite is true: uncertainty about the total is a reason to stop — or to abandon at the final screen when the number appears.

A floating summary sidebar that always shows current selections, pricing, and — crucially — the bundle savings being earned keeps the transaction transparent. A customer who can see exactly what one more add-on does to their total is more willing to add it.

Some customers want to see the whole catalog before committing — and in most booking flows, looking around means backing out, risking lost selections and an abandoned booking. Customers face a bad choice: commit without full information, or restart.

A flow that lets customers open the full service catalog at any point and return to exactly where they were removes that penalty. Browsers become bookers, and bookers who've seen the whole menu add more — because they know what else exists. Like intent-based flows, this is structural: out of reach in a fixed embed, standard in a custom build.

If a full custom flow isn't on your roadmap yet, you can still improve what surrounds the embed — see customizing your Acuity scheduling page.

None of the tactics above matter if you can't see whether the number moved. Average ticket value — total booking revenue divided by appointments, tracked weekly or monthly — is the metric every change in this guide should be judged against.

Acuity's built-in reporting gives you raw data, but a trend line of average ticket per period is generally a manual export-and-spreadsheet exercise. The Tecton analytics dashboard computes it from your Acuity data directly, and promotion tracking shows which offers changed what customers bought, not just how many booked.

One measurement gap deserves mention: because the standard Acuity embed is an iframe, tools like Hotjar and Microsoft Clarity go blind the moment a visitor starts booking — you can't see where customers hesitate over an add-on or abandon a bundle. A custom flow is native page code, so the entire journey is recordable. Full explanation: why analytics tools can't see inside the Acuity iframe.

Acuity is an excellent scheduling engine, but its embedded booking flow follows a largely fixed structure. Acuity's settings evolve, so treat the middle column as a general guide rather than a spec sheet.

A custom scheduler is a done-for-you, white-labeled build — not a SaaS template — and Acuity remains the source of truth: pricing, availability, and services sync automatically, so staff workflow doesn't change. It can also recover the roughly 3% card processing fee where surcharge rules permit, and supports a physical gift card workflow (see selling gift cards with Acuity Scheduling).