Zavora 360

Registro de cambios

1.3.4

• New: Cart Recovery now self-heals. WordPress only runs scheduled tasks when a request hits the site and its built-in cron spawn is unreliable on quiet sites, so recovery could sit dormant. The plugin now runs an overdue scan in the background at the end of any request (after the page is sent, so no added load time), throttled to at most once every five minutes and locked so it never double-runs. On any normally-trafficked store, recovery now works automatically once enabled — the manual server cron is only needed for genuinely zero-traffic sites.
• New: admin notice when Cart Recovery is enabled but the scan has not run for 30+ minutes (a quiet site with no real cron), with a link to the fix and a one-click dismiss-for-12-hours. The last scan time and summary are now stored so the dormancy check (and a future settings readout) work without reading the debug log.
• Docs: the cron FAQ now explains the self-heal behavior and exactly when a real server cron is still required.

1.3.3

• Docs: added a FAQ entry explaining how to keep Cart Recovery running on a live site. WordPress only runs scheduled tasks on visitor traffic, so on a quiet site the recovery scan can sit idle and place no calls; the FAQ walks through disabling traffic-triggered cron (DISABLE_WP_CRON) and driving wp-cron.php from a real server cron every five minutes, with guidance for cPanel/Plesk, raw servers, managed WordPress hosts, and external cron services. No code or behavior change — documentation only.

1.3.2

• Diagnostics: the Cart Recovery scan now writes a single summary line to the WordPress debug log on every run, so it always reports what it did even when it places no call. The line records how many checkout drafts and how many logged-in carts were considered, how many calls were queued, and the exact reason each candidate was skipped (already queued, no phone, below minimum value, already at checkout, empty cart). When the feature is off, the key is missing, or WooCommerce is unavailable, the scan now says so instead of returning silently. No behavior or calling logic changed — this release only makes a scan that queues nothing explain itself.

1.3.1

• New: Cart Recovery now also covers logged-in shoppers who leave a cart before reaching checkout, when they have a phone number saved on their account. Previously recovery only fired once a shopper reached checkout and entered a phone; now a registered customer who adds items and leaves can be called using their account phone. Guests, and logged-in customers without a saved phone, are unchanged — for them only the checkout stage qualifies.
• Behavior: the logged-in cart layer never double-calls. A shopper who later reaches checkout is handed to the checkout path (the cart call is cancelled), and completing, cancelling, or emptying the cart cancels a pending cart call. Because WooCommerce does not timestamp the cart, a cart only becomes eligible once it is touched while v1.3.1 is active.

1.3.0

• New: Cart Recovery (Smart Outreach). When a shopper enters their phone at WooCommerce checkout but doesn’t complete the order, your Virtual Receptionist can call them back after a delay you choose to help them finish. Configure it on the new Cart Recovery tab in Plugin Settings: enable the feature, paste your Outreach API key (from the Smart Outreach tab of your dashboard), set how long to wait before a checkout counts as abandoned, the delay before calling, an optional minimum cart value, and an optional context line for the call.
• New: if the shopper completes (or cancels) the order before the scheduled call, the call is cancelled automatically — a customer who already bought is never called.
• Notes: Cart Recovery requires WooCommerce and only fires for checkouts where a phone number was entered, in dialable international format. Detection runs on an approximately 10-minute schedule, and calls are placed inside the calling window you set on the dashboard. Requires a Zavora 360 platform on v3.29.4 or later (for the outreach trigger and cancel endpoints).

1.2.1

• New: the Connection tab’s status table now shows your current chat credit balance alongside the existing Minutes row. The figure is fetched from the Zavora 360 platform on Connect / Refresh, formatted in USD as “$X.XX remaining”. The row only appears when chat is enabled on your tenant — voice-only customers see no change.
• Compatibility: requires a Zavora 360 platform on v3.11.1 or later to populate the chat balance figure. Against older platforms the row is silently suppressed and the Connection tab behaves exactly as in v1.2.0.

1.2.0

• New: Chat tab. The plugin now supports the Zavora 360 Chat Receptionist alongside the existing voice button. Enable chat from the new Chat tab in Plugin Settings — pick a button label, color, position, and an optional welcome greeting. The chat panel is independent from the voice button; you can run either, both, or neither.
• New: [zavora_360_chat] shortcode for inline placement, mirroring the existing [zavora_360] voice shortcode. Supports per-shortcode overrides: color, label, position (br/bl/tr/tl), and greeting.
• New: visitors picking from your enabled languages on the first screen of the chat panel. Your tenant’s language list is fetched from the Zavora 360 platform on Connect / Refresh — keep it up to date by clicking Refresh on the Connection tab whenever you change your enabled languages on the dashboard.
• Improvement: the Connection tab’s Refresh action now also caches the chat widget public key, default language, and language list locally, so the chat button renders without an extra round-trip per page load.
• Compatibility: requires a Zavora 360 platform on v3.10.0 or later for the chat surface. The voice button continues to work against any prior platform version — chat-related fields are optional in the platform’s widget-config response and degrade gracefully when absent.

