Design a useful first conversation

Begin with the page and the visitor’s intent.

A visitor exploring a service page may want to understand suitability. Someone on a pricing page may have a specific question about scope. Shape the opening around that context while leaving room for the person to ask something else.

• Service enquiry: “What are you hoping to improve?”
• Product question: “What would you like the product to help your team do?”
• Human assistance: “What would you like to speak with the team about?”

Offer a useful answer before requesting details.

When someone asks a straightforward question, answer it from approved information where possible. A request for a name, phone number and company can interrupt a conversation before it has provided value. Explain why a contact detail is needed when the visitor chooses a follow-up that requires it.

Ask one question that changes what happens next.

A strong follow-up reduces uncertainty. For a customer portal, understanding what customers need to do is more useful than collecting an industry label immediately. Ask the question, use the answer and avoid requesting information the person has already supplied.

• Keep questions short and explain unfamiliar terms.
• Offer “not decided yet” when that is a reasonable answer.
• Let a visitor use their own words instead of forcing an unsuitable option.

Make the next step understandable.

Tell the visitor what their answer has helped establish and what can happen next. That may be a relevant page, a short brief or a conversation with a person. If a request cannot be completed, explain the available route without implying that a booking or message has already been created.

Review the exchange as a visitor would.

Read the complete conversation, including its ending. Check whether the original question received an answer, whether each follow-up had a purpose and whether the final action was clear. Review missing information with the receiving team before adding more questions to the flow.