The sales playbook runs on its own — you don't open a page and click "generate." The moment an invoice is marked fully paid, it reads that invoice's customer, service, and vehicle details and builds a schedule of up to six follow-up SMS messages spread out over the next year: a review request, a warranty-registration nudge, a cross-sell pitch, a maintenance check-in, a win-back offer, and a one-year anniversary message. You can watch and manage that schedule for every customer at /app/playbook, and the same schedule for a single invoice also shows up right on that invoice's own page. Nothing sends the moment it's built — every message sits in the queue until its scheduled date, and you can pause, skip, or mark any of them done any time before it goes out.
This article covers the part that's specific to AI: which of those six messages actually get AI-written copy, and what happens when it can't produce one. For the editor where you write and tune the message templates themselves, see "Configuring sales playbook templates."
What actually gets AI-written
Of the six message types, only the cross-sell pitch gets a real AI-generation pass. The other five — review request, warranty registration, maintenance check-in, win-back, and anniversary — use your saved template text for that shop, with details like the customer's first name filled in. That's straightforward templating, not AI content generation.
For the cross-sell message, the system looks at the customer's past paid services at your shop and the vehicle on file, then generates a one-sentence pitch meant to reference that specific history rather than read like a generic upsell line. It's constrained to only reference services the customer has actually bought — it isn't meant to invent purchase history that isn't there.
That generation step is best-effort. If it errors out, or comes back with something too short to be usable, the message quietly falls back to a pre-written pitch instead — one that's still matched to the service category involved and to whether this looks like the customer's first purchase in that category or a repeat one. Either way, a cross-sell message goes out; it just won't always be the personalized version.
How the rest of the schedule gets built
When an invoice gets paid, the engine looks at the service on that invoice (from the quote's line items) to decide which messages apply and how to shape them. A warranty-registration nudge only gets added for film-based services like tint, PPF, or vinyl wrap — a wash-and-wax or removal-only job won't get one. The cross-sell suggestion also checks whether the customer has bought in that service category before, so a first-time customer and a repeat customer in the same category can land different framing.
Each queued message locks in its wording and send delay at the moment it's created, so editing your templates later only changes plays created after that edit — messages already in the queue keep what they had when they were built. If your shop is part of a franchise/HQ org, a shop with no template edits of its own starts from the org's saved templates instead of SalesThumb's stock defaults. And the enqueue step is idempotent: if it somehow runs twice for the same invoice (say, a duplicate webhook), you won't end up with duplicate messages.
Things to know
- Plan requirement: the sales playbook (including the AI cross-sell personalization) requires the Growth plan or above — Growth, Professional, HQ, or Enterprise. It isn't included on Starter.
- Stub mode: if the workspace doesn't have live AI configured, the cross-sell personalization call comes back empty and that message always uses the deterministic fallback pitch instead of one built from the customer's real history. There's no separate "stub" indicator for this feature the way there is on some AI tools — the other five message types are template text regardless, so nothing about them changes either way.
- Personalization only runs once, right when a cross-sell message is first queued for an invoice. It isn't re-run later and doesn't touch messages already sitting in the queue.
- Pausing the playbook for your shop stops new messages from queuing and holds everything already pending — it doesn't delete anything, and the queue picks back up when you resume.
- A message fires once it reaches its scheduled date via an hourly background job; the queue view also has a manual "run due now" option for anything already past due.
Frequently asked questions
Q: Does AI write all six playbook messages, or just some of them?
A: Just one. The cross-sell message is the only one that gets a real AI pass, generating a one-sentence pitch based on the customer's actual service and vehicle history. The other five — review request, warranty registration, maintenance check-in, win-back, and anniversary — use your saved template text with details like the customer's name filled in, no AI generation involved.
Q: Can I stop a message before it sends?
A: Yes. Every generated message sits in the queue until its scheduled date — anywhere from the next day out to a year, depending on the message — and you can pause, skip, or mark it done any time before then from the playbook queue. You can also pause the entire playbook for your shop, which stops new messages from queuing and holds everything already pending.
Q: What happens if AI isn't configured for my workspace?
A: The cross-sell personalization step comes back empty, so that message uses a pre-written fallback pitch instead of one built from the customer's real purchase history. You likely won't notice anything different in the app itself — there's no separate stub banner for this feature — just that the cross-sell text won't be personalized to that specific customer.
Q: What plan do I need for the sales playbook?
A: Growth or above — Growth, Professional, HQ, or Enterprise. It isn't included on the Starter plan.
Q: If I edit my message templates, does that change messages already queued for a customer?
A: No. Each queued message locks in its wording and send delay at the moment it's created. Editing a template only affects plays created after that edit — see "Configuring sales playbook templates" for how the template editor itself works.
Q: Does the AI ever pitch a service the customer hasn't actually bought?
A: No. The personalization step is specifically constrained to reference services from the customer's real paid history at your shop — it isn't meant to invent purchases that aren't there.