In Ecuador, WhatsApp is where customers ask, compare and buy. If your business gets dozens of messages a day with the same questions (prices, hours, availability, order status), answering them one by one by hand eats hours and loses sales outside business hours. A WhatsApp chatbot handles the repetitive part instantly and leaves your team with what truly needs a person.
A good chatbot does not replace your team: it handles the repetitive, qualifies the customer and passes to a person whatever needs judgment.
What a WhatsApp chatbot is for
The uses that give the most value in Ecuadorian businesses:
- 24/7 service: answers about prices, hours, location, stock and payment methods, at any hour.
- Quotes and bookings: collects the data, calculates or schedules and confirms, with no manual work.
- Order status: queries your store or system and answers where the order is.
- Customer qualification: asks the initial questions and hands the salesperson an already-filtered contact.
- Reminders and follow-up: appointments, pending payments, abandoned carts (with approved templates).
- Support with handoff: if the bot cannot resolve something, it passes the conversation to a person with all the context.
See how we handle it on our AI automation page.
How it works: the official WhatsApp API
For a serious business, the right choice is the WhatsApp Business Platform (Meta's cloud API), not solutions that simulate a browser. What you should know:
- Dedicated number: a company number is registered for the API. A number already used in the regular app must be migrated carefully.
- Business verification with Meta, which enables higher limits and your brand name.
- 24-hour window: when a customer writes to you, you can reply freely for 24 hours. After that, you can only start the conversation with a Meta-approved template.
- Templates: pre-approved messages for reminders, confirmations or promotions. Each category has its own rules.
- Webhooks: Meta notifies your system whenever a message arrives, and your system replies through the API.
How a useful chatbot is built
- Define the cases: start with the 5 or 10 most repeated questions. Do not try to cover everything.
- Design the flow: what it answers, what it asks, when it says goodbye and when it hands off to a human.
- Connect it to your data: catalog, prices, calendar, orders. A bot with outdated information does more harm than no bot.
- Choose the brain: rules and menus for fixed flows, or AI to understand free-form questions. The best is usually a mix: rules for the critical (payments, data) and AI to understand natural language.
- Test with real conversations and adjust.
- Measure: which questions arrive, how many the bot resolves, how many go to a person.
If you will automate beyond chat, n8n vs Make vs Zapier helps you choose the integration tool.
What it integrates with
- Your online store (WooCommerce or custom): query products, stock and orders. See how much an online store costs.
- CRM or own system: store contacts and conversations, assign salespeople.
- Calendar and bookings: confirm appointments and send reminders.
- Invoicing and payments: send payment links or confirm receipts. For collection, review which gateway to choose in Ecuador.
- Human team: an inbox where your agents continue the conversation.
Costs: what is paid and to whom
The total cost is made of several parts, and it helps to separate them:
Item | What it is | Who charges |
|---|---|---|
WhatsApp messages | Charges for messages by type and country | Meta (check its current price list) |
Chatbot development | Flow design, integrations, testing | Whoever builds it |
AI (if used) | Per-use cost of the language model | The model provider |
Server and tools | Hosting, automations | Service provider |
Maintenance | Adjustments, new flows, support | Whoever maintains it |
Meta's pricing policy changes over time, so before budgeting check its official information and do not trust outdated figures. Have it explained to you in writing which part of what you pay is Meta's and which is the development's.
Common mistakes
- A bot that does not let you talk to a person. There must always be a way out to a human.
- Overly long replies or endless menus. On WhatsApp, brief wins.
- Outdated information on prices or stock.
- Sending unsolicited messages or promotions without consent: it risks blocking your number and losing customer trust.
- Not measuring: without data you do not know if it works.
- Promising that the AI "knows everything". Define limits and what to do when it does not know.
Privacy and consent
You are handling your customers' personal data: name, phone, conversations. Ask for clear consent, store only what is necessary and keep a visible privacy policy. Check that your provider protects that information and does not reuse it.
How long it takes
A chatbot focused on a few cases (frequent questions, a basic quote, handoff to an agent) can be running in a few weeks. With integrations to your store or system and more complex flows, the timeline grows. Starting small and expanding is almost always the best route.
How we do it at Codegea
We start by listening to your real conversations: what they ask, at what time and what takes up most of your time. With that we design the flow, connect it to your store or system, test it with your team and measure the results. We send you scope, timeline and price in writing, with no hidden costs.
Tell us how you handle WhatsApp today from contact and we will propose a first focused chatbot.
Written by
Carolina Dávila
Co-founder & Project Manager
Co-founder of Codegea. Coordinates projects, teams and deliveries so every launch lands on time.