Launch your website chatbot

From an empty workspace to a live chatbot on your website:

1. Create your workspace. Sign up at /register. Your organization is an isolated tenant — nothing in it is ever visible to another organization.
2. Tell Intellia about your business. Fill in the Business Profile: what you do, where you are, hours and contact details.
3. Add knowledge. Under Knowledge, crawl your website or upload documents — price lists, FAQs, policies, brochures.
4. Create your chatbot. Under Chatbots, pick a name, personality, welcome message and brand colour, then test it on the same page.
5. Choose what to learn. Under Attributes, pick an industry template or define the details that qualify an enquiry — budget, location, dates.
6. Go live and install. Click Go live, copy the script tag, and paste it into your site.

The profile is the short, always-relevant context every chatbot has in every conversation: what the business does, its location, phone, email, website, opening hours and services. It's included directly rather than searched, so a chatbot never fails to find your phone number.

Knowledge sources keep answers grounded. Each source is ingested, split into passages, embedded and stored against your organization. For each visitor question, the most relevant passages are retrieved and given to the model — answers come from your material, and the chatbot is instructed to say it doesn't know rather than invent prices or policies.

Re-sync a source from the Knowledge page when the content changes. Text inside your documents is treated as reference material only, never as instructions to the chatbot.

A chatbot has:

• Identity — a name and a personality (friendly, professional, concise, formal or casual), plus optional extra instructions.
• Welcome message and appearance — brand colour and which corner the chat bubble sits in.
• Capabilities — Capture leads lets it ask interested visitors for a name and phone or email; Human handover lets it offer to pass a visitor to your team.
• Knowledge — which sources it answers from.

The tester on each chatbot's page shows both the reply and what Intellia understood from the conversation. Test conversations appear in your inbox marked “Test” and are left out of dashboard and Insights numbers.

Paste one line before the closing </body> tag:

<script
  src="https://intellia.naidvartechnologies.com/widget.js"
  data-bot="YOUR_CHATBOT_PUBLIC_KEY"
  async>
</script>

It adds a chat bubble in your brand colour that opens the conversation — full screen on phones. The conversation survives page changes within the visitor's tab. The key identifies the chatbot publicly and grants nothing else: it can only start conversations with that one chatbot, and requests are rate limited per IP.

Attributes are the details your business needs from an enquiry — a budget, a location, a move-in date, which appliances a solar system must power. Each has a type (text, number, currency, date, choice, multiple choice, yes/no, location, email, phone…) so values are stored cleanly and can be analysed.

After each reply Intellia reads the conversation and extracts them. Attributes marked required are also what the chatbot asks about — one natural question at a time, never a form — and a lead is qualified once they're all known and the visitor has left contact details.

Conversations is your inbox: every transcript beside its intelligence — intent, summary, lead score, sentiment, extracted attributes and contact details. Filter to conversations that need a person and mark them handled when done.

A lead is created when a visitor shares a phone number or email, in chat or through the widget's “Talk to a person” form. Leads move through new → contacted → qualified → converted (or lost / archived). Intellia only ever moves a lead from new to qualified on its own; every other status is yours, and it never overwrites contact details a visitor typed into the form.

Insights aggregates your conversations over 7, 30 or 90 days: top intents, topics, sentiment, and — per attribute — popular values or the spread of numbers (common budgets, popular locations).

Knowledge gaps are questions your chatbot couldn't answer, with similar questions merged and counted per customer. Add the answer to your knowledge or profile, then mark the gap resolved. If customers keep asking and the chatbot still can't answer, it reopens.

Members are invited by email and hold one of three roles:

• Owner — full control, including deleting the organization. An organization always keeps at least one Owner.
• Admin — manages chatbots, knowledge, attributes, leads and members.
• Member — can view conversations, leads and insights.

Everything the dashboard does runs through the same REST API, so anything you can do in the UI you can automate — for example, pulling new leads into your CRM.

Base URL: https://intellia.naidvartechnologies.com/api

curl -X POST https://intellia.naidvartechnologies.com/api/login \
  -H 'Content-Type: application/json' \
  -d '{"email":"[email protected]","password":"..."}'

# → { "token": "1|abc...", "user": { ... } }

curl 'https://intellia.naidvartechnologies.com/api/leads?status=qualified' \
  -H 'Authorization: Bearer 1|abc...'

Commonly used endpoints:

The public widget endpoints (/widget/bots/{publicKey}) need no token and are rate limited per IP. Webhooks for events such as lead.created are on the roadmap.