Chatbot

Chatbot Deployed in One Hour: What It Really Takes

A standard chatbot really can be built and handed over within one hour, but only under clear conditions. This guide lists what you must prepare before the build starts, what kills the speed, what can safely wait until after go-live, and why a full ERP system never fits into an hour.

A chatbot deployed in one hour is realistic when the bot is a standard one and your content is ready before the build starts. At AI Media a standard chatbot is built inside the panel and handed over within one hour once the answers, catalogue, working hours and account access are prepared. The hour is build and test time; it does not include writing your business information for the first time.

This guide explains what the hour actually covers, what you must prepare, what slows a chatbot deployment down, and where the one-hour promise honestly stops.

What a one-hour chatbot deployment includes

A standard chatbot has a defined scope. Within the hour you get a working bot that does the following.

• One or two channels connected: Instagram DM, WhatsApp, Facebook Messenger or the website chat widget
• A knowledge base loaded with your questions and answers, so the bot replies from your own material
• Your catalogue or service list shown inside the chat
• Lead capture: name, phone number and what the customer wants
• Working-hours logic and a clear out-of-hours reply
• Live agent handover, where the bot pauses as soon as a person joins the same conversation
• A short test round against real customer questions

Everything is configured inside the NERO panel itself. There is no external automation layer to install, no n8n, Make or Zapier subscription, and no separate server to rent. That is one of the main reasons an hour is enough. The website chat widget is generated in the same panel, so a single code snippet goes on your site.

What must be ready before the clock starts

The hour starts when your content is on the table. Preparing that content usually takes days, and it is the part only you can do. Collect these five things first.

1. Questions and answers

Open your existing Instagram or WhatsApp inbox and read the last few weeks of messages. Write down the questions that repeat and the answer you would give to each one. Plain sentences are enough, because the bot turns them into natural replies. This one document decides how good the bot will be. The knowledge base can hold up to one million tokens, so length is not the constraint here; clarity is.

2. Catalogue or service list

Product or service names, short descriptions, variants and how they are grouped. A spreadsheet is perfectly fine. If the catalogue is long, start with the items customers actually ask about and add the rest after go-live.

3. Working hours and holidays

When you are open, when you are closed, which day is a day off, and what should happen at night. Also decide what the bot says when nobody is available: promise a call back in the morning, or collect the details and close the conversation politely.

4. Pricing rules

Not necessarily figures, but rules. Is the charge fixed, per square metre, per person, per kilogram? Does it change by district, by urgency or by quantity? If your quote depends on a measurement or an inspection, the bot should explain the rule and collect the data needed for a quote instead of guessing. Our own pricing page shows how this kind of logic is written down for a service business.

5. Account permissions

• Instagram: the account must be a professional (business or creator) account, linked to a Facebook page you administer
• WhatsApp: choose between the official Cloud API and QR connection, and make sure the number is free, because a number already logged into the WhatsApp Business app cannot be connected at the same time
• Facebook Messenger: page admin rights, not editor rights
• Website: somebody who can paste one snippet into the site template
• People: the person who owns these accounts should be reachable during the build hour

Missing account access is the most common reason a one-hour build turns into a three-day wait.

How the hour is actually spent

Stage	Roughly	What happens
Channel connection	First 10 minutes	Instagram, WhatsApp, Messenger or the website widget is linked to the panel
Knowledge base load	Next 15 minutes	Your questions, answers, catalogue and pricing rules are uploaded and organised
Scenario build	Next 15 minutes	Greeting, main menu, lead capture, out-of-hours reply and handover rule in the visual flow builder
Testing	Next 15 minutes	Real questions asked from a second phone; weak answers corrected on the spot
Handover	Last 5 minutes	Panel access, roles and a short walkthrough for your team

None of these steps needs a developer when the content is ready. When it is not ready, no step can be finished, and the hour becomes a waiting room.

What kills the speed

• Content that does not exist yet. "We will send the answers later" is the single biggest delay in any chatbot setup.
• No decision-maker in the room. Someone must be able to approve what the bot says about refunds, delivery times and discounts.
• Missing access. A password left with a former employee, an Instagram account still in personal mode, a WhatsApp number already in use elsewhere.
• Platform verification. The official WhatsApp Cloud API route requires a verified business account on the platform side, and that waiting time is outside anyone's control. The QR route avoids it.
• Scope creep during the build. "Can it also write orders into our accounting system?" is a fair question and a separate project.
• Perfectionism. Trying to cover every rare question before launch. A bot improves fastest from real conversations, not from imagined ones.

What you can safely leave for later

A narrow bot that answers correctly beats a wide bot that never launches. These items can all be added after the first version is live, without rebuilding anything.

• Additional channels, once the first one is stable
• Deep branching scenarios and specialised flows for edge cases
• Integration with your database, ERP or order system
• Broadcast messages and follow-up sequences
• Team roles, shift distribution and per-channel permissions
• Analytics review and knowledge base tuning based on failed answers
• Extra languages, although the bot already detects the customer's language and replies in it from day one

When one hour is not realistic

The one-hour figure applies to a standard chatbot and nothing else. The following are different projects with different timelines, and it is fair to say so plainly.

ERP and back-office systems. Production tracking, warehouse, cost price and payroll depend on your real processes and on migrating existing records. Ready industry systems such as e-konveyer.aimedia.az for manufacturing control, e-ferma.aimedia.az for poultry and farm accounting, and naxis.aimedia.az for carpet cleaning operations shorten the work considerably, but adapting one to your workflow and moving your data still takes weeks. Anyone promising a full ERP in an hour is showing a demo, not a system.

Bots that read and write your live data. A bot that checks stock, confirms order status or writes a new order into your database needs that database to exist and to be reachable from the outside. Reasonable to build, but not a one-hour job.

AI voice call agents. Voice needs scripting, pronunciation checks and telephony setup. Plan for more than one session.

Custom software. When no ready product fits, the timeline follows the specification. The services page and the products page show which category your task falls into.

Common mistakes after go-live

Turning the bot on and never looking at it again. The first week produces the most useful data you will ever get: the questions the bot could not answer. Review that list once and the quality jumps.

Letting the bot argue. Complaints, disputes and unusual requests belong to a human. Set the handover rule on the first day, not after the first angry customer.

Hiding the human option. Customers relax when they know a person is one message away. Say it in the greeting.

Copying a competitor's script. Your prices, delivery terms and exceptions are yours. A borrowed script produces confident wrong answers, which cost more than no answer at all.

Next step

If your answers, catalogue and account access are ready, a standard bot can be live today. If they are not, the useful first step is a short conversation: describe what you sell and which questions eat your team's time, and we will tell you honestly whether one hour is enough or whether your case is a larger project. The initial consultation is free and carries no obligation.

Contact page · Message us on WhatsApp · Platform: app.aimedia.az · More about us: AI Media company profile