Yes — TalkativeWP temporarily stores chat session data on your WordPress server for functionality and performance purposes.

By default:

• Conversation history is stored as a JSON object (for active sessions).
• Data is saved using WordPress options or transients, depending on your setup.
• The plugin does not automatically store user names, phone numbers, or personal data unless you choose to capture them (e.g., with a webhook or Google Sheets integration).

We do not create database tables or expose user data publicly.

For full GDPR compliance, you may enable consent collection and configure data expiration settings. 

Currently, TalkativeWP requires an OpenAI Assistant connection to function. It doesn’t use any built-in rule-based responses or offline logic.

The AI assistant is responsible for generating all replies, so without a valid API key or OpenAI setup — the chat interface will load, but won’t respond to user inputs.

We may explore local fallback modes or manual flows in future versions. 

TalkativeWP is a smart chatbot plugin for WordPress that integrates with OpenAI’s Assistants API. It lets you add a conversational assistant to your website — one that can respond to user questions in real-time, guide visitors, collect leads, and provide helpful answers based on your configuration or connected content.

 It’s designed to be easy to use, fully customizable, and ready for multilingual (RTL/LTR) websites. 

Yes — TalkativeWP has full RTL support built in.

The plugin:

• Applies dir="rtl" when selected in settings
• Adjusts layout, message alignment, button positions and icon margins
• Uses CSS variables like --talkativewp-text-direction, --talkativewp-icon-margin, and others to flip UI elements

No extra configuration needed — just choose RTL in the plugin settings and the layout will adjust automatically. 

Yes! You can customize the floating button’s:

• Position (left or right)
• Color (via CSS variables)
• Font & size (inherited from your design settings)
• Icon (upload a custom image from the Persona tab)
• Text direction & alignment (based on RTL/LTR settings)

If you want full visual control, you can override the styles in your theme’s CSS or via the talkativewp-chat.css file in the plugin.
RTL-specific styles and margin behavior are already handled via :root variables. 

You can change the chat font from the Design tab in the plugin settings.

Once you choose a font family (like Heebo, Fredoka, etc.), the plugin dynamically loads the matching .ttf file and injects a @font-face CSS declaration, along with scoped font-family rules for all relevant elements (chat box, buttons, messages, etc.).

No manual CSS needed – just pick the font and save.

✅ The font file must exist in the /assets/fonts/{font-name} folder of the plugin. 

Yes — you can connect TalkativeWP to Make.com using a webhook module.

Just create a Make scenario with a Webhook trigger, copy the webhook URL, and paste it into the plugin’s “Webhook” field in settings.

From there, you can:

• Store leads in a database or Google Sheets
• Trigger email notifications or CRM updates
• Connect to tools like Slack, Airtable, Telegram, etc.

✅ Make sure the Make webhook is set to JSON and that the scenario is active. 

You can set a custom webhook URL in the plugin’s Settings panel under “Global Settings”.

Here’s how it works:

• When a user submits their name (and optionally phone number), the plugin triggers an HTTP POST request to your webhook.
• The payload is a JSON object containing:

{ "name": "User Name", "phone": "050-1234567", "chat": [ { "role": "user", "content": "Hi!" }, ... ]}

Make sure your webhook is ready to receive application/json payloads.

💡 At this time, only one webhook URL is supported. 

Yes — TalkativeWP supports lead forwarding to Google Sheets via webhook.

To set it up, you can use a custom Google Apps Script that listens for incoming POST requests and writes new rows to a spreadsheet.

We also offer a bonus snippet to format messages, phone numbers, and chat summaries when a new row is added — including sending email notifications from Google Sheets.

📘 See full example 

That depends on your license type.

TalkativeWP offers different license tiers — from single-site to multi-site usage.

You can view the available plans and terms on our Pricing Page. 

No — your settings, design preferences, and saved options will remain intact during updates.

TalkativeWP uses WordPress’s options API and doesn’t rely on custom database tables, so updates are safe.

However, we recommend backing up your site before major updates, especially if you’ve made manual code changes. 

1. Go to the License tab in the plugin settings.
2. Enter your License Key and Customer ID (you receive both upon purchase).
3. Click Save License, then optionally use Check License Status to verify activation.

What it means:

The assistant process was cancelled, failed, or expired during execution.

What to do:

• Retry the chat
• Try with a simpler or shorter message 

What it means:

OpenAI returned an empty result — likely a silent failure or a missing reply.

What to do:

• Try re-phrasing your message
• Recheck Assistant instructions or model settings in OpenAI
• Contact support if it happens repeatedly 

What it means:

The system couldn’t start the Assistant run — likely due to a misconfiguration.

What to do:

• Contact TalkativeWP to confirm the Assistant ID is valid

What it means:

The plugin failed to create a new conversation thread with OpenAI.

What to do:

• Ensure you have an active TalkativeWP license is valid
• Try re-saving your settings and refreshing the page 

What it means:

This is a generic fallback error. The system didn’t receive a valid response, and couldn’t determine why.

What to do:

• Try reloading the chat and starting over
• Enable debug mode to log detailed errors

What it means:

OpenAI’s servers took too long to respond, and the request timed out.

What to do:

• Try again in a moment — temporary delays are common during high load
• Consider switching to a lighter model (GPT-3.5 vs. GPT-4)
• If the issue persists, enable debug mode and check logs 

What it means:

Your Assistant is trying to use a model (e.g., GPT-4) that’s currently offline, restricted, or not available.

What to do:

• Try again in a few minutes
• Contact TalkativeWP support

What it means:

The request sent to OpenAI was malformed or incomplete — could be a bug or a content issue.

What to do:

• Try refreshing the page
• Make sure the user entered a message (no empty input)
• If the issue repeats, enable debug mode and contact support 

What it means:

Your API key may be missing, invalid, or expired.

What to do:

• Go to the plugin’s Settings tab
• Re-enter a valid OpenAI API key
• Save the settings and test again 

What it means:

Your site or OpenAI account has sent too many requests in a short time (rate limiting).

What to do:

• Wait 10–30 seconds and try again
• Avoid clicking “send” multiple times in quick succession
• If the issue repeats often, consider slowing down user access or contacting support 

What it means:

This usually happens when your OpenAI account has used up its quota or credits.

If your message doesn’t go through:

• Double-check your OpenAI API key and Assistant ID are correctly entered in the settings.
• Ensure the user name is filled (if required in settings).
• Confirm there’s no security plugin blocking the admin-ajax.php calls.
• Try enabling debug mode to view error logs in wp-content/debug.log. 

If the chat bubble isn’t visible, check:

• License Status: Make sure your license is active and valid.
• Bot Persona Settings: Verify you’ve defined a bot name and tooltip.
• Footer Hook: Your theme must include <?php wp_footer(); ?> right before the </body> tag.
• JavaScript Errors: Open your browser console (F12) and check for JS errors.
• CSS Visibility: Ensure no external CSS is hiding the bubble (e.g., display: none or z-index issues). 

You can translate the plugin using:

• Loco Translate (recommended)
• A .po/.mo file placed in the /languages folder of the plugin

The plugin includes translation-ready strings using the __() and _e() functions. 

Absolutely.

Loco Translate is the easiest way to:

• Translate plugin strings into any language
• Customize phrases in your own dialect
• Keep translations updated after plugin updates

Just install the plugin, select TalkativeWP, and start translating. 

The plugin supports full multilingual display — both RTL and LTR — and is compatible with most translation plugins like WPML and Polylang.

Currently, it doesn’t support dynamic switching of languages for the same assistant.

You can create multiple Assistants with different languages and switch them manually per site language.