Pre-Sort Incoming Inquiries
The first message decides whether an inquiry turns into a conversation. Route it through three fixed tracks and you know at first glance what this is about, and so does your contact.
Why the first message so often leads nowhere
Someone writes “Hi, I have a quick question” and that is all there is. No topic, no reason, no hint whether this is about fit, about pricing or about an urgent problem. That message sits among twenty like it, and not one of them tells you which is worth your time. People landing in chat rather than on the phone is the norm by now: in a Kantar survey of 11,056 adults across 22 markets, 73.3 percent said they prefer messaging when dealing with a business.
A message like that gets answered in the evening, after the last appointment, and by then the window has usually closed. An analysis of 5.7 million leads from more than 400 companies shows how narrow that window is: responding within the first five minutes converts eight times better than responding after six minutes or later. The same analysis shows how rarely that happens. 77 percent of inbound marketing leads never get a reply at all. Not because nobody wants to answer, but because every single message has to be decoded before anything useful can be written back.
The fix is not typing faster, it is a different first message. It asks nothing back. It frames the situation in two or three sentences: what you typically help with and who this is meant for. Only below that comes the question, with three options to tap. The order is the actual lever here: frame first and you set the categories the other person answers in. Ask first and you get their categories back, and those look different for everyone.
A good sorting question starts from what the other person wants to know, not from what you sell. “Consulting, implementation, other” is your org chart, it helps nobody, and the catch-all branch ends up collecting half the traffic. “Whether this fits me, what it costs, I have a specific problem” are the three questions that sit in front of almost every decision. The options have to be mutually exclusive and cover the field between them. And there should be three of them: every extra option turns a tap into a read, and from there nobody decides in two seconds.
How to build the sorting path
Feed every entry point into one start node
Chat button on your site, reply to a story, keyword from a post: wherever someone comes from, the path continues the same way. That is not convenience, it is what makes the answers comparable in the first place. Three parallel tracks give you three data sets you will never lay side by side, and every change has to be made three times.
Frame first, then ask
The first message node asks nothing back, it gives context: two or three sentences on what you typically help with and who this is meant for. Someone who does not know what you handle will answer the question below by their own yardstick, or not at all. Those two sentences cost you nothing and carry the response rate of the question underneath.
Cap the choice at three options
The structure allows no more than three buttons here, and that is deliberate. Three options are taken in at a glance on a phone screen, so people tap through instead of stalling over a list. And picking the wrong track still beats never answering: a wrong track you correct in one message, silence you do not.
Give every track something different
At the end of each branch sits its own orientation asset, a PDF or a short video: a fit checklist, an explanation of how your pricing works, a short guide to the most common problem. The same freebie three times says nothing wrong, but it devalues the question before it. Someone just told you something about themselves and got back what everyone gets. Next time they tap more carefully. The difference in the material is the only proof their choice changed anything.
A follow-up question that records something
After the asset, each branch adds one more question with fixed options. The answer is stored as a variable and sets a tag, so your later follow-up knows which track the contact came from and what they have already read. Across the whole path it stays at three to five qualifying questions. And it comes after the material on purpose: before it, the question is a hurdle; after it, the obvious next step.
Merge, hand over, then split again
All three tracks converge on a shared goal of type “lead_qualified”, immediately followed by the handover to your CRM. That shared point keeps your reporting readable, because you look at one rate instead of three. After it the paths separate again: each track closes with the call to action that suits it, from an intro call to a direct answer to the problem they named.
Example scenario: an offer that needs explaining, with a chat entry point
A provider with an offer that needs explaining has a chat button on the website and also replies to story reactions on Instagram. More first messages come in than can be answered one by one, and most of them are just a greeting.
Every inquiry is read and answered by hand, usually in the evening after the last appointment. With no stated reason, each conversation opens with a question back, and the next reply takes another day. That puts the provider right at the market average: in a study of 2,241 companies published in Harvard Business Review, 23 percent never responded to a web inquiry at all, and those that did took 42 hours on average. Anyone who has moved on by then disappears unnoticed, and afterwards nobody knows what it was supposed to be about.
The path is rebuilt once in the messenger tool, the core of it in under six hours. The opening is no longer a question back but a framing plus one question with three options. Whoever picks the pricing option reads the pricing model right there in the chat instead of waiting for it. Every choice files the contact into a track with its own tag, and the CRM record already shows the topic and what the person has read. Whoever calls next no longer has to ask what this is even about, and the conversation begins where it used to arrive after ten minutes.
What you get
The sorting tree as a visual blueprint
The full structure at a glance: trigger, first message node, the choice with its three buttons, the three branches and the point where they converge. Every node states the job it does and what the text there has to accomplish, so you are not guessing when you write it.
The reasoning behind the split
Why these three tracks fit your offer, which question separates them cleanly and where an inquiry belongs when it fits two of them. This is the thinking that a self-built sorting path usually gets wrong.
The asset list per track
For every branch the blueprint names the orientation asset that belongs there and what it has to accomplish: fit checklist, pricing explainer, short guide. You can see immediately what you already have on the shelf and what is still missing.
Variables, tags and the handover point
Which answer gets stored as a variable, which tag it sets and where the contact is handed to your CRM. The blueprint marks that point and tells you which fields should arrive there.
A buyer persona as the foundation
Analysing your website and documents produces a persona with more than 50 data points on motives, questions and objections. The three tracks are derived from it rather than guessed.
More funnel blueprints
Sort first contact before it disappears
You describe your offer, you get the sorting tree: three tracks, the reasoning behind them, the asset list and the handover point. One-time payment, no subscription.
Build my funnel blueprintOne-time payment, no subscription. You get the complete strategy and overview first.