1.1.4

• Maintenance: documentation URLs for the Zavora 360 platform’s privacy policy and terms of service now point at the platform’s actual subdomain (zavora360.royalbengal.ai) instead of the parent corporate domain. Affects the Privacy and data section, the GDPR FAQ, and the External services section in this readme.
• Maintenance: renamed the admin-page JavaScript localization handle from rvaAdmin to z360Admin for consistency with the plugin’s z360 prefix used throughout the rest of the codebase since v1.1.0. Internal-only change with no impact on the plugin’s functionality, settings, or user-facing surfaces.
• Removal: the legacy [royal_voice_agent] shortcode alias added in v1.1.0 for backward compatibility with v1.0.x installs is removed. The canonical [zavora_360] shortcode remains the only supported form. If you have any content using [royal_voice_agent], update it to [zavora_360] — both render the same Talk-to-Us button.

1.1.3

• Maintenance: documentation alignment with the Zavora 360 platform’s v3.4.2 release, which migrated the platform’s API key format to the new z360_ prefix. If your API key was issued before May 23 2026 and starts with rva_, regenerate it from your Zavora 360 dashboard and paste the new key into Plugin Settings → API & Connection.
• Maintenance: clarified plugin ownership in the Description — this is the official plugin, built and maintained by Royal Bengal AI.

1.1.2

• Maintenance: refined plugin description and FAQ language for consistency with the Zavora 360 brand voice. No functional change.
• Documentation: added a dedicated External services section to this readme covering exactly which endpoint is called, what data is sent, what data is not sent, and when the calls happen — meeting current WordPress.org plugin directory guidelines for plugins that communicate with external services.

1.1.1

• Maintenance: removed legacy class-rva-*.php files and the royal-voice-agent.pot translation template that were left behind after the v1.1.0 rebrand. Dead code only — autoloader has always loaded Z360_* classes exclusively, so this is a pure cleanup with no functional change.

1.1.0

• Rebrand: Royal Voice Agent is now Zavora 360. New brand, same plugin — connects to the same platform at the new URL https://zavora360.royalbengal.ai.
• New: canonical shortcode is now [zavora_360]. The legacy [royal_voice_agent] shortcode tag still works for any existing content — both tags map to the same handler. Use [zavora_360] going forward.
• Internal: the plugin folder is now zavora-360/, the main file is zavora-360.php, and the PHP class prefix changed from RVA_ to Z360_. Option keys migrated from rva_* to z360_* on activation (your saved API key, button settings, etc. carry over automatically — no reconfiguration needed).
• Maintenance: developer comments and documentation updated for the new name. No functional changes beyond the rebrand and shortcode alias.

1.0.3

• Improvement: the Visibility picker gains three new tools — a “Show selected only” toggle that hides unticked items so you can review your picks at a glance, a “Select all visible” link that ticks every item currently shown (great combined with search — e.g. search “blog”, then click Select all visible), and a “Clear all” link that unticks every item across both tabs.

1.0.2

• Improvement: the pages-and-posts picker on the Visibility tab now has type tabs (Pages / Posts) and a search box so you can quickly find a specific item on sites with lots of content. Each tab shows its item count. Search filters within the active tab.
• Improvement: a selection counter under the picker shows how many pages and posts you currently have ticked — useful as a sanity check before saving.

1.0.1

• Fix: live preview on the Appearance tab now updates in real time as you change label, color, position, or size.
• Improvement: the Visibility tab now lists both Pages and Posts (each with a “Page” or “Post” badge), so you can target either type. The previous Pages-only multi-select has been replaced with a checkbox list — one click per pick, no Ctrl/Cmd-click needed.
• New: clicking the Talk-to-Us button now opens the Virtual Receptionist in a centered popup window (480×720) instead of a new tab. Modifier-click (Ctrl/Cmd/Shift) still opens in a new tab. If the popup is blocked, falls back to the original new-tab behavior.
• Improvement: the Help tab now includes step-by-step instructions for adding the [royal_voice_agent] shortcode in both the Block Editor and Classic Editor.

1.0.0

• Initial release.