Customer insights from the questions customers ask

Customer insights are what you learn about what your customers need, why they buy and where they get stuck, clearly enough to act on. Big companies pay research agencies and data platforms to find them. A founder already has a better source arriving every day, and it’s the questions customers ask. Each one is someone telling you, in their own words, what they wanted from your product at the moment they wanted it.

This guide covers what those questions tell you, how to collect them without sending a survey, and how to turn each kind into a change you can ship.

Deacon is an AI customer support agent built for founders who handle support themselves. It answers your customers in seconds from your own docs, and it groups what they ask into topics with a count of the people behind each, so you see what they’re stuck on and what they want next. There’s a free plan, and it needs no card.

What counts as a customer insight

An insight is more than a number. “40 people asked about exports” is a count. It becomes an insight once you know why they asked and what you’ll change.

Say most of those 40 asked from your pricing page, before signing up, whether they could take their data with them if they left. They’re worried about being locked in. The insight is that your pricing page should say exports are on every plan, and it’s something you can fix this afternoon.

A useful insight has three parts. It says what happened, why it happened and what you’ll do about it. If you can’t name the third part yet, keep reading the questions until you can.

Why questions beat surveys for a small company

A survey hears only about what you thought to ask, and only from the people willing to fill it in. A question arrives when a customer needs something, from whoever needed it, including people who haven’t bought yet. Nobody had to be asked.

Questions come in the customer’s own words. “Can I invite my accountant?” tells you more than a tick beside “collaboration” on a form. Those words are also the ones to use on your site, because they’re how the next person will search.

They cost nothing to collect, because you’re answering them anyway. And they’re about your product, your pages and your prices this week. Market research tells you about a market. Questions tell you about you.

They do have a blind spot. Questions come only from people who cared enough to ask. A visitor who left your pricing page confused and never wrote in isn’t among them. So read them beside your website analytics, which show where visitors leave, and talk to a few customers yourself each month.

What customers’ questions tell you

Most questions fall into a handful of kinds, and each kind points at a different part of your business.

Feature asks show what to build next

“Can it do this?” and “Please add this” are the same signal, so count them together. Count people rather than messages, and note whether each one is a customer or someone still deciding. Ten people deciding whether to buy who all ask about one integration is a sales problem today. Ten paying customers asking is a reason some of them might leave.

Bug reports show what’s broken for real people

Customers rarely write “bug”. They ask why their export is empty, or why the page won’t load. Treat a question like that as a report, try it yourself and fix it before the next person asks. For everyone who writes in about a bug, others may have hit it and said nothing.

How-to questions show where the product or the docs fall short

When people ask how to do something your product already does, either the control is hard to find or nothing explains it. The page they asked from usually tells you which. A question asked from inside your app points at the product. One asked from a help page points at the page.

Pricing questions show what your pricing page leaves out

“Is there a free trial?” and “Do you charge per seat?” are sentences your pricing page is missing. They come from people deciding whether to pay you, so they’re worth answering on the page itself rather than one person at a time.

Account and billing questions show where billing surprises people

Refunds, failed payments and cancellations need you, and nothing else should answer them. They also tell you something. Several people asking why they were charged means your renewal reminder is missing or unclear.

Requests for a person show where self-service stops working

When someone asks for a human, read what they asked just before. It’s often a question your content didn’t answer, or one about money. Fix that and fewer people need to ask.

Feedback gives you the words for your homepage

Praise and complaints with no question in them still count. A customer who writes “this saves me an hour every Monday” has written your next headline. Keep their exact words.

Questions your docs couldn’t answer show what to write

Every question you couldn’t answer from your docs is a page you haven’t written yet. Write the answer once, in the words people used, and put it where they were stuck. How to write knowledge base articles shows what that looks like.

The language people write in shows who’s finding you

If a steady share of questions arrive in Spanish or German, people from those markets are finding you, whatever markets you meant to reach.

Here’s where each kind of question usually leads.

How to collect customer feedback without a survey

You don’t need a new tool to start. You need every question in one place, kept the way the customer wrote it.

Start with the places questions already arrive. That’s your support email, the chat on your site, sales calls, replies to your onboarding emails, cancellation messages and any community you run.

Keep the customer’s words. Don’t write “asked about SSO” when they wrote “Do you support Okta?”, because the exact words tell you what they use and what they’d search for.

Note who asked and where. Record whether they’re a customer or still deciding, which plan they’re on and the page they asked from.

Group the questions one answer would satisfy. “Do you have SSO?” and “Can we sign in with Okta?” are one ask, however differently they’re worded.

