Exania AI documentation

Build, launch and manage business AI agents.

A practical documentation hub for Exania bots: website chatbots, WhatsApp agents, lead qualification, booking assistants, knowledge bots and automation systems. Use it to understand what each bot does, what information we need, how setup works and how to maintain results after launch.

Website and WhatsApp agents English and Spanish ready Human handoff and safety notes
Quickstart

How an Exania AI bot project starts.

Most businesses do not need a huge AI transformation project. They need a clear use case, a clean knowledge base, the right channel and a bot that knows when to hand off to a human.

1. Choose the goal

Start with one main outcome: answer FAQs, qualify leads, book appointments, support customers or automate internal tasks.

Define outcome

2. Pick the package

Micro Bot for simple web FAQs, Launch Bot for a polished chatbot, Growth Agent for sales and booking, Automate System for integrations.

Select plan

3. Share knowledge

Send your website, services, prices, FAQs, policies, opening hours, examples and the tone you want the bot to use.

Train safely

4. Launch and improve

We configure, test, install and monitor the agent. After launch, optimization keeps the bot useful and aligned with your business.

Go live
Bot types

Choose the agent that matches the job.

Every bot has a different role. The best projects are specific: one agent, one workflow, one measurable result.

Website AI Chatbot

A web chatbot answers common questions, explains your services, guides visitors and captures contact details. It is usually the fastest way to add AI to a website.

  • Best for FAQs, service pages, contact capture and basic qualification.
  • Can recommend services based on visitor answers.
  • Can send leads to email, Telegram, CRM or a secure intake system.
ChannelWebsite widget or custom page
Data neededWebsite, FAQs, services, prices and policies
Human handoffEmail, form, CRM or support route
Good packageMicro Bot or Launch Bot

WhatsApp AI Agent

A WhatsApp agent replies to customers where they already communicate. It can answer, collect information, qualify requests and route urgent conversations to a human.

  • Best for appointment based businesses, real estate, clinics, restaurants and local services.
  • Can collect name, email, phone, location, desired service and urgency.
  • Requires clear handoff rules so sensitive requests reach a person.
ChannelWhatsApp Business workflows
Data neededFAQ, opening hours, service rules and reply tone
Human handoffTeam route, notification or CRM task
Good packageGrowth Agent or Automate System

Lead Qualification Agent

A lead qualification agent asks the right questions before a human gets involved. It helps separate casual visitors from serious prospects.

  • Can score leads based on budget, timeline, industry, service fit and urgency.
  • Can prepare a lead summary for your team.
  • Can recommend the next step: call, quote, booking or nurture.
ChannelWebsite, WhatsApp or form
Data neededIdeal customer, disqualifiers and sales process
Human handoffHot lead alert and summary
Good packageGrowth Agent

Booking Assistant

A booking assistant helps people schedule calls, appointments, consultations or visits. It can answer pre-booking questions and reduce back and forth messages.

  • Best for clinics, agencies, restaurants, consultants and local services.
  • Can collect preferred date, time, service, location and contact details.
  • Can trigger confirmation messages or create a calendar flow when integrated.
ChannelWebsite or WhatsApp
Data neededAvailability rules, services, time zones and policies
Human handoffManual review or confirmed booking route
Good packageGrowth Agent

AI Automation System

An automation system connects your AI agent with operational tools. It can summarize requests, update sheets, route tasks, prepare reports and trigger follow ups.

  • Best for businesses with repeated manual workflows.
  • Can connect forms, email, CRM, spreadsheets, docs, calendars and internal tools.
  • Should start with a clear workflow map and safe fallback rules.
ChannelMultiple tools and workflows
Data neededProcess map, tool list, users and failure rules
Human handoffApprovals and exception handling
Good packageAutomate System or Enterprise AI
Project requirements

What we need before building your bot.

Good inputs make the bot useful. The more specific the business information, the better the answers, routing and recommendations.

Business profile

Company name, website, industry, location, languages, opening hours, service area and preferred tone.

Brand voiceBusiness rulesContact route

Services and offers

Services, packages, prices, what is included, what is not included, common objections and qualification rules.

Pricing detailsUpsell logicEligibility rules

Sales process

What counts as a good lead, what questions to ask, when to book a call and when to notify your team.

Lead scoreTimelineBudget range

FAQs and policies

Real customer questions, refund policies, cancellation rules, delivery times, support boundaries and safety disclaimers.

FAQ answersPolicy textEscalation rules

Tools and integrations

Website platform, CRM, forms, calendar, spreadsheet, email route, notifications and internal tools.

Website accessCRM fieldsNotification channel

Limits and handoff

Topics the bot should avoid, sensitive cases, legal or medical disclaimers, and when a human must take over.

Do not answer listHuman routeRisk cases
Installation

Typical website bot installation flow.

Installation depends on the package and website platform. This example shows the safe public idea: add the widget, configure the bot, then test before launch.

<!-- Exania AI Website Bot Example -->
<script>
  window.ExaniaBot = {
    businessId: "your-business-id",
    language: "auto",
    mode: "lead-capture",
    handoff: "human-review",
    theme: "exania-dark"
  };
