The ticket reads politely enough: “When we signed up, we were told the migration would be handled for us. Who do I talk to about that?” And support — which has never heard of any such arrangement — now has three bad options: honor a promise nobody recorded, deny a promise the customer clearly believes, or stall while someone hunts through a closed-won deal for what was actually said. Meanwhile the customer, two weeks into a relationship they were excited about, is learning that the company's right hand doesn't know what its left hand sold.
Here's the uncomfortable truth under it: the customer is almost never lying. Something was said — in a demo, a call, an email thread that lives in one person's inbox. Sales conversations run on enthusiasm and edge cases; support runs on what the product actually does today. The gap between those two is where new customers churn, and it isn't a people problem. It's a missing artifact: nothing structured travels from the person who made the promises to the people who inherit them.
The one-page handoff record
The fix is a document so small there's no excuse to skip it: one page per closed deal, written by whoever closed it, delivered to support before the customer's first week ends. Five fields. Who they are — company, contacts, and what they're actually trying to accomplish (the job, not the feature list). What they bought — plan, seats, term. What was promised — every commitment beyond the standard offering, however small: the workaround demoed, the report format mentioned, the “yes it can do that” moments. What was flagged — concerns raised in the sales cycle, because today's objection is next month's ticket. Anything unusual — discounts, custom terms, the champion who took a risk on you. Ten minutes to write while the deal is fresh; hours of triage and one churn saved is the exchange rate.
The promise log
The “promised” field earns its own discipline, because promises are the radioactive material in the handoff. Keep them in one searchable place — a shared sheet or a field on the account record — each entry with what was committed, to whom, by whom, and when. Two things happen the week this exists. First, the surprise tickets stop being surprises: support searches the log before answering, and “let me check what was arranged” becomes a lookup instead of an excavation. Second — the quieter effect — promises get more careful when they're written down. A commitment that lives in a log with your name on it gets made more deliberately than one that evaporates after the demo. That's not surveillance of sales; that's the same standard support already lives under, where every reply is on the record.
When the promise isn't in the log
The legacy cases still arrive — commitments from before the log, or ones that slipped past it. The script has three moves, in order. Verify without doubting: “I want to get this right — let me check with the person you worked with” treats the customer's memory as evidence, not accusation, and buys a real answer instead of a guess. Then decide deliberately with whoever made the sale: honor it as stated, translate it (“handled for us” often means an hour of guided setup, which you can absolutely do), or — when it's genuinely unbuildable — own it: what was described isn't something we can deliver, here's what we can do, and here's what we're doing to make the gap right. An honest no with an offset keeps more customers than a slow-motion dodge ever has. What you never do is make support relitigate the sale alone — the person who made the promise sits in on how it lands.
Close the loop backward
The handoff isn't only protective — it's the best product-feedback channel you own. Tally which promises keep appearing: the same workaround demoed in every deal is a feature request with revenue attached; the same objection flagged repeatedly is your churn early-warning wearing a sales costume. And when a promise blows up in the queue, the postmortem question isn't “who said that” — it's “what should the next handoff record have carried so this landed soft?” The record gets a little better every quarter, which is the whole system working.
The bottom line
Every closed deal ships two things: a customer, and a set of expectations only one person can see. The one-page handoff makes the invisible half travel — who they are, what they bought, what was promised, what was flagged — and the promise log turns commitments into records instead of recollections. When a promise surfaces that nobody wrote down, verify without doubting, decide with the person who sold it, and honor, translate, or own it plainly. The customer was told something. The only question is whether your team finds out from a document or from the ticket.
— Tom
Promises that survive the handoff
CSByDesign attaches the handoff record and promise log to every account — support sees what was sold before the first ticket, and repeated promises surface as the product feedback they are.
See how CSByDesign works →