Ask a Question

Ask, then pause the run until the customer answers or time runs out — typed answers match by fixed rules, or by AI if enabled.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Ask a Question.
  2. Write the Question Text, then choose a Question Type — Multiple Choice, Number, Date, and more.
  3. For Multiple Choice, add up to 20 answers. Leave them empty to take the typed reply as the answer.
  4. Optional, under Advanced Settings: turn on Add Timeout Branch, set the wait, then add steps on the Failure: Timeout branch.
  5. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • With Add Timeout Branch off, the question still expires — after 1 day by default — and the flow carries on past it with no extra steps.
The Add Steps menu open on the canvas, with Ask a Question highlighted.
The step panel with a question typed and Multiple Choice picked as the type.
Add Timeout Branch switched on, with the Timeout amount and unit fields.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Ask a Question under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Only an owner or admin can publish it, and publishing is what makes it run on live conversations.
  • Building and running workflows depends on your plan; see pricing.
  • Nothing outside Inchat has to be connected. The step sends on the conversation's last-interacted channel.

Set up

  1. Open the workflow and click + where the question belongs.
  2. Pick Ask a Question.
  3. Write the Question Text.
  4. Choose a Question Type: Text, Multiple Choice, Number, Date, Phone, Email, Website/URL, Rating or Location. Leave Multiple Choice with no answers listed to capture the customer's typed reply instead of offering choices.
  5. For Multiple Choice, add up to 20 answers; each can have extra accepted spellings (aliases).
  6. Optional, for Multiple Choice: turn on Use AI to understand free-text answers, add a few words under each answer saying what it means, and add steps on the Needs a person branch.
  7. Optional: write text under If the reply matches nothing to re-ask; leave it empty to wait silently instead.
  8. Optional: turn on Save Response As to write the answer to a contact field, a variable, or (multiple choice only) a tag.
  9. Optional, under Advanced Settings: turn on Add Timeout Branch and set how long to wait, and Add Message Failure Branch for when the question itself cannot be sent.
  10. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Question Text
The message sent to the customer.
Question Type
Text, Multiple Choice, Number, Date, Phone, Email, Website/URL, Rating (2–10 stars) or Location.
Limits: A non-multiple-choice type with no options still validates the shape of the reply (for example a real number) before accepting it as the answer.
Choices
Up to 20 answers for Multiple Choice, each with an optional list of other accepted spellings (aliases). Typed replies are matched ignoring case, spacing and full-width characters; a number like "2" picks by position.
Limits: Sent as buttons — WhatsApp shows up to 3 as buttons and the rest as a pick-list; Messenger shows them all. An unrecognised reply is re-asked, and is never guessed by a model unless you turn on AI matching.
Use AI to understand free-text answers
When a typed reply is not one of the answers, AI reads it and picks the answer it means, or none. Each answer then has a box where you say, in a few words, what it means.
Default: off — replies are matched by fixed rules only
Limits: Each answer's hint is up to 120 characters and is never sent to the customer. Multiple Choice with at least one answer only. Each AI read uses one AI message from your allowance.
If the reply matches nothing
Text resent on an unrecognised reply, while attempts remain. This is separate from the Failure: Invalid branch on the canvas, which holds the steps that run once attempts are exhausted.
Default: empty — waits silently instead of re-asking
WhatsApp pick-list label
The button label that opens the list, when there are more than 3 choices on WhatsApp.
Default: Select
Limits: Up to 20 characters. Unused on fewer than 4 choices, or on other channels.
Save Response As
Three independent switches: write the answer to a Contact Field, keep it as a Variable for later steps, or (Multiple Choice only) Tag the contact with the option chosen.
Add Timeout Branch
How long to wait for an answer before giving up and moving on. Switching it on adds a Failure: Timeout branch on the canvas — add a Send a Message step there yourself for the customer to see a message on timeout.
Default: off in the drawer, but the question still expires — see How it works
Limits: 60 seconds to 7 days; the drawer's own default once turned on is 7 days.
Add Message Failure Branch
A path to run if the question itself cannot be sent (no channel, a closed window, a provider error) — separate from the customer never answering. Adds a Failure: Sending Failed branch on the canvas.
Default: off — a send failure leaves the workflow with no branch to follow

