A chatbot routes an enquiry through two questions towards a calendar or human support.Chatbot enquiry qualification routes

A chatbot is most useful when it helps a visitor take the next sensible step. It becomes a barrier when it asks for too much, hides the human route, or tries to imitate a conversation it cannot complete. For a small service business, you do not need a complicated script to make a useful start. You need two questions that sort an enquiry into a route: someone wants an answer now, someone is considering a booking, or someone needs a person.

Quick answer

Start with one question about the visitor’s goal and one about their readiness to act. Use their answers to offer a short FAQ route, a booking route or a clear human handoff. Keep every option visible on a phone, do not make contact details a condition of help, and test the full flow yourself. The aim is not to “qualify” people out. It is to reduce friction while giving you enough context to respond usefully.

Key takeaways

  • Two well-chosen questions are usually enough for a first chatbot flow.
  • Ask about the visitor’s job to be done before asking for their details.
  • Offer booking, self-service and human help as honest routes.
  • Keep the human route available when an answer is unclear or sensitive.
  • Use optional follow-up fields only after the visitor sees a useful next step.
  • Test the flow on a real mobile viewport, not only inside an editor.
  • Review unanswered questions and handoff requests to improve the script.

Why two questions are enough at the beginning

Website visitors arrive with different levels of certainty. One person may simply want to know whether you cover a particular service. Another may be comparing providers and wants an appointment. A third may have an unusual problem that does not fit a menu. If every visitor receives the same long form, you make all three work harder than necessary.

Two questions force useful discipline. They make you decide what the first service workflow actually is. They also prevent the common mistake of collecting data without a plan for using it. A chatbot does not need to diagnose every situation. It needs to recognise enough to route the conversation safely.

Choose the first qualification question

The first question should describe the visitor’s purpose in ordinary language. Avoid internal labels such as “lead type” or “sales stage”. A simple version is: “What would you like help with today?” Give three or four buttons, not an open text box as the only choice. For example: “Find an answer”, “Discuss a service”, “Book a call”, and “Something else”.

Those choices should reflect real routes your business can support today. If there is no reliable knowledge base, do not promise instant answers. If you do not take bookings, do not add a button merely because it looks professional. A smaller honest flow is better than a large imaginary one.

Use the second question to decide the route

The second question adds just enough context. For a service enquiry, ask: “Are you looking for general information, or would you like to talk through your situation?” For a booking path, ask: “Would you prefer to see available times or leave a short message for our team?” The answer changes the next screen, not the visitor’s worth.

Keep this question specific to the route selected first. A visitor who chose “Find an answer” does not need to see a booking question immediately. Instead, offer the relevant topic and show “Speak to a person” beside it. A visitor who chose “Discuss a service” may benefit from a short choice between availability, scope and price approach, but only if you can answer those topics accurately.

Build three routes, not one tunnel

A useful first version has three exits. The FAQ route gives a concise answer or points to a clear resource. The booking route opens a calendar or collects a preferred time. The human route sends the context already provided to the right person and tells the visitor what will happen next. No route should trap the visitor in a loop.

Write the handoff plainly. “I want to make sure you get the right answer. You can send this to our team, and we will reply using the contact details you choose to provide.” If a response time is not guaranteed, do not invent one. If the chatbot cannot handle an issue, say so rather than pretending it has understood.

What to collect before a human handoff

Collect only what helps the next person respond. A good minimum is the selected topic, the visitor’s free-text question and a contact method if they want a reply. For an appointment, you might also ask for a preferred day or a time zone. Explain why a field is useful. “Add a short description so the right person can prepare” is clearer than a generic “Message”.

Do not make a telephone number compulsory unless the conversation genuinely requires a call. Do not ask for sensitive information through a general website chatbot. If your work has privacy, medical, legal, financial or safeguarding implications, use a route that is designed for that context and include an appropriate caution. A generic chatbot is not a substitute for professional advice or an emergency channel.

Make the booking route useful

Booking is a promise of a next action, so it needs a clean handoff. The chatbot should say what the meeting is for, how long it is likely to take and what the visitor needs to do next. If your calendar asks for an email address, let that request happen in the booking form rather than repeating it in the chatbot without reason.

Before you automate reminders, make one manual test booking. Check the confirmation page, email wording, calendar invitation and cancellation route. Look at them on your phone. A smooth chatbot opening is undermined by a confusing confirmation message or a calendar page that will not fit a small screen.

