Snakk AI Chat and Voice

Snakk AI Chat and Voice connects your website to the existing Snakk service. Choose one AI chat widget or one browser voice widget. No page-builder add-on is required. The plugin uses the standard WordPress frontend hooks used by classic themes, block themes and Elementor pages.

• A standard Settings page with a public agent ID, widget selection and position.
• Disabled until an administrator enables it.
• A local load button: no Snakk requests before a visitor chooses to load the service.
• Voice calls require a separate click and browser microphone permission.
• No API secrets, arbitrary scripts, analytics or WordPress visitor records are stored by the plugin.
• Translation-ready interface, with language packs managed through WordPress.org.

The plugin is free and has no local feature paywall or expiry. A Snakk account and configured agent are required. Snakk subscriptions and usage may be paid; see current service pricing. Website hosting is separate. Browser voice does not provision telephone numbers or enable AI telephony.

Chat and browser voice currently use separate Snakk runtimes. Choose one per site; this release does not combine both in a single panel. Chat appearance and its final position are configured in Snakk. The plugin position setting controls the initial load button and the browser voice button.

External service and privacy

Service: Snakk, operated through https://platform.snakk.ai/ and https://api.snakk.ai/.

Purpose: provide configured AI chat or browser voice conversations using your Snakk account. This is a service connector, not a standalone AI backend.

After the visitor clicks Load chat or Load voice assistant, the plugin loads one service script from https://platform.snakk.ai/chat-embed.js or https://platform.snakk.ai/embed.js. Requests reveal IP address and standard HTTP metadata to the service. Chat fetches configuration and may create a visitor identifier in localStorage. Opening chat can create a service session and send public agent ID, visitor ID, current page URL, referrer and browser information. Messages and contact details are transmitted when submitted. Avoid putting sensitive values in page URLs.

Voice loads the LiveKit client from https://platform.snakk.ai/vendor/livekit-client-2.22.3.umd.min.js when the voice button is used. It requests a session from api.snakk.ai, then connects to the LiveKit endpoint returned by the service. Microphone audio is sent only after user action and permission. Service-side providers and processing are governed by your Snakk agreement and privacy policy. No microphone access, conversation session or AI request is initiated by the local load button itself.

Review Snakk terms and Snakk privacy policy. Explain this processing in your own site’s privacy notice and configure any consent-management requirements for your site. The load control is not a complete consent-management platform.

Deactivation stops plugin loading on subsequent uncached page views and retains settings. Deletion removes this plugin’s settings on all sites in a multisite network. Existing open browser tabs, browser storage and data in Snakk are not erased. Manage service records through Snakk. Purge caches after enabling, changing, deactivating or deleting the plugin.