Chatbot quiz: buttons, tags and qualification with “Condition”

How a quiz works in CHBT: buttons, branches, tags

CHBT has no separate “survey engine”, and that is rather a plus: a quiz is built from the same blocks as any flow, so you can weave it in anywhere. The template has three blocks: a “Message” with two buttons, a name “Data collection” and a “Message” with the result. The trigger is /start.

A quiz answer is recorded in one of two ways, and they are not mutually exclusive.

• Button → branch → tag. Each button in a “Message” has its own exit. The branch has “Action → add tag” (size:big) or “set variable”, after which the branches merge into the next question. Tags are visible in “Contacts”; you filter by them and build a “Condition”.
• “Data collection” into a custom field. For open questions (“Kitchen area in square metres?”) — the field area with “number” validation. The value is saved to the contact card; if you turn on “to variable”, you can insert it into the result: “Two options fit {{area}} m²”.

Branching works in both editor modes: in “Steps” you choose a target block for the button, while on the “Canvas” (Basic plan) arrows are much easier to read with five questions of four options each. One flow works in all channels — Telegram, MAX, VK, the website widget. Variables are inserted into any flow message in curly braces.

How many questions and in what order

A rule that holds on almost any audience: 3–5 questions, the contact last. Every extra question before the phone cuts the share of people who finish; every removed one lowers qualification accuracy. The order:

1. An easy choice without thinking — the item type, the format, “for myself or as a gift”. The person taps and gets drawn in.
2. The parameters you need for the estimate — area, timing, number of people. One open numeric question is acceptable here.
3. Budget or readiness — as ranges on buttons, never as open text.
4. Contact — a phone with format validation; you can ask for the name earlier and address the person by it.

Technical limits: up to 4 buttons per question — readable on a phone; VK shows no more than 10 buttons, two per row. There will be no pictures for options in Telegram, MAX and VK — the bot sends only text and buttons, so name the options so they are clear without visuals. Show progress in text: “Question 2 of 4” at the start of the message reduces drop-off halfway.

Three ready-made sets: kitchens, dentistry, English

Three sets you can take as is and rename the tags to suit you. In brackets — the tag the button sets.

Custom kitchens

1. What layout? — Straight (layout:line) / L-shaped (layout:l) / With an island (layout:island) / Not sure yet
2. Kitchen length in metres — “Data collection”, number, field length
3. When do you need the kitchen? — This month (when:now) / In 1–3 months (when:soon) / Renovation still in progress (when:later)
4. Budget — up to 150k / 150–300k / 300–600k / from 600k (budget:1…budget:4)
5. Where should we send the estimate? — phone

Dentistry

1. What’s bothering you? — Pain right now (need:urgent) / Hygiene cleaning (need:hygiene) / Bite correction (need:ortho) / Prosthetics or implants (need:prosth)
2. Have you been to us before? — Yes / First time (new)
3. When is convenient? — In the next few days / This week / Just checking prices (info-only)
4. Phone for the appointment

English courses

1. Why the language? — Work (goal:work) / Moving or an exam (goal:exam) / Travel (goal:travel) / For a child (goal:kid)
2. Current level — Beginner / I understand but don’t speak / I speak with mistakes
3. How many hours a week can you study? — 2 / 4 / 6 or more (hours:2…)
4. Format — Group / One-to-one (fmt:solo)
5. Where should we send the trial lesson schedule? — phone

In dentistry, the “Pain right now” button should lead not further into the quiz but straight to the phone and the “Operator” block: a person in pain doesn’t need a fourth question. This is the first example of qualification inside a quiz.

Qualification: “Data collection” + “Condition” on tags

A quiz without qualification is just a long form. It makes sense when the answers change what happens after the phone. The tool is the “Condition” block, which checks tags and variables.

There are two ways to qualify. By points: the “Add points” action adds a number to a variable, and the “Condition” compares the total — “greater than or equal to 5”. Or by tags: each button sets a tag, and the “Condition” checks their combinations. Within one “Condition” branch several rules work as “and”, and branches are checked in order from top to bottom.

Branch	Rules	What next
Hot	has when:now and has budget:3 or budget:4 (two branches with the same outcome)	tag hot → “CRM deal” → “Notify operator” → “Operator”
Warm	has when:soon	tag warm → a message with work examples → a 2-day “Pause” → the question “Decided on the layout?”
Otherwise	—	tag cold → the material “How to prepare for the measurement” as a link, without a manager call

For numeric fields the condition is written on a variable: length greater than 4 — a large order, a separate branch. The value must be saved “to variable” in the “Collect data” block, otherwise the “Condition” won’t see it. Comparison operators and typical mistakes are covered in the help article on conditions and branches; hot/warm/cold terminology on the example of one bot — in the marketer’s glossary.

The result of qualification for a manager: hot leads arrive as conversations with the “operator” status and a deal on the kanban board, warm ones warm up by themselves, cold ones don’t eat the team’s time. If part of the audience just wants to “check prices” (the info-only tag), send them the price list as a link and don’t hand them to an operator — that’s how managers stop complaining about “junk requests from the bot”.

Where the result goes and where to place the quiz

After the quiz ends, the data lives in four places, and each solves its own task.

• “Contacts” — a card with the phone, tags from all answers and fields from “Data collection”. A tag filter gives a segment (“everyone who chose an L-shaped kitchen and a budget from 300k”); the export is CSV.
• “CRM” — a deal from “Action → Deal in CRM” with a title assembled from variables: “Quiz: {{name}}, {{length}} m”. The manager moves the kanban stages.
• “Conversations” — if the flow ended with an “Operator” block. The manager sees the whole conversation and the quiz answers before the first call.
• External systems — “Action → HTTP request”: a POST with contact fields and variables to Make, n8n or your own server, and from there to amoCRM, Google Sheets, anything. How to choose between the built-in CRM and sending data out — in the article on leads from a bot to CRM.

An email to the owner about a new request goes out automatically on the first saved phone. Placement: a deep link https://t.me/ваш_бот?start=quiz_ads in ads and posts (the payload is the source tag; set the tag src:ads in the first block after the “Deep link” trigger), a button in the VK community menu, the website widget with a proactive message on exit intent — “Find the right option in 4 questions?”. On a website a chat quiz often replaces a form: a comparison of approaches is in the article chat or a contact form. If you don’t need qualification and a phone is enough, the “Lead capture” template is simpler.

Plans: all quiz blocks, including “Condition” and “Action”, are available on the free plan (30 conversations a month); for ad traffic — Basic, 650 ₽/month per bot with no conversation limit. Open the “Quiz bot” template and replace the questions with your own.