Automating common questions in Messenger

The questions worth automating in Messenger are the ones whose answer never changes: delivery, payment, hours, returns. They make up the bulk of incoming messages and they’re the cheapest to automate — because they don’t depend on stock, season or the individual customer.

Leave product questions for later. The answer to «do you have a 38?» depends on your warehouse, and an automated answer here risks becoming a promise you never made.

How do you find your real question list?

Not by guessing. Open the last month of messages and write down the first sentence of every conversation.

After twenty conversations the list stops growing — and it almost always differs from what you assumed. Shops routinely automate «do you have discounts» while people are actually asking «when will you restock».

What should an automated reply look like?

Like an answer, not like the promise of one. That’s the dividing line between useful automation and the kind that irritates.

1. 1

   Bad

   «Thanks for getting in touch! A manager will be with you shortly.» The question is still unanswered.

2. 2

   Acceptable

   «Delivery is 1–3 days, free over £50.» The fact is there, the continuation isn't.

3. 3

   Good

   «Delivery is 1–3 days, free over £50. Where are we shipping to?» Fact plus a step.

The last version does one more useful thing: a question at the end raises the chance the customer replies — and their reply opens a fresh window of free communication in Messenger.

What signals should trigger a handover?

Three, and all should fire without deliberation:

A direct request. «Can I speak to someone?» is honoured immediately, with no clarifying questions and no further attempts to help.

A second failed attempt. If the customer has asked the same thing twice, automation won’t fix it — it only worsens the impression.

Any problem. A complaint, a defect, a late delivery. Here the cost of a bad automated reply isn’t a lost order but a public review.

Do you need a dedicated platform?

Mostly no. A persistent menu handles navigation, saved quick replies handle standard text, and a few keyword rules handle the rest — all available without a separate service or integrations.

A dedicated platform earns its place once you need multi-step flows, behavioural segmentation or dozens of simultaneous conversations. Before that it adds more complexity than it saves time.

A starter set of automated replies

1. Delivery — times, cost, free threshold + «where are we shipping to?»
2. Payment — available methods + «which suits you?»
3. Hours — when you reply, when you dispatch + what happens out of hours
4. Returns — window and condition, in one sentence
5. Availability — not a fact but a route: «tell me the model and size, I’ll check in a minute»
6. Not understood — «let me get a manager» + an actual handover

Six rules that cover most incoming messages and never promise something you don’t know.