How to make a chatbot
Making a chatbot on a general AI model looks like an afternoon of work: an API key, a prompt, a chat box. A bot that sells on a public site is a longer list. Here is that list, and what changes when you start from an agent that already has it.
Checked 12 November 2026
Seven parts of a bot that sells
To make a chatbot that answers buyers on your site, you need seven things: a language model, your content in a form the model can look through, instructions that keep it on topic, a chat widget, a place to save contacts and conversations, a way to hand a buyer to a person, and limits that stop one visitor from running up your bill. A developer can get the first three working in a few days. The other four are what make it safe to put on a public page, and they take most of the time.
Axelion is all seven, already built and tested on live sites. You type your site address, set the tone, paste one line of code, and the agent starts answering buyers. Build your own when the bot is your product or needs your private systems; start from Axelion when the bot is a way to sell what you already make.
How to make a chatbot, step by step
- Pick a model and get API access. Any general model can hold a conversation. You pay per amount of text it reads and writes, so long pages and long chats cost more.
- Turn your site into a knowledge base. Crawl your pages, clean them, split them into fragments and index them so the bot can find the right fragment for each question. Then rebuild that index every time a page changes.
- Write the instructions. Tell the model who it is, what it sells, what it must never promise and when to stop. Test it against tricky questions and rewrite until it behaves.
- Build the chat window. A widget that loads fast, works on phones, keeps the thread when the visitor changes pages and does not slow your site down.
- Capture and store leads. Ask for a contact at the right moment, save it with the conversation, and give your team a screen to see it, plus an alert when a new lead arrives.
- Hand over to a person. Decide which questions go to your team, how they find out, and how they reply without asking the buyer to start over.
- Protect it. Limit messages per visitor and per day, cap message length, accept requests only from your domain, secure the admin side and log who changed what. A public bot without limits is an open tab on your model bill.
Build it or switch it on
| Your own bot on a general model | Axelion | |
|---|---|---|
| Time to a live, safe bot | Weeks of developer time | Under a day, no developer |
| Knowledge base from your pages | You crawl, split and re-index | Built from your site, refreshed by an indexing run |
| Lead capture and console | You build and host it | Included, with the whole conversation per lead |
| Alerts to your team | You build them | Telegram on Pro and Scale |
| Per-visitor limits | You design and enforce them | Built in, and you set them per site |
| Sign-in security | Your responsibility | Two-step sign-in for every member, always on |
| Running cost | Model usage, hosting and upkeep | The plan price only |
| Full control of the code | Yes | No; API and webhooks for your systems |
The hard part is everything around the model
A prototype that answers well in a demo is the easy 20 percent. What a public sales bot needs is what happens on a bad day: a visitor who pastes a novel into the chat, a script that opens a hundred chats a minute, a question about a product you stopped selling last month, a buyer who leaves a phone number with a typo at 3 a.m. Each of these needs a rule, and each rule needs testing.
Axelion answers these with limits you can read on the Limits page: a cap on one visitor's messages and new chats per day, a cap on message length, a share of the month's conversations per address so one visitor cannot use them up, and a short message instead of an answer when a limit is reached, with the question and contact still saved as a lead.
What a home-built bot really costs
The model bill is rarely the big number. The developer's weeks are: building, then fixing, then maintaining a system that is not your product. When that developer moves to other work or leaves, the bot becomes code nobody wants to touch. Meanwhile prices change on your site and the index has to be rebuilt by hand.
With Axelion the cost is the plan, and the upkeep is your website. Pro is $49 a month for 30 conversations, Scale is $149 for 150 conversations on two sites. When your needs outgrow both, Business sizes volumes, sites and team to you.
You still get to connect it to your systems
Choosing a ready agent does not lock your data in. Paid plans include a token-protected API that hands over leads and chats as JSON, plus webhooks that send each new or updated lead with its whole conversation to your own software. Conversation data is not used to train general AI models.
When your own code is worth the weeks
Make your own when the chatbot needs to act inside private systems: check a customer's balance, change a booking, read stock levels that are not on any public page. A general model plus your own code is the right tool there, because no ready agent can see what your systems keep private.
It also makes sense when conversation is the product itself, or when you have a team that will own the bot for years and wants every line of it. For a business that wants buyers answered and leads saved, building your own is weeks spent on something that already exists.
Questions about making a chatbot
Other comparisons
Live chat software
Axelion vs a chat window your team staffs
Contact form
Axelion vs a form and an inbox
Sales development representative
Axelion vs hiring an SDR for inbound
AI SDR
Axelion vs an outbound AI SDR
Chatbot builder
Axelion vs a scripted bot you draw yourself
Building your own is one of six roads; the overview puts all of them next to Axelion.