RecoveryFlow by WA.cr

Description

Most sites lose more conversions than they finish. A shopper fills a cart and leaves at payment. Someone starts a booking and never confirms. A ticket order sits unpaid. RecoveryFlow is a recovery engine for WordPress commerce, forms, ticketing and booking systems. It notices when a journey stalls, works out whether the person may lawfully be contacted, and hands the conversation to WA.cr on WhatsApp, the channel people actually answer — or sends a recovery email from WordPress itself, which needs no WA.cr account at all.

RecoveryFlow detects → WA.cr communicates → customer converts.

Who makes this. RecoveryFlow and WA.cr are both products of KDC Tek Private Limited. WA.cr is our own WhatsApp Business messaging platform, built on the official WhatsApp Cloud API as an authorised Meta Tech Provider, and “WA.cr” is a registered trade name of ours in India. Neither RecoveryFlow nor WA.cr is affiliated with, endorsed by or sponsored by Meta, Automattic, Rocketgenius or the WordPress Foundation. Full attributions are in the Trademarks section.

An active WA.cr account is required, for WhatsApp

RecoveryFlow is one half of a pair. It is the detection, consent and orchestration half; the WhatsApp half is WA.cr, a separate third-party WhatsApp Business messaging platform with its own sign-up, terms and pricing. The plugin cannot send a WhatsApp message on its own.

To get a WhatsApp recovery out of it you need all of the following on the WA.cr side:

• An active WA.cr account and workspace, in good standing.
• A connected WhatsApp Business sender in that workspace.
• Either an Auto Flow with a “webhook received” trigger, on a WA.cr plan that can run one (Growth and above), or a WA.cr API key and at least one WhatsApp template approved by Meta (Scale and above).

In short: sending WhatsApp through RecoveryFlow needs the WA.cr Growth plan or above. Growth and Scale differ only in which of the two paths you get — Growth hands journeys to an Auto Flow, Scale adds workflows authored here with direct template sends. On free, trial and starter neither path can run, so no WhatsApp reminder can leave the site whatever the plugin is set to. The email channel is unaffected and needs no WA.cr account at all.

Install it without those and the WhatsApp half of the plugin is inert: journeys are still detected, recorded and held as eligible, and every WhatsApp step stalls there unsent. Nothing in RecoveryFlow substitutes for the WA.cr side of that. What does work without WA.cr is the email channel — recovery emails are sent by WordPress itself, through whatever mail configuration the site already uses, and need no WA.cr account, no API key and no plan. There is no SMS.

Creating a WA.cr account, whatever it costs on your chosen plan, and the WhatsApp conversation charges Meta bills through it are all matters between you and WA.cr. They are not part of this plugin, and this plugin is not affiliated with or endorsed by WhatsApp or Meta.

RecoveryFlow owns detection, identity, consent, timing, the recovery link and attribution. WA.cr owns the WhatsApp conversation: approved templates, replies, quiet hours and frequency limits. The plugin never talks to WhatsApp directly and never writes free text to a cold contact.

What you get

• Detection happens on your server. Integrations watch the systems you already run and record one open journey per customer, server-side. There is no tracking script and no third-party pixel: the one small script on the classic checkout sends nothing itself, it asks WooCommerce to re-read its own form when the phone or email field loses focus. Nothing accepts a request from the public unless you switch on the basket capture form, which posts only into the shopper’s own session behind a nonce and a rate limit. WooCommerce is the first supported integration; forms, ticketing and booking systems follow through the same integration interface.

• Ask before the checkout, if you want to. Most shoppers who leave never reach the checkout, so a shop that only asks there never learns how to reach most of the people it loses. RecoveryFlow can also ask on the basket page and beside the “add to basket” button, and can make the checkout’s phone number compulsory. All three are off until you turn them on, and each says plainly what it costs.

• Consent first. A journey is only messaged when the customer is both identified and eligible, and the two are shown as separate badges everywhere. Explicit consent at checkout is the default.

