Zavora 360 -- WordPress 插件

开发者	mohimenol
更新时间	2026年11月12日 01:06
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

This is the official Zavora 360 plugin, built and maintained by Royal Bengal AI, the team behind the Zavora 360 Virtual Receptionist platform at zavora360.royalbengal.ai. Zavora 360 is a Virtual Receptionist trained on your own business information. It talks to your visitors in their language, any time of day. This plugin puts it on your WordPress site and connects it to WooCommerce and your contact forms. Everything is switched on from the plugin's settings: no code to paste. What this plugin does

Talk to Us button: visitors press it and talk to your Virtual Receptionist in their browser.
Chat: the same receptionist in a chat window.
Booking: visitors book from your booking types, on a page or from a floating "Book now" button. Bookings land in your Zavora 360 dashboard.
Support form: a form that files a ticket in your dashboard, on a page (normal or wide layout) or from a floating "Support" button.
Cart Recovery (WooCommerce): your receptionist calls shoppers who left a checkout or a saved cart. Cancelled by itself if they finish the order.
Form follow-up: after a Contact Form 7, WPForms or Gravity Forms form is sent with a phone number, your receptionist calls back.
Order calls (WooCommerce): a call when an order changes to a status you pick, for example a failed payment.
New customer calls: a welcome call after someone's first WooCommerce order or after they create an account on your site. Each person is called once.
Each floating button has its own text, color and position. Buttons on the same side stack instead of covering each other, and the text color adjusts so it stays readable.
Show the buttons on every page, only on chosen pages, or everywhere except chosen pages. Keep cart and checkout clear.
Short tags ([zavora_360], [zavora_360_chat], [zavora_360_booking], [zavora_360_support]) and block editor blocks for placing them inside pages.
A Help tab with a step by step guide for every part.

Requires a Zavora 360 account This plugin connects to the Zavora 360 platform. You need an account at zavora360.royalbengal.ai. Calls and chat are paid from Credit you top up in your dashboard. Calls back (Cart Recovery, Form follow-up, Order calls, New customer calls) need Smart Outreach on your plan. Privacy and data The plugin stores its settings in your WordPress database. Conversations, bookings and support messages happen on the Zavora 360 platform under its privacy policy. See "External services" below for exactly what is sent and when.

In your WordPress admin, go to Plugins, Add New.
Search for Zavora 360 and press Install Now, then Activate.
Go to Settings, Zavora 360.
In your Zavora 360 dashboard, open Settings, API Keys, create a key and copy it.
Paste the key on the Connection tab and press Connect. The Talk to Us button now shows on your site.
Open the Help tab for a guide to each part (chat, booking, support form, Cart Recovery, Form follow-up, Order calls, New customer calls).

1.5.0

New: New customer calls. Your Virtual Receptionist calls a customer after their first WooCommerce order, or after they create an account on your site, to welcome them. Each person is called once; repeat buyers are not called. Pick the wait before calling and what to tell her.
New: calls from Cart Recovery, Form follow-up and Order calls now send the customer's first name and why the call is made, so she greets them by name (needs Zavora 360 v4.29.0; older versions ignore it).

1.4.0

New: Booking. Show your booking types on a page (block, short tag or "Create a booking page") or from a floating "Book now" button.
New: Support form. On a page in a normal or wide layout, or from a floating "Support" button. No code to paste.
New: Form follow-up. A call back after a Contact Form 7, WPForms or Gravity Forms form with a phone number is sent.
New: Order calls. A call when a WooCommerce order changes to a status you pick, cancelled if the order moves on.
New: block editor blocks for the call button, chat, booking and support form.
New: a Help tab with a step by step guide for every part.
New: faults the plugin cannot fix itself are reported to Zavora 360 so they can be fixed.
Fix: Cart Recovery could stop calling anyone: skipped or refused carts were tried again forever and blocked new ones. Each cart is now decided once.
Fix: Cart Recovery no longer calls about carts older than 7 days (changeable).
Fix: phone numbers typed without a country code get the store's (or the order's) country code.
Fix: a refusal such as no Credit pauses Cart Recovery for an hour instead of retrying every 10 minutes; a wrong number is not retried.
Fix: a customer who was called can be called again for a new cart a week later.
Fix: a suspended account now hides the buttons (and shows them again when active).
Fix: "only on these pages" and "hide on these pages" checked the last post in a list instead of the page itself.
Fix: the chat button no longer sits on top of the call button; buttons on the same side stack.
Fix: Connection shows one Credit row and the plan's real name instead of "Minutes".
Fix: the plan name in the Test connection message, the chat color picker, and uninstall now removes everything the plugin saved.
Better: new installs start in the Zavora 360 gold and every button's text stays readable on its color.
Better: the Outreach key is hidden like the API key; settings messages can no longer be set from a link.
Better: no connection check on every page view; Cart Recovery runs in the background, not in a visitor's page load.
Better: a short message in the page instead of a browser alert when a call cannot start.

1.3.7

Fix: corrected the wording on the settings screen so the configuration label reads "Virtual Receptionist" in line with the rest of the product. No functional change to the call or chat behaviour. Cumulative — includes all 1.3.6 changes.

1.3.6

Fix: when a visitor clicks the call button, the plugin now always confirms the account is still connected with a live check before opening — even if the key was revoked mid-visit. Previously the click could reuse a cached "connected" result from earlier in the page and open anyway. The chat launcher continues to appear only after the same check passes. The live check is rate-limited so it cannot be abused, and still fails open on a network blip so a working customer is never blocked. Includes the v1.3.5 auto-disconnect changes.

1.3.5

Fix: a revoked or suspended account now removes the call and chat buttons instead of leaving them live. Previously, if you deleted your API key (or your account was suspended) on the dashboard, the site kept showing the buttons — and pressing "Test connection" reported the key was invalid but did nothing about it. Now Test connection and Refresh config disconnect the site the moment the server reports the key is no longer valid.
New: the plugin re-checks your connection automatically every hour in the background, so a revoked or suspended key is detected and the buttons removed on their own — no need to press anything.
New: when a visitor clicks the call button, the plugin confirms the account is still connected before opening; if it isn't, the button is removed and nothing opens. The chat launcher is injected only after the same check passes, so a disconnected account shows no chat either. The check is throttled to at most once a minute and only ever blocks on a definitive invalid/suspended response — a brief network hiccup never hides the buttons from a working customer.

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.

Zavora 360

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: