WhatsApp chatbot: comparing providers — what really matters

01 — Criteria

How quotes differ

• What exactly is included. Two quotes with the same total can cover completely different deliverables. Ask for scope as a list, not as running text.
• Who delivers what. Content, images, data, access — if it's not specified, it becomes a point of conflict later.
• What operation costs. Calculated over three years, including licenses, hosting, and support.
• What happens if you want to switch. Do you get access, data, and documentation? The answer to this question says more about a provider than any reference.
• Who actually does the work. With small providers this matters: who sits in the meeting, and who then does it.

02 — Questions

Questions you should ask

• What happens if the project becomes more expensive than estimated — who bears that?
• Who owns data, access, and, if developed, the source code?
• What does operation cost in the second and third year?
• What does the documentation we receive at the end look like?
• How would you measure whether the project was successful?
• Is there a case in which you would advise us against this?

03 — Warning signs

When to be skeptical

• Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
• No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
• Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
• Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
• No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.

04 — Scope

What's included

• Setup of the official WhatsApp Business access including verification
• Automatic replies to the most common requests, with handoff to a human
• Shared inbox for the team instead of messages on a personal phone
• Templates for appointment reminders, order status, and follow-up questions
• Integration with CRM or order system so conversations belong to the customer
• Opt-in logic and data protection notices per GDPR