In short
Should you score demo requests or just route them?
Do both, in that order. Score each demo request on fit from three answers, such as team size, current tool, and timing. Then route it before the conversation ends, so good fits get a time to book right away and everyone else still gets a prompt, polite reply.
On this page
Advice on demo requests usually goes one of two ways. Either every request goes straight onto the sales calendar, or each one waits for a lead score built from many signals. The first fills the calendar with calls that were never a fit. The second makes a ready buyer wait for a number.
There is a middle path. Score each request on fit from three answers. Then route it before the visitor leaves the page.
What does "just route them" get right?
Someone who asks for a demo has already raised their hand. Making them wait while a score is worked out wastes the moment they care most. That part of the advice is right. A score should never slow the reply.
It is also right when requests are few. If a business gets a handful of demo requests a week, reading each one takes minutes, and booking them all is fine. The post on whether small businesses need lead scoring covers that case.
The advice stops working when there are more requests than open times. Picture a team of two that wants a free plan and a team of 80 ready to switch tools. Both land on the same calendar. Both deserve a reply. Only one needs a call this week, and the calendar cannot tell them apart.
Why does a full lead score slow down demo requests?
Many lead scores add points for things a person does over time, such as pages viewed and emails opened. That suits a long list of contacts who have not asked for anything yet. A demo request is different. The person has already asked.
Points for activity build up slowly, so the score is ready after the moment has passed. Asking ten questions to build a fuller score has a cost too. Each question is one more round of back and forth before the visitor sees a time.
The difference between these two kinds of signal is explained in fit vs engagement scoring. For a demo request, fit is the part that matters. It can be asked for in one short conversation and scored as soon as it is answered.
Which three answers are enough to score a demo request?
Ask only what decides whether a call is worth it. For software sold to teams, three answers usually do it. The scoring below is an example. Use your own smallest account and your own timing.
| Question | Why it matters | Example scoring |
|---|---|---|
| How many people would use it? | Shows whether the account is big enough for a call | Full credit at 20 people or more. A smaller number scores lower. |
| What do you use today? | Shows whether they are switching, and from what | A grade for each answer, from Best fit down to Not a fit |
| When do you want to start? | Shows whether the project is now or later | Sooner scores higher |
A question someone skips should not count as a zero. Someone who would rather not share their team size has not told you anything bad. Score what they did say, and leave the rest out.
The B2B software page shows these questions in a full form.
How do you route a scored demo request right away?
Decide one next step for each score range before any request arrives. Then every request gets its step at the end of the conversation, not hours later in an inbox.
In Qualiform, the B2B software template starts with team size, current tool, and timing, and team size counts most. Scoring and routing run in code from your own rules, so the same answers always get the same score and the same next step. When a rule offers a time, the AI gives your scheduling link, or times from your own hours, in its closing message.
Example cut-offs, which you set on the Routing tab:
- 70 and up (Hot): offer a time to book.
- 55 to 69 (Warm): say someone will be in touch today.
- 40 to 54 (Cool): say someone will be in touch this week.
- 15 to 39 (Cold): say someone will be in touch.
A skipped question is left out of the score instead of counting as zero. If too little was answered, the lead is not offered a time on its score alone. It goes to the fourth rule, and you choose what that rule says. No time is offered to anyone until you save the Booking tab once, with your hours or a scheduling link.
Scoring demo requests on fit means asking the three things that decide whether a call is worth it, then letting the score pick the next step at once. The guide to lead routing rules shows how to set each step.
To check your setup, read a week of demo requests next to what became of them. If a deal you won scored low, change one of the three questions or how much it counts.
Common questions
Should a demo request form turn anyone away?
Rarely. A small team or a later start date is a reason to score lower, not a reason to refuse a reply. In Qualiform, the rule that tells a visitor they are not a fit is off until you switch it on.
What if a lead you want ends up with a low score?
Change the question or how much it counts. In Qualiform, every lead carries a line saying how it got its score, so you can see which answer pulled it down.
Does the visitor see their score?
No. In Qualiform, the AI never tells a visitor their score, their priority, or the reason for either, even when asked.