The five-minute rule for sales chatbots

A lead who messages you at 2 a.m. is not going to still be interested by the time you check your phone at nine. The data behind this book is blunt about it: the odds of qualifying a lead drop by roughly 21 times if you wait even thirty minutes to respond, against an industry average response time of about 42 hours. That gap isn't a staffing problem you can hire your way out of: nobody is paying a team to sit awake for the 2 a.m. lead.

The instinct is to see a chatbot as a lesser substitute for a human reply. The more useful frame, and the one this kit's book leans on, is that a chatbot is a filter standing at the door of your business, not a replacement for the person who eventually closes the deal. Its job is narrower than "talk to everyone": it's "catch the moment while it's hot, and only bring you the people worth your time."

The Hook-Value-Ask script, and how to write your first flow

The book calls the ideal, friction-free version of a sale the "Happy Path": the ordered sequence a good-fit customer follows from hello to purchase, assuming nothing goes wrong. Before opening any chatbot software, it has you sketch this path on paper as three linked moves: Hook, Value, Ask.

The Hook is the greeting, and it earns permission to keep talking: it has to reference whatever the person just did, not open with a generic "how can I help you." The Value is what you actually give them: the answer, the resource, the thing they came for. The Ask is the smallest possible next step (an email, a click, a one-word reply), never the full pitch on message one.

Worked example from the book, for an e-commerce jacket seller responding to someone who messaged from an Instagram post: Hook: "Hey, great taste. That jacket's one of our best sellers. Want to know about the fit, or see a discount code?" Value: a size note plus a link to the chart. Ask: "We've got a flash sale on outerwear ending tonight, want the link?" Three exchanges, no form, no "please leave your details."

The book pairs this with a rule worth stealing on its own: match the greeting to how the person arrived. Someone who clicked a coupon ad wants the coupon in the first line, not a generic hello, and someone who direct-messaged a specific question about shipping wants that question answered before anything else. Sending the coupon script to the shipping question, or the reverse, is what it calls the fastest way to lose someone who was already interested.

Once the Happy Path is mapped, the accompanying checklist has you add qualifying questions early (before asking for contact details) so the flow filters out obvious non-fits gracefully instead of dragging them through the whole script. And every message, the checklist insists, should end in a button-based choice rather than an open question, because typing is friction and a tap is not.

This is deliberately not a technical chapter. The book's own argument is that the software comes second: a badly mapped flow built in a sophisticated tool is still a badly mapped flow. Map the path on paper first, in your own words, before you touch a flow builder.

Where people go wrong

The most common mistake is skipping the paper stage entirely and building straight inside a flow-builder tool, which tends to produce a maze that mirrors the software's defaults rather than an actual sales conversation. A second is answering every entry point with the same generic greeting: treating a warm message from someone already engaged with your content exactly like a cold click from an ad, which reads as not having listened.

The third is optimizing for volume instead of fit. It's tempting to see every incoming message as a win, but a chatbot that lets everyone through to your calendar produces the same overload a human inbox does, just faster. The book's own math on this is specific: nearly two-thirds of lost sales trace back to reps talking to people who were never qualified in the first place. A few knockout questions early in the flow do more for close rate than any amount of extra traffic.

Chatbots are one piece of a bigger automation decision (what to hand to software first, and what stays human), which we cover at the system level in the AI & Automation guide.