How it works

  • The step pauses this run: nothing after it in the workflow happens until the customer answers, the deadline passes, or the attempt limit is used up on unrecognised replies.
  • While it waits, the customer's next reply is claimed as the answer, not treated as an ordinary inbound message: the AI does not answer it, and no Message received-triggered workflow fires on it. The one exception is a customer asking something back, described below.
  • A customer who opts out is not answering. A typed STOP (or any word Inchat reads as an opt-out) is not taken as the answer, whatever the question. On WhatsApp, Messenger, Instagram and Telegram the question also ends. The steps this run had queued that could message the customer are cancelled, and a note on the thread lists them. Runs started by an order, a shipment, a booking or a payment slip carry on. On website chat and email a typed STOP does not yet stop automation: it records no opt-out and the workflow carries on. A menu that offers that very word as an option, or a tap on one of its buttons, is still the customer's answer.
  • That reply is still an inbound message to every other live workflow that has its own exit rule watching for one. A payment chase with "exit on inbound reply" still exits on it, the same as any other inbound would.
  • Only the workflow that asked the question is exempt from its own exit rule on this reply; a live workflow with no such exit rule configured is unaffected either way.
  • Multiple Choice with at least one answer matches by fixed rules first: normalised case, spacing and full-width characters, a bare position number ("2" for the second choice), or any alias you listed. A model's guess is never used unless you turn on AI matching.
  • With Use AI to understand free-text answers on, AI reads only a typed reply those rules could not match. A reply that already matches, and every button tap, never calls AI.
  • AI can only choose one of your listed answers, or none, or needs a person. It writes nothing to the customer: whatever is sent next comes from the steps you built.
  • When AI picks an answer, the steps on that answer's path run as if the customer had picked it, and How the answer was matched reads ai. An exact match reads exact.
  • When AI is unsure, the reply counts as unrecognised: your retry text is sent and an attempt is used, as before.
  • When AI reads a reply as upset, as asking for a person, or as something a menu cannot handle, the steps on the Needs a person branch run at once and no attempt is used. If that branch is empty, the reply is treated as unrecognised instead. That branch only runs when AI matching is available. If AI is off or does not answer in time, the reply counts as unrecognised: it is asked again while attempts remain, and Invalid runs once they are used up.
  • An answer that matches nothing is re-asked, if you set retry text, or waited on silently, and does not count against the attempt limit's final failure until attempts run out.
  • Leaving Multiple Choice with no answers listed switches the step to free-text capture: the customer's next reply is taken as the answer outright, with no matching at all. The exception is a reply that reads as a question back (below).
  • A non-multiple-choice type with no options — Number, Date, Phone, Email, URL, Rating, Location — still checks the reply is a valid one of that shape before accepting it. An invalid reply counts as an unrecognised attempt the same way a Multiple Choice mismatch does.
  • The step always has a deadline, whether or not Add Timeout Branch is turned on. With it off, the question still expires after 1 day by default — or sooner still, if the messaging window would otherwise close first.
  • It simply runs no extra steps when that default deadline passes, rather than waiting forever. Turning the toggle on and leaving the amount at its default asks for 7 days instead.
  • On a windowed channel, a deadline that would land after the messaging window closes is pulled back to end just inside the window instead.
  • Without that pull-back, a default deadline as long as the window would end with it, and the customer would hear nothing when the run continued with a free-form message.
  • If the customer's reply reopens the window before that pulled-back deadline, the next unrecognised attempt restores the deadline back toward what you actually authored, capped by the now-later window edge.
  • A stuck questionnaire is not held open longer than it was authored to be, but it is also not left artificially short once the customer is clearly still talking.
  • The deadline is checked the moment the customer's next message arrives. If that message is late, it is not treated as the answer.
  • The deadline is also checked by a background sweep roughly once a minute, so a question with nobody left to reply still resolves in reasonable time.
  • A message that looks like an automated away-reply is ignored rather than treated as an answer or counted as an attempt. The question is left exactly as it was, still waiting for the customer's own reply.
  • On a free-text question, a reply that reads as the customer asking something back ("How much is one box?") is not taken as the answer. Free-text means any question with no answers listed, whatever its type. The question keeps waiting and no attempt is used. The message goes to the AI agent as an ordinary message: it answers, knowing the question is still open, and invites the customer to answer it. When no AI can answer on the thread (paused, or a person owns it), the message stays in the inbox for a person and the question keeps waiting. A reply saying the customer does not know is still the answer, and so is any reply when the question itself asks for a question ("Any questions?").
  • The recorded answer is exposed to later steps as Answer picked (answer.key), Answer as typed (answer.text) and Answer result (answer.status).
  • Answer result reads matched, unmatched, unanswered or captured, so a Condition step can branch on any of these fields, and on How the answer was matched too.

