Chatbots
Business chatbot: dialogue scripts and handover to a person
The bot answers common questions and collects inquiries in a messenger, and passes difficult questions to a person. Inquiries from the bot appear in the report as a separate line.
What the bot does
Takes requests
Asks a few questions and passes the answers to you.
Answers common questions
Address, working hours, what a service includes. The answers are written by you, or by us together with you.
Guides step by step
A simple flow: question, choice, contact.
Hands over to a person
If the bot does not know the answer, it says so and calls you.
Channels
Messenger rules and availability change. So we do not build a business on one channel: a bot can work in several messengers, and requests are duplicated to email or a site form.
Stages
Scenario
You describe common customer questions. We draw the dialogue.
Build and test
We build the bot and test every branch.
Launch
We connect it on your command.
Improvement
We see which questions the bot cannot answer and add answers.
Limits
A bot does not replace a person. It handles difficult and unusual questions poorly. It does not make decisions for you and does not promise a customer anything you did not write.
A bot collects customer data. We ask only for what is needed, add a separate consent and describe it in the policy.

A customer writes at nine in the evening, "Do you have a slot on Saturday?" The answer comes next morning, after they have booked elsewhere. A chatbot covers that gap. It handles questions that repeat, collects what an inquiry needs and hands the chat to a colleague when the talk leaves the script.
When a bot has work to do
A bot makes sense in situations like these:
- Staff type the same reply about the address, opening hours or what a service includes many times a shift.
- Messenger messages sit unread while the manager is on a call.
- Before a real conversation you need the customer's task and preferred way to be reached, and it takes three messages to find out.
- Inquiries from a messenger get retyped into a spreadsheet by hand, and some are lost on the way.
- You would like the report to show how many inquiries came through the bot.
What a bot is made of
| Element | The work |
|---|---|
| Dialogue map | You list the questions customers keep asking. We turn them into a flow: greeting, buttons, follow-up questions, branches, the exit to a person |
| Type | A button menu, a scripted exchange with answer options, a base of question and answer pairs, or a mix. We choose by what people actually ask |
| Wording | The bot's lines are written by you, or by us together with you, the way you talk to customers |
| Channels | Messengers and a web chat on your site. We also set up a copy of each inquiry to your email or to a form on your site |
| Handover line | When the bot has no answer, it says so and calls a colleague. You decide ahead of time which topics it steps back from at once |
| Personal data | We ask only for what the inquiry cannot do without, add a separate consent and describe it in the site policy |
| Testing | We walk every branch, including awkward replies such as "I don't know" or a photo instead of text |
| Growing the base | After launch we read the conversations and add answers where the bot had none |
Messenger rules change, so where the platform allows we build the script to be portable.
From contract to live conversations
The steps up to signing are on How we work. For a bot, the rest goes like this:
- Draft dialogues. You get the flow and the lines in a readable form. Read them as a customer would and strike whatever you would never say.
- Closed test. The bot is assembled in a mode visitors cannot reach. You write to it the way a customer might: politely, curtly, with typos.
- Handover rules. We agree who receives a conversation and which channel carries the notification.
- Going live. The bot launches when you say so.
- Reading the chats. We pick the dialogues where a visitor walked away or the bot got stuck, and revise the script.
What the report shows
We cannot promise a number of inquiries or sales growth: your offer, traffic and demand decide those. We settle how often reports arrive in the preliminary proposal. For a bot we look at:
- Inquiries. How many the bot collected and in which channel.
- Drop-offs. The step where people stop replying, if the platform provides such data.
- Gaps in the base. Questions the bot found no answer to. The script grows from them.
- Handovers. How many conversations reached a colleague.
- Cost per inquiry. When ads send people to the bot: spend divided by the number of inquiries.
When you can do without a bot
It works well when:
- questions repeat and the answers can be written in advance;
- your customers are used to typing in a messenger and call less often;
- a handover has an addressee: a colleague who will see the dialogue and pick it up.
Skip the bot when:
- inquiries are few and a form on the site is enough;
- every question is one of a kind, like individual quotes or disputes: those need a live person;
- you expect the bot to make decisions or promises on your behalf. It says only what you wrote.
Bot builder, freelancer or team under contract
| Bot builder | Freelancer | Team under contract | |
|---|---|---|---|
| What you get | Ready templates and a script editor | A bot for one specific job | A bot together with the site, ads and report, if those are with us too |
| Channel | Often just one, set by the service | Settled by agreement | Chosen for your audience, with a move to another channel discussed in the preliminary proposal |
| Ask up front | Whose data it is and how to take it out when you leave | Who looks after the bot once it is delivered | Which tasks are included and how the terms are set out |
Questions and answers
Does the bot improvise or follow prepared answers?
It follows prepared ones: buttons, questions with options, and a base of question and answer pairs written with you beforehand. When a question falls outside them, the bot says it does not know and passes the dialogue to a colleague.
What does the bot say at the start of a conversation?
It introduces itself as a bot. That is our default setting, and you edit the greeting at the draft stage.
Will the bot replace a manager?
No. Decisions, unusual cases and negotiation stay with a person, while the greeting, frequent questions and the first collection of details go to the bot.
What if the messenger stops working?
We set up copies of inquiries to your email and the site form, so they are not tied to a single window. Moving the script to another channel is discussed in the preliminary proposal.
Who writes the bot's lines?
Whoever finds it easier: you, or we together with you. Either way you read and edit the draft before launch, and any line that sounds like someone else is struck out.
Services that sit next to a bot
Need a bot for requests?
Leave a short request: we will send you a link to the brief. From your answers we will prepare an analysis and a preliminary proposal.