kavilo
Sign in

Guide

Getting started

Ten minutes, most of it spent writing the description. Nothing to install and nothing to host.

1. Sign in

Go to the portal and continue with Google or GitHub. The first successful sign-in creates your account.

Sign-in is OAuth-only. There is no password or email-link sign-in, and no invite is needed.

2. Add a bot

Give it a name you will recognise and the domains it may run on — for example https://example.com. The name is for you; the domains are a control. A key used from a domain you did not list is refused, so another website cannot use your key through a visitor's browser.

Include every hostname you actually serve from. example.com and www.example.com are different origins, and a staging domain is a third.

3. Describe the business

Four fields, all plain prose:

  • Greeting — the first line visitors see.
  • Persona — who the agent is and how it speaks.
  • Context — what is true. Services, hours, prices, areas covered, policies.
  • Guardrails — what it must never say, do or promise.

If a public page already says what the bot should know, use import to copy it into Context rather than retyping it. It can be a pricing, FAQ or services page; it does not have to be your homepage.

Start rougher than feels comfortable. You will learn more from ten real conversations than from an hour of drafting, and the transcripts tell you exactly which sentence was missing. There is a longer guide on getting this part right.

4. Paste one line into your page

The portal shows a snippet with your key already in it. It goes anywhere in the HTML — just before </body> is conventional:

<script src="https://kavilo.cloud/widget.js" data-key="kw_pub_…"></script>

Load the page and a chat button appears in the corner. Where to paste it on the common site builders.

5. Have a conversation with it

Then try to break it. Ask something you did not cover, and check it says so rather than inventing. Ask it to be someone else, and check it declines. Ask the question your most annoying customer asks.

Fix what you find in the four fields, save the draft, preview it, then Publish. Published changes take effect on the next message, with nothing to redeploy.

What to do in the first week

Read the transcripts. Every question the agent handled badly is either a sentence missing from Context or a Guardrail you had not thought to write down. That loop is most of the work, and it converges quickly.