serpixel, a registered Meta Tech Provider: WhatsApp agents on the official API

More and more small businesses take orders, questions and requests over WhatsApp. The channel works because it is the one their customers already use, but it carries a hidden cost: someone on the team spends hours reading messages, looking up the customer in the system and copying data by hand. That is exactly the kind of repetitive process an AI agent can take on, as long as it is built on the right foundation.

So it is worth starting with a concrete piece of news: serpixel (Clever European Business, S.L.) is a registered Tech Provider on Meta and builds bespoke agents on the official WhatsApp Business API. This article explains what that means for a business, how it differs from unofficial solutions, and how it fits with the human team that answers those messages today.

What being a registered Meta Tech Provider means

Meta defines the Tech Provider role for companies that connect software or agents to WhatsApp Business on behalf of their clients, through the official platform. It is the intended, authorized route for a third party like serpixel to integrate an agent into a business’s WhatsApp account without that business losing control of its number or its data.

serpixel being registered as a Tech Provider has a practical consequence: every implementation rests on the WhatsApp Business Cloud API, the interface Meta itself publishes. No shortcuts. Each client’s account is connected under its own control, with permissions scoped to exactly what the automated process needs.

The official API, no virtual numbers or WhatsApp Web tricks

The market is full of solutions that promise to “automate WhatsApp” through routes worth avoiding. The two most common:

• WhatsApp Web automations. They mimic a person using the browser version of WhatsApp. They depend on a phone or a server staying on, they break with every update, and they expose the account to bans, because they use the platform in a way Meta does not authorize.
• Virtual numbers. They ask you to set up a new number your customers do not recognize, breaking the continuity of the channel that already works.

The official WhatsApp Business API fixes both at the root. It is a stable, authorized interface: every inbound message arrives signed so its origin can be verified, the connection does not depend on a phone being on, and there is no risk of a ban for using disallowed tools. Building on the Cloud API is not a technical detail; it is the difference between an integration that holds up in production and a workaround that fails at the worst possible moment.

Coexistence: your number and your app stay yours

A business’s most common worry is reasonable: “if I connect an agent, do I lose my usual WhatsApp?”. The answer is no. serpixel works in coexistence mode.

In coexistence, the business keeps its number and keeps using the WhatsApp Business app on the phone as before. The agent runs on that same number through the official API, without displacing manual use. And the part that matters most for the team: anyone can take over a conversation at any time. If the agent has started handling an order and the case gets complicated, someone on the team steps in, reads the full thread and continues from the app itself. That handover, from agent to person and from person to agent, is what we call takeover.

The result is that the end customer notices no change of channel or number. They write to the same WhatsApp as always. Behind it, the mechanical layer of the process is resolved faster and human hands are freed for what really needs them.

The agent handles the mechanical layer; the team keeps the judgment

Here is the principle that guides every serpixel project. An agent does not replace a person. It takes on the mechanical layer of a bounded process (clear rules, repetitive volume, long hours) so the human team can focus on what only people do well: judgment in the doubtful cases, the final decision and the customer relationship.

In a WhatsApp order flow, that mechanical layer is concrete: read the message, identify the customer in the system, retrieve their history, look up the products in the active catalog, check stock and compose a draft order. What the agent does not do is blindly close an ambiguous case. When the message is incomplete, when the customer is not found or when the product is unclear, the process is handed to a person. Human judgment stays the reference.

One bounded workflow per project

serpixel scopes every engagement around a single process with one measurable success metric. We do not automate “WhatsApp” in the abstract; we automate a concrete flow. The canonical example:

WhatsApp order intake into the ERP. Metric: share of orders turned into a draft with no human edit.

Starting bounded is not a limitation; it is the serious way to work. One process, one channel, one metric. Once that first flow is live and measured, the next one can be planned. What we do not do is promise a system that does everything on day one; that is smoke, not a project.

Kill-switch, human fallback and data ownership

An agent that touches real orders needs real brakes. Every serpixel implementation includes three guarantees from day one:

1. Kill-switch. A way to disable the agent instantly, without depending on the provider. If you notice odd behavior, the agent stops within minutes.
2. Human fallback. Once the agent is off, conversations return to the team, who keep seeing and answering them from the same WhatsApp Business app. The process does not stop; who runs it changes.
3. Data ownership. The WhatsApp account and the number belong to the business. The data belongs to the client. serpixel acts as data processor under the contract, with sub-processors declared, and hands over prompts and configuration if the relationship ends.

This is the part inflated proposals tend to dodge. For serpixel it is a requirement, not an optional extra.

What to do now

If your business takes orders or questions over WhatsApp and the team loses hours handling them by hand, there is a conversation worth having before asking for quotes. In a 30-minute discovery session we put the process on the table and come out with three things clear: which mechanical part the agent can take on, which success metric to measure, and what the minimum viable architecture on the official WhatsApp Business API would look like.

If you want to have that conversation, let’s book 30 minutes on Calendly. No commitment to hire and no sales pressure: just the conversation needed to know whether the project makes sense and, if it does, where to start.