

Settings page: choose your AI provider and add your key
Attendant adds a free AI chatbot to your WordPress site. Visitors ask questions in the chat, and it answers using your own posts, pages, and products, with buttons that take them straight to the right page. It is a chatbot, an AI assistant, and a smart site search in one chat widget.
It runs on Google Gemini’s free plan. One free key, no credit card, ever. Prefer OpenAI, the company behind ChatGPT? That works too.
This plugin connects to the AI provider you choose in Settings: Google Gemini (recommended, free tier) or OpenAI. This is required for the AI chat features: the provider turns a visitor’s natural-language question into a structured search of your own content and writes the answer.
What is sent, and when: only when a visitor sends a chat message, the plugin sends that message text plus the titles and short excerpts of the matching content from your own site to your chosen provider. If you enable the optional Semantic Q&A mode, the text of your selected content is also sent to that provider during indexing to generate embeddings. Your API key, your full database, and IP addresses are never sent. Nothing is sent until you add your own API key and turn the chat widget on. Both are off by default. The plugin only ever talks to the one provider you configure.
Note on Google’s free tier: Google’s terms allow content submitted on the free tier to be used to improve their services. Attendant only sends your public website content and visitor chat messages. Review Google’s terms if that matters for your site.
Google Gemini API, provided by Google LLC:
OpenAI API, provided by OpenAI, L.L.C.:
Slack, provided by Slack Technologies, LLC (a Salesforce company). Only used if you connect Slack for the live handover, which is off by default and does nothing until you finish the setup wizard.
What is sent, and when: only when a visitor asks to speak to a person, the plugin sends the recent conversation (their messages and the assistant’s replies) plus a short summary of what they need to the Slack channel you chose. While that handover is open, each new message the visitor sends is posted to the same Slack thread, and each reply your team writes there is sent back to the visitor’s chat. Nothing is sent to Slack at any other time. Your Slack credentials are stored encrypted on your own site and are never sent anywhere except to Slack itself.
Four features can handle personal data. All are OFF by default and only do anything once you, the site owner, turn them on.
Conversation history (in the visitor’s browser). The chat keeps a copy of the current conversation in the visitor’s own browser using localStorage so it survives page changes and refreshes. This data never leaves the visitor’s device except as the normal chat messages already described above. It is not stored on your server or in your database. The visitor can clear it at any time with the “New chat” button or by clearing their browser storage.
Conversation logging to files (optional, off by default). When you enable file logging in Settings, the plugin writes each exchange (the visitor’s message and the assistant’s reply) to a dated log file in a protected folder inside your uploads directory, so you can review how the assistant is used. IP addresses are never stored. Session identifiers are stored only as short one-way hashes used to group a single conversation. Logs are kept for 30 days and then deleted automatically, and only a logged-in administrator can download them. No conversation data is sent anywhere by this feature; the files stay on your server.
Callback / lead capture (optional, off by default). When you enable lead capture and a visitor explicitly agrees to be contacted, the plugin collects the email address the visitor provides (and, if they choose, a phone number and a preferred time) and emails that request to the address you configure, using your site’s normal email. It is rate-limited to one request per conversation and a daily maximum. This information is handled by whatever email service your WordPress site already uses; the plugin does not store it in a database or send it to any third party of its own.
Live handover to Slack (optional, off by default). When a visitor asks to speak to a person, the conversation is sent to your Slack workspace as described under External services above, and stays readable by whoever is in that Slack channel. The plugin keeps the link between a chat and its Slack thread on your own server for 24 hours and then discards it. IP addresses are never sent. If you use this feature, your visitors’ messages are handled by Slack under Slack’s own privacy policy, and you should say so in your privacy policy.
You are responsible for disclosing these features in your own privacy policy if you enable them.