Meta's WhatsApp Business Agent in Italy: worth it?

Meta has brought the WhatsApp Business Agent to Italy, and SMBs are already getting emails from agencies promising “automated customer support in one click”.

The real question for a Head of Support or a COO isn’t “does my competitor have it too?”. It’s: does this bot solve a problem I actually have, or create yet another experience that annoys customers?

Key takeaways:

• Meta’s WhatsApp Business Agent is a generic, low-entry-cost bot: great for repetitive FAQs, weak the moment context or action inside your systems is needed.
• The decision isn’t “Meta bot yes/no”, it’s channel (WhatsApp) vs logic (who answers): you can use WhatsApp as the channel and build your own agent on top.
• A client-facing chatbot falls under the AI Act’s limited-risk tier: transparency and human escalation are mandatory.
• Without a baseline on volume and request type, you can’t tell whether you need a bot or a vertical agent. Measure first.
• Rule of thumb: below high-volume trivial questions the Meta bot is enough, above processes that touch your CRM/ERP you need a custom agent.

What the Meta bot does (and doesn’t do)

The WhatsApp Business Agent answers one precise type of request well: repetitive question, answer contained in the FAQs, zero action in your systems. Hours, shipping status, “are you open today?”, basic routing.

What it doesn’t do:

• It doesn’t know your real catalogue, the individual customer’s history, or your commercial rules.
• It doesn’t write to your CRM, ATS or ERP (TeamSystem, Zucchetti, Odoo).
• It doesn’t run a process. It answers, it doesn’t act.

It’s the same distinction we draw between ChatGPT and a vertical agent: a generic model answers, an agent built on your context runs the task and acts inside your systems.

The real decision: channel vs logic

Here’s the mistake we see most often. SMBs treat “WhatsApp” and “Meta bot” as one block. They’re not.

• WhatsApp is the channel. The official Business API is a standard, your customers already live there.
• The logic is who answers. It can be Meta’s generic bot, or your own agent running over the same channel.

Using WhatsApp as the channel and connecting a vertical agent gives you the best of both: you reach customers where they are, but with logic that knows products, customers and processes and writes to your systems. It’s the approach we use in our customer & compliance automation work.

When the Meta bot is genuinely enough

We’ll tell you straight, because Soraia doesn’t sell agents where they aren’t needed:

• High volume of trivial questions, almost all covered by 20-30 FAQs.
• No action in systems: answering is enough, no need to update orders or tickets.
• No customer-specific context required to answer well.

In that case the Meta bot is the right economical choice. A custom agent would be over-engineering.

When you need a vertical agent

You need one when the WhatsApp channel becomes an entry point to a process, not just to a FAQ:

• The customer writes and the agent must read the history, understand which order they mean, update the status in the ERP.
• The request has to be routed and enriched before it reaches the right team.
• You need an immutable audit trail of every interaction (compliance, GDPR, disputes).

It’s the same value jump we’ve measured elsewhere: at Navily an agent cut operational time by -70% on moderation and enrichment, not by answering FAQs but by running a process. The same holds on the commercial side, where WhatsApp becomes a qualification and follow-up channel (sales & marketing), not just support.

Before you decide: measure

Don’t buy either the bot or the agent before you have a baseline. For one week, count:

• How many requests arrive on WhatsApp per week.
• What percentage is pure FAQ vs requests that touch your systems.
• How long your team takes to handle them today.

Without those three numbers, any choice is an opinion. With them, the bot-vs-agent call takes five minutes.

The AI Act bill

A chatbot that talks to customers is limited risk under the European AI Act. That applies to both the Meta bot and your own agent: you must state the user is talking to an AI and guarantee escalation to a human. In our projects, the immutable audit log and transparency are default, not an add-on.

Want to work out whether you need the generic bot or an agent on your WhatsApp channel? Let’s talk for 20 minutes, or assess the fit with AI agents. No pitch, just an honest answer on your case.