Every call starts already knowing why you booked.
Someone reads about a specific service on the pricing page, decides it is worth a conversation, and clicks to book a call. The calendar entry arrives with their name and nothing else. The one thing they just told you, which service they were weighing up, is gone.
So the call opens with "so, what were you looking at?". It wastes the first few minutes, and worse, it signals you were not paying attention. The context the prospect handed you is thrown away at the exact moment it is most useful.
I built a booking panel where every service card carries its own identifier, and that identifier travels all the way through to the calendar entry. Ten tier cards across the pricing and landing pages, each tagged, so the booking knows where it came from.
The principle is that intent is carried, never inferred. Most setups try to guess it from referrer data, which vanishes the moment a link is shared or opened in a new tab. Here the signal rides with the person, so it survives all of that. The panel also opens in place rather than sending anyone off to another site, so you do not lose people straight off a page you paid to get them to. While I was in there, I found and cleared sixty-one trailing-slash inconsistencies across twenty-six files that were quietly breaking links.
A calendar entry now arrives already knowing whether the person was reading about the entry-level partnership or a fifteen thousand pound build. The call opens on the real thing, not on catching up. It runs across every page that offers a call, and the configuration and the data stay with the practice, portable if the calendar provider ever changes.
Honest scope: an internal build for my own practice. The gain is qualitative, better-prepared calls, rather than a single conversion figure.
The friction was tiny per call and taxed every single one. That is exactly the kind of thing worth fixing properly: small, constant, and quietly expensive. The move was to carry the signal explicitly rather than guess at it, which is more work up front and far more reliable after.
And I kept it owned and portable. The config and the booking data belong to the practice, so changing calendar tools later is a change, not a migration. One senior operator, AI-leveraged, is why it was worth building the plumbing instead of living with the gap.