Test unclear enquiries deliberately

Do not test only the ideal path. Try “I’m not sure”, a question that does not match a button, a request for a person and a visitor who changes their mind. In each case, there should be a calm escape route. A useful fallback is: “I may not have understood that. Would you like to choose a topic, see how to book, or send your question to a person?”

Also check for accidental dead ends. Every final reply should offer a next action or a way to close the conversation. Buttons must be reachable by keyboard, labels must make sense out of context, and colour alone should not carry meaning. These are practical usability checks, not decoration.

Review the flow after real conversations

Once the flow is live, review patterns rather than judging it by a single chat. Which buttons do people choose? Where do they ask for a person? Which questions produce a blank response or an unhelpful answer? You may find that a missing FAQ is more valuable than another qualification question.

Keep a small test log with the date, device, route selected, expected result, actual result and any follow-up needed. This makes improvements deliberate. It also gives you a record of what changed if someone reports a problem later. Treat the script as an operational tool, not a one-off piece of copy.

What does the two-question flow look like in practice?

Imagine a small web design studio that gets three kinds of message through its contact page. Some visitors want to know whether the studio works with existing WordPress sites. Some are ready to discuss a redesign. Others are asking for help with a current project. The studio already has a service page, a short introductory call and a support inbox. Its chatbot can direct people to those three things without introducing a new process.

The opening question is ‘What can we help you with?’ The choices are ‘Ask about a website project’, ‘Get help with an existing project’ and ‘Something else’. When somebody chooses a website project, the follow-up asks ‘Would you like to see what we cover or talk through your project?’ The first choice shows the service page and an option to get in touch. The second explains what the introductory call covers and gives the booking link. Existing customers go straight to support without repeating the new project questions.

A visitor who types ‘My site is down’ gets a different response. That message might come from an existing customer or from someone the studio has never worked with. The bot should avoid guessing which it is or saying a repair has started. It can offer the support contact and say what kinds of request the studio handles. It can also show the visitor how to send a message if the situation doesn’t fit. If the studio cannot provide urgent help, the contact copy should make that clear.

Try writing out each branch with a pen before configuring the chatbot. Write the exact button wording on the left and the exact destination on the right. If you cannot describe the destination in one sentence, the route probably needs more work. ‘Send the visitor to the contact page’ may be too vague if the page contains several forms. ‘Open the existing customer support form and explain what to include’ gives you something you can test.

How do you decide which answers should skip the second question?

Treat two as the maximum for the first pass. Once the visitor has asked for a person, protect that choice. Someone who clicks ‘Talk to the team’ should reach the contact route immediately. A second question about budget, company size or timing can wait for a reply. Asking it first may delay help and can put a useful conversation off course.

The same applies to straightforward factual questions. If the visitor chooses ‘What areas do you cover?’, show the approved service area answer if you have one. Offer a route for visitors who are unsure whether their location is included. Do not make them choose an appointment type to see an answer you already have. This keeps routine enquiries quick and leaves the calendar available for people who actually want to book.

Write a small decision rule beside each reply. A known answer goes to the relevant information. A visitor who explicitly wants a conversation can choose booking or a message. An unclear or sensitive enquiry goes to a person or the appropriate support channel. When two rules match, give priority to the route the visitor asked for. A booking link can still be offered later if it is useful.

Consider what to do when the user changes direction. If a person starts with an FAQ and then asks to book, the bot can show a booking link without starting over. If they change their mind from booking to messaging, carry over the selected service where appropriate. That feels like a continuation and gives the team a useful starting point. Let people correct the subject before sending, particularly when the bot inferred it from free text.

What should a useful handoff message contain?

Write the message the team will actually receive before deciding which boxes to show the visitor. A short example is: ‘Reason for contact: existing website. Visitor’s question: Can I keep the same domain during a redesign? Requested reply: email.’ That gives the person reading it enough to choose the right colleague and prepare a useful reply. It also helps you spot fields which have no obvious purpose.

Keep the visitor’s wording alongside any route label. ‘New project’ tells the team where to start. ‘I’m not sure whether I need a redesign or just a new home page’ tells them what the visitor needs to understand. If the bot summarises an enquiry, make the summary easy for the person to correct. A mistaken summary should not be the only copy the team can see.