When it fails

  • AI matching is on, but AI is off for the workspace or channel, the plan has no AI, or the month's AI messages are used up.
  • Or the AI call fails or takes longer than 2 seconds. In each case the reply is treated as unrecognised and re-asked, and exact matches still work.
  • The question itself cannot be sent — no channel to send on, the messaging window is closed, a provider error — and Add Message Failure Branch is off.
  • The contact then simply leaves the workflow: nothing is waiting and nothing runs after it.
  • The question cannot be sent and Add Message Failure Branch is on: that branch's steps run instead.
  • An unrecognised reply, with attempts remaining: the retry text (if any) is resent and the step keeps waiting. This is not a final failure, and nothing downstream runs yet.
  • Every attempt used up on unrecognised replies: the answer settles as unmatched, and the steps on the Failure: Invalid branch run.
  • Before that, a bad reply only gets the If the reply matches nothing text; the branch runs once, as the final outcome.
  • Whatever comes after the question in the workflow follows after that branch.
  • When the Failure: Invalid branch (or the Needs a person branch) assigns an AI agent and has no AI Reply step of its own, the AI answers what the customer wrote right after the assignment. That holds when the branch then sends a "please pick an option" message and asks the question again. A branch that already has its own AI Reply step gets no second AI answer.
  • The deadline passes with no reply at all: the answer settles as unanswered, the Add Timeout Branch steps run (empty if the toggle was off), followed by whatever comes after the question.
  • An away-message-looking reply arrives: it is ignored — not consumed, not counted as an attempt, not treated as an answer. The question is untouched and still waiting.
  • The workflow was deleted, the workspace's plan no longer includes automation, or the merchant stopped the flow and ticked "Abandon them instead" in the stop dialog.
  • In those cases the questionnaire is dropped and a system note says so on the conversation — except on a conversation held by a person or with the AI paused (below).
  • The customer's reply is then handled as an ordinary inbound message, which the AI may now answer.
  • A conversation held by a person, or with the AI paused, does not drop it: the reply is not taken, and a note says the question is still waiting.
  • The flow resumes once the conversation is released.
  • A plain stop, or a stop-and-republish without ticking that box, does none of this — see Limits: the question keeps waiting and resumes against the version the customer was actually shown.
  • The reason and the outcome are visible in the workflow's Activity tab, under Execution log, on this step's line.