• Recovery links that rebuild the cart. Each message carries its own link. It merges the saved items into whatever the customer has now, never wipes anything, and lands them on checkout.
• Stops the moment they convert. The instant an order is placed, messaging stops. The journey is marked recovered when the order is paid, and the revenue is attributed to the touch that brought them back.
• Opt-out honoured from both sides. A STOP reply, the opt-out link, or an opt-out recorded in WA.cr ends every open journey for that number. The suppression survives a privacy erasure.
• Core WordPress admin, built to be accessible. Overview, journey list and timeline, integrations, settings with shareable deeplinks, and a system status screen, all on core admin components to WCAG 2.2 AA and AAA where achievable.

Two paths, and your WA.cr plan decides which

An account is required either way. The plugin pushes a signed recovery.journey_eligible event to your flow, and WA.cr runs the delays, follow-ups, stop-on-reply and quiet hours. No API key is required for the hand-off — but your workspace does have to be able to run an Auto Flow, which starts at the WA.cr Growth plan. On plans below that, RecoveryFlow still records everything it finds; it just has nowhere to hand it yet.

WordPress-authored multi-touch workflows with direct template sends, where the plugin decides the timing and content of each touch and reads delivery status and replies back, use the WA.cr developer API and are included with WA.cr Scale and above. The plugin detects what your workspace has and shows the right screens. Nothing is a disabled shell, and the Auto Flow path is complete on its own.

How it works

1. A supported integration (WooCommerce today) records activity as a Recovery Event: what was in the cart, what it is worth, and when it was last touched.
2. When the customer gives a phone number, at checkout or from their account, RecoveryFlow resolves who they are and checks eligibility: a usable WhatsApp number, consent, no opt-out, no open journey and no message in the last 24 hours.
3. After the inactivity threshold (30 minutes by default) a Recovery Journey starts under a workflow.
4. The workflow either hands the journey to a WA.cr Auto Flow, or sends an approved WhatsApp template through WA.cr with mapped variables and a recovery link, then waits and checks again before any further touch.
5. The customer taps the link. RecoveryFlow rebuilds their cart and sends them to checkout.
6. When the order is placed, messaging stops. When it is paid, the journey is recovered and attributed. If nothing happens, the journey expires quietly after seven days.

All processing runs in the background, through Action Scheduler when it is available and WP-Cron otherwise, in small, locked, resumable batches. Nothing slows the storefront.

Supported integrations

• WooCommerce 8.0 or later: carts and checkouts, classic and block-based, HPOS compatible. Available now.
• Gravity Forms 2.4 or later: save-and-continue drafts, and entries whose payment never went through. Nothing is rebuilt from a snapshot — Gravity Forms hands the half-finished form back on its own resume link. Available now; spotting these is local work and needs no WA.cr account.
• Tickera: planned.
• Event Tickets: planned.
• Easy Digital Downloads: planned.
• Your own system: register a custom integration with one PHP class through the recoveryflow_register_sources filter. See integrations.md and developer-api.md.

RecoveryFlow is not a WooCommerce plugin. WooCommerce is a supported integration; the plugin installs, activates and runs without it.

External services

RecoveryFlow requires an active account with WA.cr, a third-party WhatsApp Business messaging platform operated independently of this plugin and of WordPress. The plugin connects to the WA.cr API to send WhatsApp messages on your behalf and, optionally, to read the delivery status of those messages and any replies. Without an active WA.cr workspace and a connected sender the plugin still detects and records journeys locally, but cannot message anyone, so no recovery happens. Sign-up, plan pricing and per-conversation charges are WA.cr’s, not this plugin’s.

Where it connects

• https://api.wa.cr in production, or https://api.wacart.dev when you select the staging environment in Settings.
• For Auto Flow hand-off, the hook URL you copy from your WA.cr Auto Flow. It must use HTTPS and be on one of the hosts above.

What is sent

• The customer’s phone number in E.164 format.
• The name and language code of the approved WhatsApp template being sent.
• The mapped variable values for that template: the customer’s first name, the cart total and currency, the item count, the recovery link and your site name.
• For Auto Flow hand-off, the same values plus a short summary of item names, your site URL, the time the journey was abandoned, an opt-out link and an opaque journey reference, so your flow can personalise its own messages.
• Only when you switch them on in Settings › WA.cr: the customer’s last name and email address (default: first name on, last name and email off).