Count people, not messages. One stuck customer can send ten messages about the same thing, and one bad afternoon shouldn’t look like a trend.

Read the list on a fixed day. Once a week is enough for most small companies, and a fixed day stops it becoming something you’ll get to later.

How to act on customer insights

An insight only counts once something changes. For each group of questions, pick one of five moves.

1. Fix the product when the same how-to question or bug keeps coming back.
2. Fix the page when a question comes from a page that should have answered it.
3. Write the answer when the question is fair and nothing you’ve published covers it.
4. Put it on the roadmap when enough of the right people ask. Keep a note of who they were, so you can tell them when it ships.
5. Say no, plainly, when it’s something you won’t build. A clear “we don’t do that” on your site saves every future asker a wait for your reply.

Then watch the count. If people keep asking after your fix, it didn’t reach them, so move the answer to where they were when they asked. When the count falls, go to the next group down the list.

How Deacon turns questions into customer insights

Deacon answers your customers and keeps the tally for you, so the insight arrives without the admin.

You add one script tag to your site and point Deacon at your help pages, files or pasted text. From then on it answers your customers in seconds, day or night, in whatever language they write in. When your content doesn’t cover a question, it says it doesn’t know instead of guessing, and asks for the visitor’s email. You get an email when they leave one or ask for a person, and you reply from the dashboard.

Topics group the questions one written answer would satisfy, whatever the wording and whatever the language, and count the people behind each. A topic is listed once two people have asked. Most topics get one of seven types, which are bug report, feature ask, how-to, pricing, account and billing, wants a person and feedback. A topic where two types tie for the lead gets none. “Can it do this?” and “Please add this” both count towards a feature ask, and greetings, thanks and off-topic messages are never grouped at all.

You can sort topics by how many people asked or by when they last came up, or show just one type, so this month’s feature asks are one click away. Open a topic to read its newest questions in visitors’ own words, with how many your content didn’t cover and how many people left straight after asking. Mark it done once you’ve acted, and it stays at the bottom of the list until more people ask.

Analytics › Widget shows how many messages came in, how many people sent them and the share Deacon answered, each against the period before. It lists the languages people wrote in as soon as any question isn’t in English. And once one page’s questions go unanswered more often than anywhere else on your site, it names that page, so you know which one to fix first. Every conversation is saved word for word, with the page the visitor was on, and you can search them all by what visitors asked.

Every question your content didn’t cover has an Answer this button. Write the answer once and press Save & check. Deacon asks itself the question again and shows you the reply it now gives, and when that reply answers it, how many other open questions your answer covers too. Every answer you write becomes part of what Deacon knows, so it can answer the next person who asks and needs you a little less each week.

The same script counts your website’s visitors, where they came from and which goals they reach, such as a sign-up, so you can read what people asked beside what they did. That’s website visitor tracking, with no second script to add.

Deacon runs no surveys and puts no rating on a conversation. What you get is what your customers actually asked, counted and grouped. Every feature is on every plan, including the free one, which needs no card and has no end date.

Questions about customer insights

What’s the difference between customer insights and customer feedback?

Customer feedback is what customers tell you, such as a question, a complaint or a feature request. A customer insight is what you conclude once you’ve seen the pattern and the reason behind it. Twenty people asking whether you work with Slack is feedback. Noticing that they all ask just before inviting their colleagues, and that the answer belongs on your invite screen, is an insight.

How are customer insights different from market research?

Market research studies a market, such as its size, its buyers and your competitors, often before you’ve built anything. Customer insights come from the customers you already have and the visitors already on your site. Once your product is live, the second is cheaper, more specific and arrives every day.

Is this the same as Dynamics 365 Customer Insights?

No. Dynamics 365 Customer Insights is a Microsoft product. Microsoft’s overview describes it as a customer data platform combined with real-time journey orchestration, for data analysts, marketers, sellers and customer service agents. This guide is about the practice of learning from your customers, which any company can do.

How many people need to ask before a question matters?

Two people asking the same thing is worth watching, and Deacon lists a topic from the second person. Act when a topic keeps growing, or when the people asking are the customers you most want. One question from a customer you’d love to keep can matter more than ten from people just looking.

Can Deacon run a survey or rate its conversations?

No. Deacon runs no surveys, and there’s no rating and no thumbs up or down on an answer. Its insights come from what people ask, the share it answered and the questions it couldn’t.

Is this on Deacon’s free plan?

Yes. Topics, Analytics › Widget and every conversation are on every plan, the free one included. The free plan gives you 50 answers a month, needs no card and has no end date. See the plans