This playbook answers every buyer who asks to talk to sales. A demo, pricing or contact request gets the right rep's calendar at once, or a personal reply within the time your team agreed, and ends in a held first meeting or a recorded reason. Once a week the team measures how fast it answered and fixes the rules behind the misses.
Who does what
- Inbound rep the SDR or account executive who owns the request, sends the personal reply, calls and follows up until a meeting is booked.
- Meeting owner the rep or account owner who holds the first meeting and records its outcome.
- Sales manager owns the response targets and the escalations, and runs the weekly review.
- RevOps owns the forms, the fit and routing rules and the CRM fields, and changes them after each review.
- Agent Claude or ChatGPT, drafts the reply, the meeting brief and the weekly report. A person sends every message.
What you need
- A CRM, HubSpot or Salesforce, with your forms and chat writing into it.
- A booking tool that shows the owner's calendar after the form: your CRM's own meetings, Chili Piper, Calendly or Default.
- Written fit rules such as country and size, and routing rules with territories, tiers and rotation pools.
- A chat tool for alerts, such as Slack, and an agent for the drafts and the report.
Some answers are yours to set before the first run:
- The response target for each request type, and whether it counts business hours or the whole day.
- Who covers outside the team's hours, and the fallback owner when everyone is away.
- How many tries over how many days before a request closes as unresponsive.
- How many missed meetings before a request closes as a no-show.
1Capture the request
- Meeting request comes in
- Check who is asking
The response clock starts when the buyer submits. The form asks only what routing needs: work email, name, company and one qualifying question, because enrichment fills the rest. A phone number stays optional and is asked for only when the offer is a call, with a note next to the field that says what it is for. Chat and in-app requests ask the same question and write the same fields as the form, so every channel counts.
Two values go on the record at submit:
- Submit time: the moment the buyer asked. A CRM's own response report often starts later, and HubSpot's starts at owner assignment and resets on reassignment.
- Response target: the target the team agreed for this request type, and whether it counts business hours or the whole day.
The CRM then checks who is asking. Bot checks run first, and junk is flagged with a reason instead of deleted, because real buyers end up in the spam folder and someone looks there every week. A second submit from the same email on the same day is the same request and keeps the first time. Enrichment takes the company from the email domain and the role from the name and email, and the buyer's own answers win. Free email addresses are marked and left to the fit rules.
Last comes the match against what you already have: contacts with the same domain first, then companies whose website matches. In HubSpot a subdomain creates a separate company, so one customer can turn into two. A customer who lands in the new business rotation is the sign to look.
2Check the fit
- Is it a sales fit?
- Send to the right team
- Handled by another team
The first decision asks whether sales takes the request. The CRM applies the team's written fit rules:
- Sales fit: the request is clean, the company passes the hard rules such as country and size, and it asks for sales.
- Existing relationships: customers, open deals and owned accounts go to their owner even when they fail the new business rules.
- Unknown: when enrichment is empty and the answers are plausible, the request counts as a fit and the rep decides.
- Not for sales: spam, competitors, vendors, job seekers, students, support questions and companies outside the hard rules.
The marketing lead score stays out of this decision, since it belongs to lifecycle stages. When reps disqualify many approved requests in the first call, or buyers say they were turned away, the rules need a look.
Requests that are not for sales still get an answer. The person sees a message or page that says where the request went, and a workflow sends it on by reason: support to support, partners to partnerships, job seekers to careers and other buyers to nurture. Spam and competitors stay out of sales views and marketing email.
3Route and book
- Assign the right owner
- Offer times right away
- Did they book a time?
- Draft a personal reply
- Reach out until booked
- Closed as unresponsive
A sales fit gets one named owner by written rules, in this order:
- Matched accounts go to the account owner or the account team.
- The rest goes by territory, segment and account tier, with top tiers straight to account executives.
- Within the chosen pool the request rotates among the reps who are available, weighted where reps carry different loads. A fallback owner covers the times when everyone is away.
- A catch-all rule at the end takes every request no earlier rule assigned.
The record keeps which rule assigned the owner, so wrong routing can be traced. In HubSpot the rotate action in workflows needs Sales Hub or Service Hub Professional. In Salesforce one lead assignment rule is active at a time, and its last entry catches the rest. Chili Piper, Default or LeanData add ownership rules, weighted rotation and fallbacks on top of either CRM.
Right after the submit the buyer sees the owner's calendar, or the pool's, in place of a plain thank you. The form answers carry over, so nothing is asked twice, and the slots lie in the next few working days. When no calendar can be shown, the page says who will get in touch and by when. In HubSpot a form leads straight to a scheduling page only with Sales Hub or Service Hub Enterprise. Chili Piper, Calendly and Default route from the form and show the calendar themselves.
The second decision asks whether the buyer booked. A self-booked meeting with the right owner and a start time meets the response target, and automatic emails never count as a response. With no meeting a few minutes after the calendar appeared, or when none could be shown, the request goes to a person.
The agent drafts a personal reply at once, so the rep can send it well inside the target. It restates what the buyer asked for in their words, offers two times in the next two working days or the owner's booking link, and stays at three to five sentences in the owner's voice, with no pitch and no attachments. Every detail that came from enrichment is marked for the rep to check.
The inbound rep gets a CRM task and a chat alert with the form answers and the draft, edits the draft and sends it from their own inbox, and calls when the buyer gave a number for a call. Before the target runs out, the manager is alerted and then the request moves to the next available rep. Outside the team's hours the reply confirms receipt and says when someone will call. After the agreed tries over the agreed days, the request closes as unresponsive and goes back to nurture with its history.
4Hold the meeting
- Brief the rep and confirm
- Hold the first meeting
- First meeting held
- Closed as no-show
Once a time is booked, the agent writes a brief for the meeting owner: the buyer's reason in their words, company facts, tier and CRM history, in five lines or fewer. It also drafts a two-sentence confirmation from the owner that restates why the buyer asked. The booking tool sends reminder emails, for example a day and an hour before the start. HubSpot's default meeting reminders send up to three emails on every plan, and Calendly workflows send reminders and reconfirmations.
The meeting owner runs the meeting, and the step ends one of two ways:
- Held: the owner records a standard meeting outcome, a value that reports can count, and the meeting goes on to lifecycle stages with its outcome.
- Missed: a few minutes after a missed start the owner calls or emails and offers a new time within the next two days. A rebooked meeting stays in this step, and after the agreed number of no-shows the request closes as a no-show and goes back to nurture.
A recording or AI notetaker starts only after every participant agreed. The invite says when a call will be recorded or transcribed, and the owner asks again at the start. In HubSpot custom meeting outcomes, up to 30, need Sales Hub or Service Hub Professional, and a saved outcome cannot be edited. In Chili Piper, marking a no-show updates the CRM field and can credit the rep back in the rotation.
5Review the week
- Weekly speed review
- Report the week's speed
- Tune rules and coverage
- Week reviewed
Every week, on the same day and at the same time, the sales manager and RevOps look at how fast requests were answered, with last week's change log open. The agent pulls the week's requests from the CRM and reports:
- Speed from the stored submit time to the first personal email, call or booked meeting, as the median and the slowest tenth, in wall clock time and in business hours.
- The funnel: requests, junk, sales fits, calendars shown, booked at once, booked by a rep, held and no-shows.
- Every missed target by rep, weekday and hour, with a sample of wrong routings and rejected fits.
The CRM's own response time can start at assignment, so the report counts from the submit time. The famous five minute figures come from a 2007 study of six companies, and the report shows your own numbers instead.
Then the sales manager and RevOps fix what caused the misses:
- Coverage first: the rota or the pool size changes before the target number does.
- Wrong routing: the match or routing rule is fixed, and the requests it touched are reassigned.
- False spam: real buyers move out of the spam folder, and the rule that caught them is loosened.
Each change gets one line in the log with its reason, so next week's report shows its effect. When the same misses come back every week, or the target gets looser while coverage stays the same, the review needs a closer look.
Compliance checks
The playbook carries checks for the EU, Germany and the US. Four examples:
- Under GDPR the privacy notice covers answering the request, and marketing email needs its own unticked box.
- Data enriched from sources other than the buyer comes with its own duty to inform under Art. 14 GDPR.
- In the US, dialers, prerecorded calls and texts to mobile numbers need prior consent under the TCPA, so calls are made by hand.
- Recording or transcribing a call starts only after everyone agreed. Germany's § 201 StGB and California Penal Code § 632 are the rules behind that check.
They are checks for whoever owns privacy on your team and no legal advice.
Run it in Vanthis
Pick your CRM, booking tool and agent above the Canvas, and the steps and guides on this page follow your choice. In Vanthis the playbook becomes your own Motion with that stack. Your agent, Claude or ChatGPT, asks which tools your team uses, then works through it step by step and drafts every reply for a person to send. To run it somewhere else, download it as Markdown or as an agent skill.


