Official WhatsApp with AI: connect processes and understand costs

A message should advance the process

A delivery confirmation can update a control tower. A quote request can trigger an ERP lookup. An incoming document can feed a review task. The channel creates value when the conversation stays linked to an order, owner and next action.

Choose one workflow and define completion. Receiving a reply does not approve a quote, change an order or authorize payment. For the first pilot, use authorized contacts and synthetic data, retain human review for business actions and compare results with the current process.

Prepare the account and connect through Meta

Cloud API uses a Meta business portfolio, a WhatsApp Business Account (WABA) and a business phone number. Confirm with the administrator who may authorize those assets. Account and phone-number identifiers differ from the visible phone number and the Zild API key.

In the reviewed Zild version, open the WhatsApp API channel configuration and save it before connecting. In the Meta connection area, use Login with Facebook and complete embedded signup with the company assets. The interface receives an authorization code, WABA ID and Phone Number ID; WhatsApp Identifier and WhatsApp Account SID are read-only fields in this workflow. Labels may be translated depending on interface language.

Wait for connection confirmation and reopen the channel to check its agent association. A coexistence option exists in the implementation, but selecting it does not prove Meta has enabled the account and number. Confirm eligibility during embedded signup before planning simultaneous use or migration of an existing number.

Confirm operations before expanding the channel

Cancelled signup, missing identifiers and pending authorization are incomplete states. Check the displayed message and permissions with the owner; do not remove an active integration merely to retry. Screen availability depends on the deployed version.

With an authorized test contact, separately validate incoming messages, agent replies, delivery status and handoff to the correct queue. Check the association between channel, conversation and process; an API-accepted send does not prove delivery or receipt of events. If an event does not arrive, the administrator must review the webhook subscription and destination for the deployed integration. This guide does not provide a universal webhook URL.

Record the outcome, time and failure owner without copying tokens into the report. Only then expand recipients and volume. For template tests, confirm language, variables, approval and purpose; follow the window and consent rules applicable to the channel.

Shared contacts in field processes

When the WhatsApp channel receives a shared contact, the integration prepares a message for each contact in the event. Text uses the name and the first non-empty phone number received. When the event contains a vCard accepted by the integration, it is stored as contato.vcf and associated with the message; missing content or invalid encoding leaves readable text without a vCard file.

For a delivery or technical visit, use this to record the contact provided for the location and review it alongside the incident. Do not confuse the shared contact with the conversation sender: receiving a card does not establish identity, permission to change the recipient or creation of an ERP record. Confirm the responsible person and delivery or service-order reference before operational changes.

Use fictional data to validate a contact with a file, a text-only contact and an event containing multiple contacts. Check the messages actually persisted in the deployed version; the text summary does not guarantee that all phone numbers in the card are visible.

Separate three budget components

The Zild subscription follows company size and the contracted band. External models and services use customer-configured credentials and have separate charges. WhatsApp also has channel rates, plus any charges from the contracted messaging provider.

Budget for subscription, channel, AI, implementation and operations. Avoid counting the same rate twice when a partner already includes it in an invoice. Record currency, applicable taxes, allowances and included services. A message with no Meta charge can still invoke a model, OCR or another paid tool.

Reference rates for Brazil

On 28 October 2026, selecting Brazil and BRL in the official pricing tool displayed BRL 0.3217 per marketing message and BRL 0.0350 per utility message in the initial tier. Charges depend on delivered messages, category and recipient market. Service messages are free; utility messages responding to users have a free condition. Utility and authentication have volume tiers.

Synthetic example: 1,000 chargeable marketing messages and 2,000 chargeable utility messages, all delivered in Brazil within the initial tier, produce BRL 391.70 in message charges: 1,000 × 0.3217 + 2,000 × 0.0350. This is not the total project price. Check the official selector and current rate card before approving a budget; currency, category, free conditions and volume change the calculation.

Plan the window, template and human escalation

Meta policy requires recipient permission for subsequent contact and respecting opt-outs. The 24-hour customer service window opens and resets with user messages. Outside it, sending requires approved templates. Automation must provide a clear escalation path.

In the workflow design, record the contact purpose, selected template and exception owner. Do not disguise a commercial offer as an operational update. The agent should recognize missing information or requests for a person, preserve context and route the case to the responsible team.

Connect sending to the actual API contract

Zild Docs describe proactive sending as an agent tool and the POST /Conversation/whatsapp-proactive-conversation operation. The contract includes channel, recipients, agent, template, variables and queue. Zild API authentication uses X-API-Key; this key differs from channel-provider or AI-model credentials.

Validate the channel and template in the deployed environment before supplying their identifiers. Do not treat conversation creation as delivery confirmation. The message model documents send, delivery, read and failure states; define how the process tracks them. After an interruption, reconcile the event before retrying to avoid duplicate messages.

Evaluate cost per completed process

Test wrong recipients, missing variables, unavailable templates, repeated messages, expired windows, opt-outs and human escalation. For a logistics confirmation, check whether the reply was associated with the correct delivery and whether a discrepancy created an issue with an owner.

Track delivery, correct completion, rework, escalation and total cost per closed case. Separate marketing campaigns from operational updates in reporting. Define a spending limit and an owner to review volume increases. The objective is a shorter, controlled process, not indiscriminately increasing message volume.