Zavora 360

Yes. This plugin is the WordPress connector for the Zavora 360 platform. Sign up free at zavora360.royalbengal.ai — Free plan includes 10 minutes per month.

Free plan: 10 minutes per month, no credit card needed. Paid plans from $4.99/month for more minutes plus outbound calling and call forwarding to your human team. See pricing .

Yes — the floating button is responsive and the call popup works in mobile browsers. Visitors need to allow microphone permission when prompted.

No noticeable impact. The plugin’s frontend footprint is a small CSS file (~2 KB) and an HTML button. No JavaScript loads on the frontend unless a visitor actually clicks the button.

All voice processing happens on the Zavora 360 platform (zavora360.royalbengal.ai). The plugin only embeds the popup link — no voice processing runs on your WordPress server.

Yes — in your Zavora 360 dashboard, not in WordPress. The dashboard has a Knowledge Base section where you can add information about your business, services, FAQs, etc. The agent uses that to answer questions.

The plugin itself stores no visitor data. When a visitor interacts with the Virtual Receptionist, that interaction is governed by the Zavora 360 privacy policy . For GDPR compliance, mention Virtual Receptionist usage in your own privacy policy and consider a cookie/consent banner if you’re in the EU.

Yes — use the shortcode [zavora_360] in any page or post. Optional attributes: label , color , size . Example: [zavora_360 label="Call us now" color="#dc2626" size="large"] .

Cart Recovery runs on a scheduled background task (about every 10 minutes). As of v1.3.4 the plugin self-heals: at the end of any request to your site (an admin page, a visitor, a bot, an uptime monitor) it will run an overdue scan in the background, so on any normally-trafficked store recovery works automatically once you turn it on — no setup needed. The catch is that WordPress has no internal clock; it only runs when a request hits the site. On a brand-new or zero-traffic site with nobody visiting and nobody logged in, nothing can trigger the scan, and you will see an admin notice saying so. The fix for that case is a real server cron: add define('DISABLE_WP_CRON', true); to wp-config.php (above the “stop editing” line), then have your host call https://YOURSITE/wp-cron.php?doing_wp_cron every 5 minutes. On cPanel/Plesk use the Cron Jobs tool; on a raw server add */5 * * * * curl -s "https://YOURSITE/wp-cron.php?doing_wp_cron" >/dev/null 2>&1 to your crontab; on managed WordPress hosts (Kinsta, WP Engine, SiteGround, Cloudways) use their built-in cron manager or contact support; and if you can install plugins but not edit server cron, a free external service such as cron-job.org can hit that URL on a schedule. This is standard production hygiene for any WordPress site that depends on scheduled tasks, not specific to this plugin.