1. Choose the goal
Start with one main outcome: answer FAQs, qualify leads, book appointments, support customers or automate internal tasks.
Define outcomeA 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.
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.
Start with one main outcome: answer FAQs, qualify leads, book appointments, support customers or automate internal tasks.
Define outcomeMicro Bot for simple web FAQs, Launch Bot for a polished chatbot, Growth Agent for sales and booking, Automate System for integrations.
Select planSend your website, services, prices, FAQs, policies, opening hours, examples and the tone you want the bot to use.
Train safelyWe configure, test, install and monitor the agent. After launch, optimization keeps the bot useful and aligned with your business.
Go liveEvery bot has a different role. The best projects are specific: one agent, one workflow, one measurable result.
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.
A WhatsApp agent replies to customers where they already communicate. It can answer, collect information, qualify requests and route urgent conversations to a human.
A lead qualification agent asks the right questions before a human gets involved. It helps separate casual visitors from serious prospects.
A booking assistant helps people schedule calls, appointments, consultations or visits. It can answer pre-booking questions and reduce back and forth messages.
An automation system connects your AI agent with operational tools. It can summarize requests, update sheets, route tasks, prepare reports and trigger follow ups.
Good inputs make the bot useful. The more specific the business information, the better the answers, routing and recommendations.
Company name, website, industry, location, languages, opening hours, service area and preferred tone.
Services, packages, prices, what is included, what is not included, common objections and qualification rules.
What counts as a good lead, what questions to ask, when to book a call and when to notify your team.
Real customer questions, refund policies, cancellation rules, delivery times, support boundaries and safety disclaimers.
Website platform, CRM, forms, calendar, spreadsheet, email route, notifications and internal tools.
Topics the bot should avoid, sensitive cases, legal or medical disclaimers, and when a human must take over.
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>
The bot should answer from approved business knowledge and avoid guessing when the information is missing. Important information should always be checked.
| Data type | Examples | How the bot uses it | Best practice |
|---|---|---|---|
| Services | Packages, pricing, descriptions, deliverables | Explains what you offer and recommends the right option | Keep updated |
| FAQs | Hours, locations, delivery times, refunds, process | Answers common questions without involving your team | Use real customer questions |
| Lead rules | Budget, urgency, industry, location, service fit | Scores leads and routes high intent requests | Define hot lead criteria |
| Policies | Cancellation, support limits, privacy, terms | Provides boundaries and prevents overpromising | Review carefully |
| Internal docs | PDFs, SOPs, guides, onboarding notes | Supports internal copilot or knowledge bot | Limit access by use case |
| Sensitive data | Passwords, payment details, private records | Should not be used as training content unless a secure approved workflow exists | Avoid by default |
Exania agents are built to reduce repetitive work, not remove responsible human review. The handoff rules keep the experience useful and safe.
The agent identifies whether the user wants support, pricing, booking, purchase advice, technical help or human contact.
Name, email, phone, business type, service needed, urgency and message summary are captured only when relevant.
If the request is sensitive, unclear or outside the approved knowledge, the bot should not invent an answer.
The conversation summary can be sent to email, Telegram, CRM, dashboard or another approved business workflow.
Complex, urgent, legal, medical, financial or account sensitive issues should be reviewed by a responsible person.
Choose the plan based on the workflow you want, not only the channel. More integrations require more setup, testing and maintenance.
Basic website chatbot for FAQs and simple contact capture. Best when you need a fast starting point.
$390 + $79/moProfessional website chatbot with stronger presentation, lead capture and email alerts.
$590 + $149/moRecommended for lead qualification, booking flows, WhatsApp or more serious sales workflows.
$1,200 + $299/moAdvanced automation connecting forms, CRM, sheets, calendar, documents, reports and internal tools.
$2,500 + $599/moAI can make mistakes. Important information should be checked, and sensitive workflows should use human review and approved data handling.
The bot should answer from business approved sources and avoid unsupported claims when information is missing.
Collect only the details needed for the workflow. Avoid passwords, payment card details or unnecessary private information.
For important, legal, medical, financial or account sensitive information, the bot should recommend human verification.
Every production bot should have a fallback route so the user can reach a human when needed.
Before launch, test common questions, edge cases, weird phrasing, wrong assumptions and lead routing.
Update the knowledge base when services, prices, hours, policies or business processes change.
A bot is not finished forever on launch day. It should improve as the business changes and as users ask new questions.
Yes. Exania bots can be configured for English, Spanish or automatic language detection depending on the project.
No. The goal is to reduce repetitive work, answer faster and prepare better summaries. Complex or sensitive issues should still go to a human.
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.
Yes. WhatsApp workflows are usually part of Growth Agent, Automate System or Enterprise AI because they need more configuration and handoff rules.
Yes. For a knowledge bot or internal copilot, Exania can use approved documents, policies and FAQs. Sensitive documents should be reviewed before use.
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.
Simple website bots can be faster. More advanced WhatsApp, CRM, calendar or automation workflows take longer because they require testing and clear business rules.
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.