Unusual Questions We Are Not Prepared For

A study of 433 companies found that only 7% answered a web form within 5 minutes, and a familiar message followed: respond faster, use automation, use AI, capture the lead, and become part of the 7%.

Yet a question stayed with me: what happens when the question is unusual? An unusual question is one that no script, FAQ, or workflow was written for, and it carries the asker's own uncertainty.

Speed answers the questions a business expected, and tools create efficiency while leaving understanding, judgment, and responsibility with people. Unusual questions show whether a business understands the person asking. Before buying another tool, find out which questions your business is not prepared for.

What the 5-Minute Message Assumes

The 5-minute message assumes that speed is the problem. Sometimes it is, and sometimes it isn't. The aim here is to examine that assumption, and the people who repeat it deserve no blame.

The statistic comes from the 2017 Drift lead response survey. A secret shopper submitted forms to 433 B2B software companies and measured how quickly each one replied, and only 7% replied within the first five minutes. More than half did not reply at all within five business days.

For that second group, speed was a real problem, and so was silence. The survey's authors recommended real-time messaging, including chatbots that qualify leads inside the five-minute window.

Businesses hear the same story in many forms: more leads, more calls, faster responses, more automation. Each version shares one assumption, which is that the gap between a question and an answer is the thing to fix. The survey measured how quickly a reply arrived, and it left open whether the reply understood the question.

Capture Before Understanding

Almost every sales message in this space gives the same instructions: capture the lead, respond faster, automate the process, and don't lose the opportunity. Few of those messages ask whether the business understands the opportunity, or the person behind it.

The Question Nobody Asks Before Buying a Tool

Before buying another tool, ask why the business needs it. The reason may be fear of missing opportunities, fear of competitors, fear of falling behind, or a genuine business challenge. Only the last one defines a problem, and many organizations buy solutions before defining one.

A working test: choose a tool when the problem fits in one sentence that names who is waiting, what they are waiting for, and what the wait costs them. If that sentence will not form, the purchase is premature.

The 7% Problem

The 7% figure deserves a challenge to its interpretation, and the study itself stands. Becoming part of the 7% does not automatically bring better understanding, better judgment, or better outcomes. A company can answer within 30 seconds and still misunderstand the customer completely.

Take a home renovation company whose website form is answered within seconds by an automatic message listing opening hours and a booking link. One inquiry reads: the house is old, one wall is shared with a neighbor who objects, and the permit may fail, so what happens then? The reply arrives fast and answers a different question.

What Tools Add and What They Cannot Create

Tools route calls, send notifications, book appointments, answer frequently asked questions, and capture details. They cannot create experience, judgment, responsibility, or understanding, because those live in people.

Tools create efficiency inside the capacity a business already has. If a team cannot handle today's inquiries with understanding, a larger volume of inquiries tomorrow creates a larger problem. A marketing automation setup raises the volume a team can touch, and it leaves the team's capacity to understand where it was.

The Unusual Question Behind the Expected One

Businesses train systems to answer opening hours, pricing, services, and processes. These expected questions keep systems busy. A different conversation begins when someone says: \"My situation is different.\"

That is where scripts end, and where judgment begins. An unusual question can wear the clothes of an expected one, and three pairs show the pattern:

• Behind \"How much does it cost?\" can sit \"Why should I trust you?\", a question that no pricing page answers.
• Behind \"What services do you offer?\" can sit \"What happens if this fails?\", a question about risk and recovery.
• Behind \"Can AI answer this question?\" can sit \"Can AI understand why I asked it?\", a question about being understood.

Each unusual question carries uncertainty, and uncertainty is where human conversations begin. The renovation inquiry above fits the second pair: it asks about services in form and asks about failure in substance.

Dependency and the Abilities Behind the Tools

Every generation builds tools to remove effort, and nothing is wrong with that. The risk begins when dependence on every tool weakens the abilities that made the tools valuable: listening, understanding, judgment, and responsibility.

This is a case against dependency. Technology deserves credit where it earns it. The equation \"more technology equals better service\" holds sometimes, because technology amplifies what already exists and creates no understanding where none exists.

The pattern is older than the web. In 1966, MIT researcher Joseph Weizenbaum published ELIZA, a program whose DOCTOR script reflected a user's own words back as questions. Weizenbaum was surprised that people, including his secretary, attributed human-like feelings to a program that only matched patterns, and he later argued against treating computers as replacements for human judgment.

A recent case shows where responsibility lands. In February 2024, British Columbia's Civil Resolution Tribunal decided Moffatt v. Air Canada. A customer had asked the airline's website chatbot about bereavement fares and received incorrect information, and Air Canada argued that the chatbot was a separate legal entity responsible for its own actions.

The tribunal rejected that argument and held that the airline remained responsible for the information on its website, whether it came from a static page or a chatbot. The customer's question carried more than a fare inquiry. It was asked during bereavement, a tool produced the answer, and the company owned it.

Run a Question Audit This Week

A Question Audit shows which questions your business is prepared for and which ones it is not. It takes recent inquiries from every channel and sorts them by how well a script can answer them. Your own lead response process supplies the baseline.

1. Collect recent inquiries from forms, chat, email, and call notes, and remove names and contact details first.
2. Tag each inquiry as Expected (a script answers it), Variant (a script answers it after edits), or Unusual (no script has a branch for it).
3. For each Unusual inquiry, write the question underneath: what the person needed to know before acting.
4. Check what the system replied, who read the message, and how long a person took to give a useful answer.
5. Decide the handoff: which words and situations route to a person with the full message attached.

Choose the handler by the question:

• Choose automation when the question is expected and the answer carries no stakes for the asker.
• Choose a person, with the full message attached, when the question carries uncertainty, trust, or a high-stakes consequence.
• Choose to track the time to a useful answer for unusual questions, next to the time to a first reply.
• Choose capacity before volume: add more inquiries only after the team can handle the current ones with understanding.

Flag the phrases \"my situation is different\", \"what happens if\", and \"why should I\", plus any mention of money, health, safety, or legal exposure. Route those messages to a person.

The audit costs a few hours of reading, and it needs permission to read customer messages under the business's privacy rules. A small sample shows patterns and does not prove how often unusual questions arrive. A business with only a handful of inquiries can skip the tagging and read them all.

The Final Observation

Businesses spend enormous effort preparing answers. Yet growth can arrive disguised as a question nobody prepared for. The expected questions keep systems busy, and the unusual questions reveal whether we truly understand what we are doing.

A tool can answer a known question. Judgment begins when the question itself is unknown.

The real subject here is the uncomfortable truth that businesses prepare for predictable conversations while important opportunities can arrive through the questions nobody expected to hear. The question underneath is whether we are preparing businesses to answer questions or to understand people.

Open the last batch of inquiries, find the ones no script was written for, and read them as people asking for help. A free assessment can review your inquiry flow alongside you if a second read helps.

FAQs

People Also Ask