Attendant is an AI-powered site search chatbot that helps your visitors find content on your website. When someone asks a question in plain language, Attendant searches your own posts, pages, products, and listings, then answers right in the chat — so visitors reach the right page without digging through menus. It combines conversational search with knowledge Q&A in one chat widget.
Replies stay short and scannable: the assistant links to matching pages as clickable buttons, offers tappable choices when the next step is a selection, and guides the visitor with one question at a time when a search comes up empty. The conversation is remembered in the visitor’s own browser so it survives page changes and refreshes. When the assistant genuinely cannot help, you can optionally let it offer a callback and email the request to your team.
Mode 1 — Smart Search (for sites with listings)
A visitor says: “Find me apartments in Lisbon under €500K with 3 bedrooms” Attendant extracts the parameters, searches your WordPress database, and answers in the chat with clickable buttons to the matching listings.
Mode 2 — Knowledge Q&A (for all sites)
A visitor says: “What is your return policy?” Attendant searches your indexed content and answers the question with source citations.
The AI automatically picks the right mode based on what the visitor is asking.
This plugin connects to the OpenAI API. This is required for the AI chat features: OpenAI 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 OpenAI. If you enable the optional Semantic Q&A mode, the text of your selected content is also sent to OpenAI 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 OpenAI API key and turn the chat widget on — both are off by default.
The service is provided by OpenAI, L.L.C. Please review their policies:
Three 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.
You are responsible for disclosing these features in your own privacy policy if you enable them.