</script>
<script async src="https://exania.ai/widget/exania-bot.js"></script>
Place code before closing bodyThe widget normally loads near the bottom of the page so it does not block the main content.
Test on desktop and mobileCheck opening, closing, keyboard behavior, lead capture and design spacing.
Verify routingSubmit a test lead and confirm it reaches the correct destination.
Review answersAsk common, difficult and sensitive questions before going live.
Launch with a fallbackThe bot should always offer a contact route when it is unsure.
Knowledge and data

How the bot should use your business information.

The bot should answer from approved business knowledge and avoid guessing when the information is missing. Important information should always be checked.

Data typeExamplesHow the bot uses itBest practice
ServicesPackages, pricing, descriptions, deliverablesExplains what you offer and recommends the right optionKeep updated
FAQsHours, locations, delivery times, refunds, processAnswers common questions without involving your teamUse real customer questions
Lead rulesBudget, urgency, industry, location, service fitScores leads and routes high intent requestsDefine hot lead criteria
PoliciesCancellation, support limits, privacy, termsProvides boundaries and prevents overpromisingReview carefully
Internal docsPDFs, SOPs, guides, onboarding notesSupports internal copilot or knowledge botLimit access by use case
Sensitive dataPasswords, payment details, private recordsShould not be used as training content unless a secure approved workflow existsAvoid by default
Human handoff

A good bot knows when to stop.

Exania agents are built to reduce repetitive work, not remove responsible human review. The handoff rules keep the experience useful and safe.

01

Bot detects intent

The agent identifies whether the user wants support, pricing, booking, purchase advice, technical help or human contact.

02

Bot collects structured details

Name, email, phone, business type, service needed, urgency and message summary are captured only when relevant.

03

Bot checks confidence and policy

If the request is sensitive, unclear or outside the approved knowledge, the bot should not invent an answer.

04

Bot routes to the team

The conversation summary can be sent to email, Telegram, CRM, dashboard or another approved business workflow.

05

Human takes over when needed

Complex, urgent, legal, medical, financial or account sensitive issues should be reviewed by a responsible person.

Packages

Documentation by package level.

Choose the plan based on the workflow you want, not only the channel. More integrations require more setup, testing and maintenance.

Micro Bot

Basic website chatbot for FAQs and simple contact capture. Best when you need a fast starting point.

$390 + $79/mo

Launch Bot

Professional website chatbot with stronger presentation, lead capture and email alerts.

$590 + $149/mo

Growth Agent

Recommended for lead qualification, booking flows, WhatsApp or more serious sales workflows.

$1,200 + $299/mo

Automate System

Advanced automation connecting forms, CRM, sheets, calendar, documents, reports and internal tools.

$2,500 + $599/mo
Security and limits

Practical safety rules for business bots.

AI can make mistakes. Important information should be checked, and sensitive workflows should use human review and approved data handling.

Approved knowledge only

The bot should answer from business approved sources and avoid unsupported claims when information is missing.

Least data by default

Collect only the details needed for the workflow. Avoid passwords, payment card details or unnecessary private information.

Clear limitations

For important, legal, medical, financial or account sensitive information, the bot should recommend human verification.

Human escalation

Every production bot should have a fallback route so the user can reach a human when needed.

Launch testing

Before launch, test common questions, edge cases, weird phrasing, wrong assumptions and lead routing.

Ongoing review

Update the knowledge base when services, prices, hours, policies or business processes change.

Maintenance

Keep the agent accurate after launch.

A bot is not finished forever on launch day. It should improve as the business changes and as users ask new questions.

Monthly review checklist

Review unanswered or low confidence questionsCheck lead quality and routingUpdate prices, services and hoursImprove prompts and fallback messagesTest mobile experience and response speed

When to request changes

You launch a new product or serviceYour pricing or policies changeThe bot receives repeated similar questionsYou add a new channel or integrationYour team wants different lead scoring rules
Documentation FAQ

Common questions about Exania bots.

Can Exania answer in English and Spanish?

Yes. Exania bots can be configured for English, Spanish or automatic language detection depending on the project.

Can the bot replace my support team?

No. The goal is to reduce repetitive work, answer faster and prepare better summaries. Complex or sensitive issues should still go to a human.

What happens when the bot does not know an answer?

The safe behavior is to say it is not sure, offer the best next step and route the user to a human or contact form.

Can the bot connect to WhatsApp?

Yes. WhatsApp workflows are usually part of Growth Agent, Automate System or Enterprise AI because they need more configuration and handoff rules.

Can the bot use PDFs or internal documents?

Yes. For a knowledge bot or internal copilot, Exania can use approved documents, policies and FAQs. Sensitive documents should be reviewed before use.

Can the bot take payments?

The bot can guide users to approved checkout links, but payment handling should stay with secure payment providers such as Stripe or another approved gateway.

How long does setup take?

Simple website bots can be faster. More advanced WhatsApp, CRM, calendar or automation workflows take longer because they require testing and clear business rules.

Ready to build

Turn this documentation into a working AI agent.

Tell Exania what business you run, what customers ask and what you want to automate. We will recommend the right bot type, package and launch path.