Limits

  • The timeout, when set, is clamped between 60 seconds and 7 days; turning the toggle on with no amount changed defaults to 7 days.
  • Leaving the toggle off does not mean an infinite wait — the question still expires after 1 day by default, just with no extra steps attached to that expiry.
  • The attempt limit is 1 to 10, defaulting to 3; only unrecognised replies count against it — an ignored away-message reply does not.
  • The drawer has no field to change the attempt limit by hand — a question you add yourself uses the default of 3. A prebuilt template or Build with AI can set a different number.
  • Multiple Choice offers at most 20 answers; each can carry up to 10 aliases and one AI hint of up to 120 characters.
  • AI matching reads one reply at a time, with no memory of earlier replies, and waits at most 2 seconds for the model. It does not hold a conversation: asking several questions in a row is still done with several Ask a Question steps.
  • It pauses only this run, and it claims the customer's next reply for itself: the AI does not answer it, and no fresh Message received flow starts from it.
  • Any other live workflow with its own "exit on inbound" rule still exits on that reply, exactly as it would on any inbound — the asking workflow alone is exempt from its own rule. A live workflow with no such rule is unaffected. A human agent can still act on the conversation at any time; automation is what stands down.
  • A send failure with no Add Message Failure Branch authored simply drops the contact out of the workflow. There is no default fallback branch to fall through to, unlike a mid-flow send whose failure the run just continues past.
  • A question's continuation is bound to the exact workflow version the customer was shown, not to whatever the workflow looks like now. Editing and republishing the workflow while a question waits means the eventual answer resumes against the old version, not the edit.

Best practices

  • Always give a question either a timeout branch or a reason it cannot go unanswered forever. A silent customer otherwise leaves the run paused for a full day by default before anything else happens on this conversation.
  • Keep Multiple Choice under about 3 options if the channel matters — WhatsApp only renders up to 3 as tappable buttons before falling back to a pick-list.
  • Add aliases for the ways people actually type an answer (numbers, single letters, the local-language word) rather than relying on the button label alone — typed replies are common even when buttons are shown.
  • Turn on AI matching only where customers really do answer a menu in their own words. Keep each hint short and concrete, such as the towns an answer covers, and always give the Needs a person branch a step that reaches a teammate.
  • Use free-text capture (no options) only for answers that cannot be listed, such as a phone number or a company name. It accepts the first reply that is not a question back, with no validation beyond the question's own type.

Use cases

  • Ask which product tier interests the customer, with 3 buttons and aliases for common typed answers, tagging the contact with whichever they pick.
  • Ask for an email address (kind: Email) to save into a contact field before continuing to a quote step.
  • Ask a satisfaction rating at the end of a flow, with no timeout branch needed since the flow simply ends if nobody answers.

FAQ and troubleshooting

Does the AI keep answering this conversation while the question is open?
No. Only this workflow run is technically paused, but the customer's next reply is claimed as the answer to this question. The AI does not answer it, and no fresh Message received flow starts from it. The exception is a free-text question where the customer asks something back: that goes to the AI as an ordinary message. A different live workflow with its own "exit on inbound" rule still exits on that reply, same as it would on any message; a live workflow with no such rule keeps running regardless. A human agent can still act on the conversation at any time.
I left Add Timeout Branch off. Does the question wait forever?
No. It still expires — 1 day by default, or sooner if the messaging window would otherwise close first — it just runs no extra steps when it does, since no timeout branch was authored. Use the toggle if you want something to happen on timeout.
What happens if the customer keeps giving answers that don't match any option?
Each unrecognised reply, while attempts remain, resends your retry text and waits again. Once the attempt limit is used up, the answer settles as unmatched and the Failure: Invalid branch runs as the final outcome, followed by whatever comes after the question.
Does AI matching send anything to the customer?
No. It only decides which of your answers a reply means. The messages the customer receives still come from the steps on the paths you built, and the question is asked again when AI is unsure.
Does an exact match or a button tap call AI?
No. AI reads a reply only after the fixed matching rules found nothing. A tap, a typed answer, an alias or a position number never uses an AI message.
Can I branch on whether the customer answered at all?
Yes — a Condition step after this one can read Answer result (answer.status: matched / unmatched / unanswered / captured) as well as Answer picked (answer.key) and Answer as typed (answer.text).

Reading this with an AI assistant? Plain Markdown version.