Connect Wati and review results

Wati is an optional addon, disabled by default. It connects your existing CartWhizz WhatsApp messaging channel to your Wati account. Turning on the addon does not create campaigns, start recovery rules or send customer data automatically.

Connect your Wati account

1. Open Modules and enable WhatsApp Notifications, then Wati: WA Cart Recovery & AI.
2. Open Wati → Configure WhatsApp channel and choose Wati as the provider.
3. Enter your Wati API token and choose your account region: Global, Europe or Saudi Arabia. The connector selects the correct API address. Optionally enter the Wati channel name or phone number if your account uses a specific channel; otherwise leave it blank for the account default.
4. Turn on Send messages and save. Your API token is encrypted in the existing WhatsApp channel settings and masked when read. There is no second credential form on the Wati page.
5. Return to Wati and select Check connection. This reads your template count and does not send a message.

The connection check verifies template API access. It does not verify delivery or permission to read Wati campaign statistics. After changing channel settings elsewhere, use Refresh on the Wati page.

Map an approved text template

Select Read Wati templates. The list shows up to 20 templates at a time, their exact names, language, status, body and named parameters. Search applies to the current page; use the page controls to read more. Template content is displayed as text. This action does not create or approve templates in Wati.

For a supported approved text template:

1. Copy its exact name and note its language and parameter names.
2. Open Message templates, create or edit the WhatsApp message for the intended event, and open the existing-template/manual mapping section.
3. Enter Provider template name and Provider template language.
4. Under Wati named parameters, enter each exact Wati parameter name and choose its CartWhizz event variable, then select Add parameter mapping. For example, a Wati parameter named customerName can map to the event variable customer_name. Names must match Wati exactly; numbered order alone does not identify Wati parameters.
5. Map every required parameter, mark the template approved only after it is approved in Wati, and save.

Headers, buttons and carousel templates are managed in your Wati workspace. This connector sends supported approved text templates. Other messaging providers keep using their existing parameter-order settings.

Use existing CartWhizz automations

• WhatsApp broadcasts use approved templates, audiences and existing marketing-consent checks.
• Customer audiences use CartWhizz segments. Dynamic membership is evaluated when the campaign sends; these segments are not synchronized to Wati, and already queued recipients do not change automatically.
• Abandoned carts use existing reminder settings and approved WhatsApp templates.
• Order and event rules queue messages for enabled events.
• Message activity records the local queue outcome.

Each tool keeps its existing permission, module, consent and quiet-hours checks. An accepted submission means Wati accepted it, not that the customer received or read it.

If a submission times out after it may have reached Wati, review the Wati account before retrying. CartWhizz stops automatic retries when it cannot safely tell whether Wati accepted the message.

Read CartWhizz results

The Wati page automatically reads this store's local CartWhizz records for the selected 7-, 30- or 90-day period. It shows queued, accepted, failed and suppressed messages, activity by event, cart recovery and up to 20 campaigns with the newest Wati activity.

Cart recovery shows reminders followed by recovery, deduplicated by cart and order. Campaign attribution uses CartWhizz's existing last-touch policy. Attributed values are gross placed-order totals, grouped by currency; they are not profit or proof that a message caused a sale. Invalid, failed, voided and refunded orders are excluded.

Local results do not contain verified delivery or read counts because this connector does not receive authenticated Wati delivery callbacks.

Read optional Wati account totals

Read Wati account totals explicitly requests Wati's account-wide broadcast statistics for the selected period. These totals can include activity outside CartWhizz. They are separate from the local store results and must not be treated as CartWhizz attribution.

Your Wati token may need additional permission to read campaign statistics. If that read fails, the connection check and template tools can still work. No provider statistics are requested automatically when the page opens.

Find customer context

With Manage settings, View users and View orders, search customers by name or email, then select View context. This lookup reads only CartWhizz records and does not send customer data to Wati.

The profile includes up to 20 recent orders, up to 20 products viewed while signed in, and paged local Wati message activity. Anonymous browsing is not merged into the customer. OTP messages and message content are excluded. Open the linked customer or order to use its normal admin detail page.

This is CartWhizz customer context, not a synchronized Wati conversation inbox.

Use the Wati workspace

Use Open Wati for Wati-hosted shared inboxes, AI agents, chatbot and automation flows, carousel campaigns and the channels available to your account. This addon does not build or synchronize those resources in CartWhizz. Review availability, API access, message fees and your subscription on the Wati pricing page.

Click-to-WhatsApp ad-source tagging, inbound conversations, customer replies, opt-outs, reply windows and delivery callbacks are not imported by this connector. Keep customer consent in CartWhizz up to date when opt-outs arrive in Wati. Use approved templates for CartWhizz automations and the Wati workspace for conversations.

Do not configure a CartWhizz callback URL for Wati. CartWhizz's WhatsApp Shop continues to use its separate Meta integration.

Permissions, mobile and disabling

Local results require View reports or Manage settings. Connection settings, template reads and optional Wati account totals require Manage settings. Customer context also requires View users and View orders. Each route requires the Wati addon to be enabled.

The native admin app offers the same Wati status, explicit account reads, local results and customer context. Existing channel, template and campaign editors use their authenticated web handoff; the template editor includes the named-parameter mapping form.

Disabling Wati stops Wati provider access, including queued sends. Saved templates, message history and credentials remain available for later use. The WhatsApp channel's Send messages switch separately stops sending for that channel.