For web implementers

Your client's FAQs. Their next useful feature.

Build a website assistant around information your client approves.

See the example
Sculpture of website, document and FAQ panels linked by brass pipes to a glowing approved-answer block on a plum marble base

Illustrative workflow — not a live agent

A question worth answering.

Visitor question

Can it answer from our existing FAQs?

Approved-content workflow

Start with approved content. Review the answers. Add a website widget when you're ready.

An approved-input and client-handoff example

Illustrative setup checklist, not a client record or reseller promise.

  1. 01

    Inputs to approve

    Collect the client’s published service FAQ, preparation page and preferred contact page. Identify a named approver and exclude draft prices or internal notes.

  2. 02

    Review with the client

    Test a common service question and an exception not covered by the source. Record the approved answer and the existing contact destination for the exception.

  3. 03

    Hand off ownership

    Give the client the source list, update owner and review questions. Confirm approval before embedding; keep booking and additional channels separately scoped.

Start with three questions your client already hears.

  1. 01

    Choose your client's three common questions

    Collect the FAQs and website pages your client approves. Agree on which questions the assistant should answer and which should go to their team.

  2. 02

    Configure and review answers

    Configure the assistant around those sources. Test the three questions, review the answers with your client and adjust the guidance before sharing it.

  3. 03

    Embed when ready

    Add the website widget after review. Keep a path to the client's existing contact pages for questions outside the approved content.

This workflow does not promise white-label or reseller features, or instant deployment. Setup and review come before embedding.

Your questions, before you start.

What should my client approve first?

Start with their three common questions and the source pages or FAQs that answer them. Have the client review the configured answers before adding the widget.

Can I promise an instant launch or reseller setup?

No. Treat this as a configured website assistant that needs source approval and answer review. White-label and reseller features are not promised here.

Does the website workflow include phone, SMS or live booking?

Phone/SMS and live booking are separate setup paths. Review the current packages and discuss any additional requirements before making commitments to your client.

Start with the free package

Review the current packages for included features, usage and limits. Choose your approved sources and review the answers before sharing your website assistant.

Setup and answer quality depend on your sources and configuration. Phone/SMS and live booking are separate setup paths.

Create free account See current packages