Write the message the visitor sees after sending as carefully as the questions. ‘Your message has been sent to our website team’ is suitable only after a confirmed send. If the send fails, show an honest error and an alternate contact option. If the form takes longer to respond, tell the visitor what is happening and make it easy to avoid submitting the same message twice.

Give the handoff an owner. Choose the mailbox or queue that receives the message, and agree who checks it during holidays or busy periods. If a message is sent to an inbox nobody checks, the chatbot has simply made it easier to lose an enquiry. Test a sample from the website to the person who handles it, and ask them whether the context is enough to respond without making the visitor start again.

What should your first test cover?

Build a short test script using real tasks with fictional contact details. Start with a visitor who wants the answer to a common question, one who is ready to book and one who asks to speak to a person. Write the expected outcome in advance. For the FAQ test, success could mean the correct answer appears without a contact form. For booking, it could mean the correct service calendar opens and is usable on a phone.

Add a few awkward cases. Try a query containing two requests, a spelling mistake and a message in which you change your mind halfway through. Try leaving an optional field empty. Turn off the network briefly before submitting a test message and check whether the bot explains that it could not send. If your team does not monitor the inbox outside working hours, check what the bot says then.

Open the public page on a phone and use the chat with the keyboard open. Check whether the buttons and send control remain visible. Then try the same flow with keyboard navigation on a desktop. You should be able to reach the chatbot, move between choices, see which control has focus and close the panel without losing your place on the page.

When you fix a route, rerun its nearest neighbour. A change to the project booking link might also affect the general enquiry link if both buttons reuse the same setting. Record which page, device and route you checked rather than writing only ‘passed’. This makes the log useful when you later add a service, change your working hours or move to a new calendar.

When should you add another question?

Review a small batch of messages after launch, with private information handled according to your own process. Look for repeated requests which the current flow cannot route. For example, if visitors regularly ask about two different services and those services go to different teams, an extra service choice might save a round of messages. If every request goes to the same person, another mandatory question may do little for either the visitor or your team.

Start by changing one question or one reply at a time. Keep the previous wording in your log so that you can restore it if the new version confuses people. Ask the team whether the contact messages are easier to answer and check whether the visitor can still reach each route quickly. With low traffic, direct feedback and a handful of clear examples can be more helpful than an impressive-looking dashboard.

Use the free Chatbot Qualification Checklist from Prodify Digital Pro to review the questions, next steps and handoff before you extend the flow. Begin with one service, one real booking destination and one dependable contact route. You can add detail once you can show who benefits from it and where it changes the outcome.

Get the free Chatbot Qualification Checklist

Use it to check the two questions, route choices, handoff fields and mobile test before you put a first flow live.

Frequently asked questions

What are the best first chatbot qualification questions?

Ask what the visitor wants help with, then ask a route-specific question that identifies whether they need an answer, a booking or a person. Use language your visitor would use.

Should a chatbot collect contact details before helping?

Usually no. Show a useful route first, then ask for the minimum contact detail needed for a booking or human reply.

When should a chatbot hand an enquiry to a person?

Offer a handoff when the visitor asks for one, the request is unclear, the topic is sensitive, or the chatbot cannot give a reliable answer.

Should both questions be compulsory?

No. Skip the second question when the visitor has asked for a person or selected a topic with a clear answer. Ask a follow-up only when it changes the next step.

What should I check on a phone?

Open each route with the keyboard visible. Check that the buttons and send control remain reachable, the booking page opens, and the visitor can close the chat or reach a person.

What if the booking calendar has no availability?

Offer an alternative contact route with a clear explanation of what will happen next. Avoid promising an appointment time the calendar cannot confirm.

Bottom line

Your first chatbot does not need to be clever. It needs to be clear. Two questions can direct a visitor towards a useful answer, an honest booking option or a real person without turning the conversation into an obstacle course. Start with one service workflow, test it on a phone, then improve it using the questions people actually ask.

author avatar
Garry Knight
I'm Garry Knight, the person behind Prodify Digital. I write about email list building, email marketing, SEO, AI search and the tools that connect them. My aim is to make online marketing easier to understand, so creators and small business owners can make informed decisions about building an audience and keeping people engaged. Here you'll find straightforward guides and product reviews that explain what something does, where it fits and which limitations matter. The focus is on clear explanations and useful next steps—not hype, shortcuts or promises of easy earnings.

Leave a Reply