What is NOT sent to WA.cr. Recovery emails do not go through WA.cr and are not sent by it. They are handed to WordPress’s own wp_mail() and leave by whatever route the site already uses for its other mail, so no part of an email recovery — not the address, not the subject, not the message — reaches WA.cr at all.
* Only when you enable “Sync contacts to WA.cr”: the customer’s phone number and name, saved as a contact in your WA.cr workspace. Only when you enable “Sync opt-out to WA.cr”: the customer’s opt-out flag.
* Your WA.cr API key, in the request’s authorisation header, so WA.cr can identify your workspace.

When it is sent

• Only after you have saved a WA.cr API key or an Auto Flow hook URL, and only when a journey has been judged eligible: identified, consented and not opted out.
• When you press “Test connection” in Settings. This sends the API key only, no customer data.
• When the plugin lists your approved templates and connected senders in Settings. No customer data.
• Before a direct send, if you have granted the contacts:read scope: the customer’s phone number, to check whether they have opted out in WA.cr.
• When polling for delivery status and replies, if you have granted the messages:read scope: the customer’s phone number, to read that one conversation.
• When a journey is recovered or expires, if you have configured a second Auto Flow hook for those events: the journey reference and the phone number, so the flow can stop.

Nothing is sent when the integration is disabled, when eligibility mode is set to Disabled, or for journeys that are not eligible. No data is sent at install, activation or upgrade.

WA.cr: https://wa.cr. Terms of service: https://wa.cr/terms. Privacy policy: https://wa.cr/privacy.

Privacy

RecoveryFlow keeps its data in its own tables in your WordPress database. It stores:

• Identity: first and last name, email address, phone number as entered and in E.164 form, country, and the linked WordPress user ID when there is one. Phone and email are also stored as keyed one-way hashes for matching.
• A cart snapshot per journey: product names, SKUs, quantities and amounts. Never addresses.
• A consent record: granted, denied or withdrawn; where it came from (classic checkout, block checkout, account, opt-out link, STOP keyword, WA.cr, admin); the wording version; the time; and the IP address as a keyed hash only.
• Journey and message history: states, timestamps, template names, delivery status, message IDs returned by WA.cr, link clicks and attribution. Message text is never stored.
• An opt-out record. After a privacy erasure this is kept only as a one-way hash of the phone number so that the opt-out continues to be honoured.

Retention. Finished journeys are anonymised after 90 days by default; you can change the period or set it to manual. Carts that never identified a customer are deleted after 7 days. Logs are kept for 14 days and never contain phone numbers, emails, names, message text or recovery links.

Privacy tools. Tools › Export Personal Data includes RecoveryFlow data for the email address and the phone numbers linked to it. Tools › Erase Personal Data anonymises it: names, email, phone and cart items are removed, totals are kept for reporting, and the eraser reports that a one-way hash is retained to keep honouring the opt-out.

Uninstall. Deleting the plugin always removes your API key, the hash key, capabilities and scheduled tasks. Tables and settings are removed only if you enable “Delete all data on uninstall” in Settings › Privacy.

Trademarks

RecoveryFlow and WA.cr are products of KDC Tek Private Limited. “WA.cr” is a registered trade name of ours in India, and the “WAcr” in this plugin’s name is that mark — it is not an abbreviation of anyone else’s.

All third-party trademarks, service marks (™) and registered marks (®) are the property of their respective owners and are used here for identification only — including, but not limited to, WhatsApp®, Facebook® and Meta® (Meta Platforms, Inc.), WordPress® (WordPress Foundation), WooCommerce® (Automattic Inc.) and Gravity Forms (Rocketgenius Inc.). The same applies to the trademarks of any system a future integration names.

Their use does not imply any affiliation with, endorsement by or sponsorship from their owners. WA.cr is an independent service built on the official WhatsApp Cloud API as an authorised Meta Tech Provider; no endorsement beyond what is expressly disclosed is implied.