Skip to content

Help website visitors find their next step with AI chat.

A visitor may have a question before they are ready to call or book. Ember configures website chat around the answers you approve, the details you need and the point where your team takes over.

Gather EventsWebsite assistant

Can you help with a small outdoor event?

I can collect the details for the team to review. What kind of event are you planning?

A birthday gathering.

A useful answer. Details for the team.
Fictional conversation · Read-only previewExplore the conversation

A WRITTEN QUESTION, A USEFUL NEXT STEP

A useful answer at the point of interest.

Help visitors understand your services and how to proceed without searching through every page. The conversation should use approved information, ask relevant questions and offer a next step your business can support.

These fixed examples show three different moments in a conversation. They do not send an inquiry or run a live AI tool.

Example website conversation · Fictional scenario · No inquiry is sent.

A service question

Gather EventsWebsite assistant · Fictional business
Demo
You

Can you help with a small outdoor event?

10:41
Gather Events · Assistant

I can collect the details for the team to review. What kind of event are you planning?

10:42
You

A birthday gathering.

10:43
Gather Events · Assistant

What date and approximate guest count should the team consider?

10:44
Example conversation · chat is read-only

Details being collected; availability and quote not confirmed.

The details needed for review

Gather EventsWebsite assistant · Fictional business
Demo
You

We are planning a birthday gathering outdoors.

10:41
Gather Events · Assistant

Which date and approximate guest count should the team consider?

10:42
You

I haven’t settled on those details yet.

10:43
Gather Events · Assistant

The team can review your plans once those details are clear.

10:44
Example conversation · chat is read-only

Details still needed; no availability, price or reservation is confirmed.

A question for a person

Gather EventsWebsite assistant · Fictional business
Demo
You

The venue has unusual access rules. Can you work with them?

10:41
Gather Events · Assistant

The team needs to confirm the venue requirements before I can give an accurate answer.

10:42
Example conversation · chat is read-only

Team review needed; the venue requirement is not confirmed. For the team to review: an outdoor birthday gathering with unusual venue access rules. The team needs to check those requirements before confirming what can be provided. An illustrative reply: “Please share the venue’s access requirements. We’ll review them before confirming what we can provide.” This fictional continuation does not store or send a request.

Service question example shown.

Good conversations start with clear information.

We organize the business details the assistant may use and define what it should do when information is missing. Pricing, policies and service restrictions need a clear owner so an old answer does not become a new promise.

Approved information

  • Your current services and business details, including what visitors need to know before asking for a quote or making a request
  • Answers and policies your business has checked, with a person responsible for approving changes when the information becomes outdated
  • The next steps included in the selected setup, with clear wording about what the visitor has requested and what still needs review

Questions for a person

  • An answer outside the approved information, such as a detail that must be checked against a current record
  • An exception requiring a business decision, rather than a routine answer the assistant is authorized to give
  • A request needing the team to confirm the details, with enough context for that person to continue the conversation

Move from chat to an owned next step.

We agree which details to capture, where an inquiry goes and who responds. Appointment actions or other channels are included only when selected and verified for that implementation.

  1. Visitor question

    Identify the service or question behind the visit. Use relevant follow-up questions to understand what the visitor needs before directing them to a next step.

  2. Information or request

    Explain the approved information in plain language. Where an inquiry is needed, collect the details your team has agreed are useful, rather than implying an unverified answer.

  3. Responsible team

    Use a supported action selected for the setup or pass the request to its owner. Agree where that person sees the conversation and how unresolved questions are handled.

No saved customer record or confirmed booking is implied by the illustrative conversation.

Built around the way your team responds.

Before launch, review the approved answers, inquiry details, escalation path and representative conversations. Include routine service questions, incomplete requests and questions that need a person. Your team supplies the approved information and checks whether the answers match it. The handoff defines how staff review unresolved conversations and how information changes are approved.

  • The website questions visitors commonly ask
  • Approved answers and an owner for updates
  • The details needed for each selected next step
  • The person and process for a handoff
  • Ordinary conversations and exceptions to review
See a conversation review checklistClick hereClose preview
  • Does the answer use current approved information?
  • Is uncertainty stated clearly?
  • Are inquiry details relevant to the next step?
  • Does a person own the question that needs judgment?
  • Is it clear how staff take over, use any supported pause controls and handle an unanswered handoff?

A few things to know.

Explore all FAQs
Is this the same as the AI receptionist?

Website chat handles written visitor conversations. The AI receptionist handles voice calls. Their channels and actions are configured separately.

Can it answer every question?

AI website chat should answer within approved knowledge and scope. When a visitor asks about an exception, an unverified price or information the business has not supplied, it needs to explain what requires review and follow the agreed handoff path to a person.

Who keeps the answers current?

The proposal and handoff name the person responsible for business information and any ongoing review. Changes to services, hours or policies need to reach that owner so the approved answers can be updated and checked; ongoing content management is separately agreed.

See a conversation built around your business.

Show us the questions visitors ask before contacting you. We will explore a useful path from question to next step.