Launch it yourself

This is what Chapiee introduces itself as, and where it lives. Your timezone drives business hours and after-hours behaviour, so it is worth getting right before anything else.

• Name your workspace and add your website

  The site you add here is the property the widget installs on. One workspace can run several websites — each gets its own knowledge base, widget and leads.

  Dashboard → Sites

• Set your timezone and business hours

  Business hours decide when the agent answers normally and when it switches to after-hours lead capture. Set the timezone first — everything else follows it.

  Dashboard → Conversation Settings

Chapiee only says what it can back up, so what you feed it here is the ceiling on what it can answer. Most of your setup time belongs in this step.

• Add your knowledge sources

  Upload documents — PDF, DOCX, TXT, MD, CSV or HTML — or write question-and-answer pairs directly. Prices and claims are only ever quoted from what you add here.

  Dashboard → Knowledge Base

• Add the questions your team answers every day

  The fastest coverage win. Pair each common question with the answer you would give, and the agent uses your wording rather than paraphrasing a document.

• Crawl your website Not built yet

  Point Chapiee at your site so it ingests your public pages and re-crawls on a schedule, keeping answers in step with your content. For now, upload the pages that matter most as documents.

How it sells, what it sounds like, and where it refuses to go. All settings, no code — and the guardrails are not optional.

• Set the persona and tone

  Name the agent, write its persona, and set formality, verbosity, enthusiasm and proactiveness. Preview how it reads before anyone else sees it.

  Dashboard → Train Chapiee → Brand voice

• Set your guardrails

  Forbidden phrases and redirect topics. Answering only from your knowledge, and handing over when a visitor asks for a human, are always on.

• Override the tricky answers

  Pin exact question-and-answer pairs for anything policy-critical or brand-specific. A pinned answer wins over whatever retrieval would have said.

  Dashboard → Train Chapiee → Training examples

• Greet visitors in their own language Not built yet

  Detect the visitor language and answer in it, while your team keeps reading leads in one language.

One tag to ship — this is the whole install. It loads asynchronously and never blocks your page.

<script
  src="https://widget.chapiee.ai/chappy-widget.js"
  data-site-id="YOUR_SITE_ID"
  async></script>

Your Site ID is shown beside the snippet in the dashboard, under Widget Designer → Install snippet. It is not a secret — it identifies which site is asking, nothing more.

Where to paste it

On WordPress, use the plugin

1. In Widget Designer → WordPress, click Download plugin and copy your Site ID.
2. In wp-admin, go to Plugins → Add New → Upload Plugin, choose the zip, install and activate.
3. Under Settings → Chapiee, paste your Site ID and save.

Once a page carrying the tag loads on an allow-listed origin, the site shows as installed on the Sites screen. Nothing needs to be clicked to confirm it — the first real page load is the confirmation.

This is where captured leads go. Connect it once and every conversation files itself — without it, leads live only in Chapiee.

• Connect your CRM

  Odoo or HubSpot. Captured leads are pushed automatically, and later enrichment updates that same record rather than creating a second one.

  Dashboard → Integrations

• Map your CRM fields

  Match each Chapiee field onto a field in your own CRM, including custom ones. Anything unmapped is appended to the record notes rather than dropped.

• Connect your calendar

  Google Calendar. The agent offers real free slots from your availability and books the one the visitor picks.

• Send follow-ups from your own domain Not built yet

  Verify a sending domain with DNS records so follow-ups arrive from your address rather than a shared one.

What happens after the conversation. Two or three rules cover most businesses on day one — the rest can wait until you have seen real traffic.

• Decide what makes a lead hot

  Score leads on the facts the agent captured, so "hot" means what it means in your business rather than a generic guess.

  Dashboard → Lead Scoring

• Route by score, then follow up automatically

  Build the after-the-chat automation: push to the CRM, move a pipeline stage, notify the team, wait, then invite them to a meeting.

  Dashboard → Flow Builder

• Add in-chat rules

  React while the visitor is still there — escalate to a human, send a canned reply, steer a single answer, or tag the lead.

  Dashboard → Playbooks

• Say who takes handovers

  When someone asks for a human, your team picks the conversation up with the full transcript already in front of them.

  Dashboard → Team & Permissions

• Confirm bookings by phone Not built yet

  A voice agent that rings to confirm a booking, and answers the phone when someone would rather talk than type.

Run the checks an engineer would run before handing this to real customers. All four are things you do yourself, on your real setup — which is the only kind of check worth trusting.

• The answers are grounded

  Ask a real customer question in Train Chapiee → Test playground and confirm the answer cites your own content rather than improvising. The sources it used are listed under the answer.

• A lead reaches your CRM

  Hold a short conversation through the widget on your own site, leaving a name and email. Confirm it appears in Lead Pipeline — and then in your CRM.

• Booking offers real slots

  Ask for a meeting and confirm the times offered match your actual calendar availability — block out an hour and check it disappears from the offer.

• Human handover works

  Ask for a human in the widget, take the conversation over from Conversations, and confirm the agent goes quiet immediately — you should never see two replies to one message.

Once the tag is on your site and the checks pass, you are live — visitors are already being answered. There is no separate switch to flip, and nothing here is irreversible: remove the tag and the widget disappears.

The first 48 hours

• Read the conversations in full

  Not just the leads. The wording visitors actually use is the best guide to what to add next, and it is rarely what you would have guessed.

• Fix what day one exposes

  Answers the agent got wrong or hedged on are flagged in Train Chapiee → Review queue. Correct one and it can be pinned as a training example straight away, so it is right next time.

• Watch the numbers

  Conversation volume, resolution rate, satisfaction and lead counts — enough to tell whether it is working in week one.

  Dashboard → Analytics

The bar we hold ourselves to

These are design targets, not current measurements — Chapiee Technical Systems Requirements Study v0.1.