← Back to Kawl NowFROM FIRST HELLO TO FIRST CUSTOMER

Set up your voice agent.

Sign in with the link sent to your email, then follow your dashboard’s launch checklist. You need product information and permission to add a small snippet to your website. Kawl Now manages the voice service; you do not need your own AI account or API key.

Choose your brand

Use the brand selector in the dashboard to switch brands or choose Add brand. Each brand has its own support and sales agents, knowledge, website origins, widget snippets, team phones and access tokens. Follow the setup steps below for each brand. All brands share your account’s free allowance and billing.

1. Add and approve your knowledge

Open Knowledge, choose Add knowledge, and paste a FAQ or getting-started guide. Include what your product does, common questions, and your team’s usual contact options. Add only information you want customers to hear. You can also scan your public HTTPS website or upload a PDF with selectable text. A website scan discovers up to 250 public HTML pages, then lets you import all pages or choose a selection. It does not run JavaScript or read sign-in pages. Scanned pages and PDF text are saved as drafts for Support only, Sales only, or Both agents in this brand. Upload up to 25 PDFs at once, at most 2 MB, 100 pages and 50,000 characters per PDF. Scanned images need OCR before upload; Kawl Now imports selectable text only.

Open the saved document, check the facts, and choose Approve for your agent. Only approved sources are available during calls. You can also scan a public GitHub repository and select text or source-code files to import. Private repository access must be arranged by Kawl Now, and every GitHub sync requires your approval again.

To share common facts, choose Both. You can change a saved source’s audience without copying its text. This keeps its approval, so an approved source becomes available to the selected agents immediately. Review the full text before widening its audience. Saving the change requires the current revision; approval is a separate action.

2. Make the agent yours

In Support agent, enter your product name, choose a voice, and write a short greeting. Add instructions about how to help and where to send questions your agent cannot answer. Save your changes before testing; calls use saved settings.

3. Add your website and test a conversation

In Installation, add your website’s HTTPS origin and save. For example, use https://www.example.com, without a page path. The www version and the version without it are separate origins, so add both if visitors use both.

Choose Test your agent on the Overview page. Allow microphone access, ask a question your knowledge covers, then ask something it does not cover. Check that the answers are accurate and that the agent can say when it does not know. Finish the call and close the test window to update your checklist. You can test while customer calls are off.

4. Install the widget and enable calls

Copy your Installation snippet into your website, just before the closing </body> tag. In a website builder, use its custom code or footer code setting. Publish your website, then switch on Accept customer calls in Kawl Now and save the widget settings.

Visit the published website and make a final call through the widget. Check the microphone, audio, answers, and captions on the devices your customers use. The dashboard test checks your agent; the website call also checks your installation. Switch off Accept customer calls and save whenever you need to pause.

5. Keep answers up to date

Review calls in Conversations to find unanswered questions. Add and approve new documents when your product changes. The optional Sales agent has its own knowledge, settings, allowed origins, and widget snippet. Use manual notes for pricing and product information, or scan the public pages you want that agent to use. Review and approve every imported source. Refreshing a source clears its approval until you review the new revision.

For coding-agent setup, open Installation and run the npm command. Finish the website integration first, then give your trusted coding agent a short-lived setup key for the selected brand and agent. Browser OAuth is an optional alternative. Broader management tokens remain in Developers for trusted tools. Imported content still needs your review and approval before calls use it.

Install with one coding-agent prompt

Open Installation, choose support or sales, and copy the short prompt into Claude Code, Codex, Cursor or another coding agent. Your agent chooses npm for JavaScript, React and Next.js, or the native PyPI installer for Python, Flask and Django. No workspace ID, key or browser sign-in is needed to prepare the local integration. The canonical agent setup guide covers the package and account setup. The command prepares local files and an installation plan. Your agent finishes the dependency and shared layout or template, runs your project checks and the local doctor, then asks for a setup API key. Review the changes before publishing. The classic external-script option remains available.

The public packages are kawlnow on npm and kawlnow on PyPI. Both prepare local files without account access. Python installations need no Node.js. After wiring the site and passing the local doctor, your agent asks for a setup key. An owner creates it here for the selected brand and agent; it expires after 24 hours. Use the installer’s hidden input or your agent’s secret-input facility. Keep the key out of website code, command arguments and logs. It permits installation checks and website origins, with no knowledge access or call enablement. An optional React or JavaScript SDK is documented in the agent setup guide.

The coding agent should verify your actual production HTTPS origins, preserve existing settings and leave customer-call enablement under your control. A setup key can merge verified origins and check the installation. It cannot change agent wording, read or write knowledge, approve sources, start or enable calls, change billing or human destinations, or read transcripts. Viewers can prepare website code; the account owner creates the connection key. Never echo the key or put it in generated prompts, command arguments, website source or logs.

Once connected, the widget uses public brand identifiers. Setup-key expiry or revocation does not undo the installation or end existing calls. Your Kawl Now account still provides the configured voice service.

Agents discover the canonical guide through llms.txt and the machine-readable install workflow. Browser OAuth at /api/mcp remains an optional alternative. Use get_setup_status, configure_setup and verify_installation for the guided workflow. The static published-page check does not run JavaScript or prove voice audio; pages that inject the widget after hydration may need a browser check. Access lasts ten minutes, or can refresh for up to 24 hours when the client requests refresh access. You can revoke the connection in your dashboard. The OpenAPI specification documents broader REST management. Imported or generated knowledge still needs human review and revision-specific approval. Coding agents must not start voice calls automatically. Complete and verify a private dashboard test before enabling calls.

Free conversations and current limits

An account’s first 50 conversations are free. All brands, support calls, sales calls and test calls share those 50. Adding a brand does not add free calls. Free browser calls can last up to 10 minutes. No credit card is needed to start.

To continue after your free allowance, add a payment method in Usage & billing. A customer call costs £2.50 when the voice service confirms at least 15 seconds; shorter calls are free. Paid calls can last up to 30 minutes with no per-minute charges. Qualifying calls are billed monthly in GBP plus applicable tax. Your tests are excluded from paid billing.

For human handover, open Settings, verify a UK or US team phone number, then turn on handover for support or sales. Your team hears a private briefing before connecting. Human calls last up to 10 minutes. The agent can answer questions and record feedback; it cannot change a customer’s account. Insights groups questions and issues from up to your latest 30 completed customer calls in the last 30 days.

If something does not work