Support Chats to Better FAQs

A support conversation can show where your website leaves people guessing. Keep the question, find the missing detail, then check the answer with the person responsible for it.

Worked examples

All excerpts, businesses and policies below are fictional. They show the editing method; they are not policies to copy into your own website.

When does the delivery clock start?

From the conversation

Customer: The page says two days. Does that include Saturday?

Support: That estimate starts after dispatch, and it means business days.

Customer: I thought it started when I placed the order.

The customer needs to distinguish processing time from delivery time. A shorter answer about shipping speed would leave the same ambiguity.

FAQ edit

Earlier wording
How long does delivery take? Usually two days.

When should I expect my order?

In this example shop, processing takes one business day. Standard delivery takes two business days after dispatch; Saturdays, Sundays and public holidays are excluded. Check the destination-specific estimate at checkout before ordering.

Before publishing: Confirm the processing time, dispatch cutoff and destination exceptions with the fulfilment owner. Put the timing explanation beside the estimate as well as in the FAQ.

Why is the widget missing from the public page?

From the conversation

Customer: I can see the widget in the editor, but it is missing on my website.

Support: Did you publish the page after adding it?

Customer: I saved it. I didn't realise publishing was another step.

The setup instructions stop at saving. The missing step is publication, not a broader introduction to what the widget does.

FAQ edit

Earlier wording
Why can't I see my widget? Check that you installed it correctly.

I can see the widget in the editor. Why isn't it on the live page?

For the editor used in this example, saving a change does not publish it. Save, publish the page, then open its public URL to check the result. If the widget is still missing, confirm that its embed code is on that page before contacting support.

Before publishing: Test these steps in the supported editor. Keep platform-specific instructions separate, and ask for the page URL through the actual support route if the problem continues.

Does cancelling also request a refund?

From the conversation

Customer: I cancelled my subscription. When will the refund arrive?

Support: Cancellation stops the next renewal. Refund requests are reviewed separately.

Customer: The cancellation page didn't explain that.

The customer treats cancellation and a refund request as the same action. The answer needs to explain the consequence of each action.

FAQ edit

Earlier wording
How do I cancel? Use the cancellation option in your account.

What happens when I cancel my subscription?

Under this fictional policy, cancellation stops the next renewal and access continues until the end of the paid period. It does not submit a refund request. Use the billing contact route to request a refund review under the applicable policy.

Before publishing: Get the wording approved by the billing owner. Explain this beside the cancellation control too; a separate FAQ alone may not reach someone making the decision.

Reviewing the conversations

Group the underlying need

Use conversations your team is permitted to review. Remove personal details from saved excerpts. Group questions by what someone needed to understand or do, rather than by the exact words they used.

Count conversations consistently

Count a repeated issue once per conversation. A conversation can reveal more than one gap. Keep the date range and sample size with your notes; the chats you reviewed do not represent every customer.

Check the answer and its location

The support reply is a clue, not an approved policy. Confirm facts with the responsible person. Update the FAQ and the page where the confusion starts. After publication, review later chats for the same misunderstanding and record what you observe.

Notes template

Copy these fields into a document or spreadsheet. Keep each proposed edit with its source and the person who checked it.

Review period and sample size:
Conversation reference (no personal details):
Underlying question or task:
Relevant excerpt, with personal details removed:
Existing page or FAQ:
Missing information or unclear wording:
Proposed question and answer:
Fact or policy source:
Owner who checked the answer and date:
Where the change should appear:
Publication date:
What later conversations showed:

Tools and further reading

These resources cover website chatbots, customer reviews and a separate topic: how a business appears in search answers. The editing method above can be used with different support tools.

On your website

In search answers

Research and papers