Skip to content

EP Concierge

EP Concierge puts a floating AI chat bubble on the public side of a PageMotor site. It knows the business (services, prices, and FAQs from its settings, plus live booking data), answers visitor questions, points people to the booking page, and captures enquiries which are emailed to the owner. It is the only bot in the EP AI line-up that your site’s visitors actually talk to.

Published by ElmsPark Studio.

A visitor clicks the chat bubble, asks a question, and gets an answer grounded in what you have told the assistant about your business. Behind the scenes:

  1. The visitor’s message (plus recent conversation history) goes to your configured LLM provider with a system prompt built from your persona, your knowledge text, your site’s own pages and any documents you uploaded, and live booking data.
  2. If the visitor wants to be contacted or to make a booking enquiry, the assistant collects a name, a way to reach them, and their message, then calls its capture enquiry tool. The enquiry is emailed to the owner. If live chat is on and someone is available, it can instead fetch a real person into the chat (see Live chat below).
  3. The reply comes back to the chat bubble. Conversations can be logged for the owner to review, with automatic retention-based deletion.

Read-only by design. The assistant reads, it never changes anything: it cannot edit pages, run queries, or touch files. What it reads is your Knowledge box, the text of your live public pages (from 1.6.0; pages behind a login or marked private are never read), the documents you upload, and live booking data: if EP Booking or EP Boarding is installed, current prices, services, and the weekly availability schedule are read into the system prompt automatically, so the assistant quotes real prices and real opening days rather than guessing.

Guardrails are built into the prompt: the assistant is instructed to answer only about this business, never to invent prices, dates, availability, or policies, and to state availability exactly as the live schedule gives it.

ProviderModels
OpenAIGPT-4o mini (fast, economical), GPT-4o, GPT-4.1 mini
DeepSeekDeepSeek Chat
Kimi (Moonshot AI)Kimi K2.6 (fast, economical), Kimi K3
Anthropic (Claude)Claude Haiku 5.5 (fast, economical), Claude Sonnet 5.5

You bring your own API key, billed per message to your own provider account. The model list in settings narrows to the chosen provider, and the backend validates the pairing too, so a provider/model mismatch can never break the chat. Cheaper, faster models (mini, Haiku) are ideal for a website chat.

  • PageMotor 0.11.5 or later
  • An API key from OpenAI, DeepSeek, Kimi, or Anthropic
  • EP Email (recommended). Enquiries are sent through EP Email when it is active, so they are deliverable and logged; without it the plugin falls back to PHP mail().
  • EP Booking / EP Boarding (optional). When present, live prices and the weekly availability schedule are fed to the assistant automatically.
  1. ep-concierge.zip comes with an EP Suite licence, and ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.
  2. Upload via Plugins → Manage Plugins. Activate.
  3. Open Plugin Settings → EP Concierge, set the provider and API key, tick Enable chat assistant, and fill in the knowledge box.

The chat bubble only appears once the plugin is enabled and an API key is saved.

  • Enable chat assistant. Master switch. Shows or hides the bubble for visitors.
  • AI provider. OpenAI, DeepSeek, or Anthropic (Claude). The Model list updates to match.
  • API key. Your key for the chosen provider (OpenAI sk-..., DeepSeek, or Anthropic sk-ant-...).
  • Model. Which model answers the chat. Only models for the selected provider are shown.
  • Assistant name. The name shown in the chat header.
  • Opening greeting. The first message a visitor sees when they open the chat.
  • Input placeholder. The hint text in the message box.
  • Accent colour. Optional hex colour so the bubble matches your brand.
  • Language the assistant answers in. (1.8.0) The visitor’s own language (the default): a visitor who writes in French gets French, one who writes in English gets English, and when it cannot tell it uses your site’s language (Site Settings). Or pick one language for it to always use. Prices, product names and page addresses are never translated.
  • Send enquiries to. Where captured enquiries are emailed. Defaults to your booking admin email.
  • Persona / role. Who the assistant is — its tone and manner. Five presets (friendly, warm and reassuring, professional, knowledgeable specialist, upbeat and playful) plus Custom, which uses the box below.
  • Custom persona. Your own persona text, used only when Persona is set to Custom.
  • Knowledge. Everything the assistant should know: services, FAQs, policies, prices. This is what it knows, as opposed to who it is. Live booking prices are added automatically. If the Knowledge box and a page disagree, the Knowledge box wins.
  • Answer from my site’s pages. On by default (1.6.0). The assistant reads the text of your live public pages and re-reads them when one changes. Pages behind a login or marked private are never read. The panel lists the pages it reads.
  • Documents. Add a price list, menu, policy or FAQ: PDF, Word (.docx), text, CSV or HTML, up to 10 MB, up to 25 documents. Only the text is kept. A PDF is read by your AI provider when it can (Anthropic or OpenAI, on your key). Anything in a document can be repeated to visitors, so only add what you would put on your website.
  • Products and current offers. (1.8.0) Under Products & Offers, add each product as a row: name, price as it should be quoted, the current offer, its page link, and the date the offer ends. Only the name is needed. The assistant quotes prices and offers exactly as written, sends buyers to the product’s page, and never makes up a discount, a deadline or a price. On the end date it stops mentioning that offer by itself.
  • Price check. (1.8.0) On by default. Every price and percentage in a reply must appear in what the assistant was given (your products, the Knowledge box, pages, documents, live booking prices) or in what the visitor wrote. A reply with any other figure is rewritten once without it, and a sentence that still carries it is removed. It can cost one extra AI call on the rare reply it catches.
  • Privacy note. An optional short line shown beneath the chat input (for example “Chats may be saved so we can follow up”). Recommended whenever logging is on.
  • Keep conversation logs for (days). Retention is the single logging control: 0 turns logging off entirely; any other number logs conversations and auto-deletes them after that many days. Default 90.

Below the settings, a Recent conversations panel shows the last 25 logged chats — expandable transcripts, each marked when it produced an enquiry, each with a Delete this conversation button.

When a visitor asks to talk to a person, the assistant can fetch you into the same chat.

  1. Under Live Chat, choose when you are offered: When I have the Live chats screen open, or During my hours (days and times, in your site’s time zone).
  2. Click Open Live chats (or go to yoursite.com/?epc_live=1 while signed in). Keep it open on your phone or computer, and tap Turn on sound and alerts once.
  3. When someone asks for you, the screen plays a sound, shows a notification and puts a count in the tab. You are also emailed. With EP Video 0.21.2 or later, its iMessage number set and its Mac helper running, you get an iMessage too.
  4. Click Take over and reply. The visitor sees your messages within a few seconds, with your name on them. Hand back to the assistant or End chat when you are done.

If nobody takes over within the wait time (2 minutes unless you change it), the assistant apologises and takes the visitor’s details instead. No AI is used while you have the chat. With conversation logging off, nothing of a live chat is kept once it ends. Live chat is off until you switch it on.

With EP Lead Source active, an enquiry taken in the chat carries the visitor’s source like a form enquiry does: a Lead source line in the enquiry email (the channel, campaign, first page and the advert’s utm_content), and the lead in EP Lead Source’s report and its lead.created event. EP Lead Source decides what may be kept, under its own consent rules: an advert’s click ID is only kept when the visitor allowed marketing cookies (or you chose “Always, without asking” there). Without EP Lead Source nothing changes. The enquiry marker line can carry it too, as {lead_source}.

An AI assistant connected to your site over MCP (with an admin token) gets five tools: EP_Concierge__get-setup, set-setup, set-products, add-document and remove-document. It can read and change the assistant’s name and greeting, persona, Knowledge text, banned words, products and offers, documents, answer language, price check and live-chat hours.

  • Every value is checked first; if any is wrong, nothing is saved and the reply says why.
  • Each change is written to your site’s audit log, and the latest are listed under Products & Offers as Changes made by an AI assistant, with who made them.
  • The API key, the provider and model, switching the chat on, where enquiries are emailed, conversation logging and the daily caps stay yours, on the settings screen.

The plugin is built for data minimisation:

  • No IP addresses are stored with conversation logs.
  • Retention is automatic. Logged chats are purged after the configured number of days; setting retention to 0 disables logging entirely.
  • Right to erasure. Any individual conversation can be deleted from the settings page, which removes it from the database immediately.
  • Privacy note. The optional line under the chat input tells visitors their conversation may be stored. Mention chat logging in your privacy policy when logging is on.
  • Same-origin only. The chat endpoint rejects requests whose Origin or Referer does not match the site.
  • CSRF protected. A frontend token is required on every chat request.
  • Rate limited. 25 messages per 10 minutes per visitor IP, protecting your API key (and your bill) from spam. Rate-limited visitors are asked to wait rather than shown an error.
  • {prefix}ep_concierge_chats — logged conversations: session id, timestamps, message count, enquiry flag, transcript JSON. Created on first use; only exists when logging is on.
  • {prefix}ep_concierge_sources — the text the assistant reads (1.6.0): a cached copy of each public page, and each uploaded document’s text.
  • {prefix}ep_concierge_live and {prefix}ep_concierge_live_msgs — live chats with a person (1.7.0): each chat’s state and the conversation so far, and the messages sent while it was live.

Check both conditions: Enable chat assistant is ticked and an API key is saved. The bubble is hidden unless both are true.

On a site built from standalone HTML pages (every site built by Page), the bubble needs version 1.4.0 or later. After updating, open the site’s admin once so existing pages pick it up.

“The assistant says it is not available right now”

Section titled ““The assistant says it is not available right now””

Same two conditions checked server-side. If both are set, the API key may be rejected by the provider — check it matches the selected provider (Anthropic keys start sk-ant-, OpenAI keys start sk-).

“Visitors get ‘Please reload the page and try again’”

Section titled ““Visitors get ‘Please reload the page and try again’””

The CSRF token has expired or the page was cached without one. A reload fixes it. If it persists behind an aggressive page cache, exclude the page from caching cookies.

Check Send enquiries to holds a valid address (or that your booking admin email is set). If EP Email is installed, check its delivery log; if not, delivery depends on your host’s PHP mail(), which is unreliable — install EP Email.

“The assistant quotes wrong opening days or prices”

Section titled ““The assistant quotes wrong opening days or prices””

Live schedule and prices come from EP Booking / EP Boarding when installed. Otherwise the assistant answers from the Knowledge box, your pages and your documents, and the Knowledge box wins when they disagree, so check it does not hold old hours or prices.

Retention is set to 0, which is the off switch. Set a number of days to start logging.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.

A security update. Please install it.

  • Fetch a person has its own limits. Asking for a person now allows three requests an hour per visitor and your daily enquiry limit for the site, and only the first waiting chat alerts you; others join the queue you already see.

A security update. Please install it.

  • The chat assistant no longer reads members-only text. When it learns your site’s pages it now skips anything any of your EP plugins marks as private, and it leaves out the inside of members-only and sign-in gates on ordinary pages. Before, a visitor could ask the assistant about content they had not paid for.
  • Your products and current offers. A new Products & Offers section takes each product’s name, price, current offer, page link and the date the offer ends. The assistant quotes prices and offers exactly as you wrote them, sends buyers to the product’s page, and never makes up a discount, a deadline or a price. On the offer’s end date it stops mentioning that offer by itself.
  • Price check. Every price and percentage in a reply must be one the assistant was given: in your products, the Knowledge box, your pages, documents and live booking prices, or in what the visitor wrote. If a reply carries any other figure, it is rewritten once without it, and a sentence that still carries it is removed. On by default; you can switch it off.
  • Answers in the visitor’s own language. A visitor who writes in French gets French, one who writes in English gets English. When it cannot tell, it uses your site’s language. You can choose one language for it to always use instead. The few fixed lines visitors see (the default greeting, “nobody is free right now” and so on) follow that language too, in German, Spanish, French, Italian, Dutch and Portuguese.
  • The settings screen in your language. EP Concierge’s settings now follow the EP Suite language switcher: German, Spanish, French, Italian, Dutch and Portuguese.
  • Where a chat lead came from. With EP Lead Source active, a chat enquiry now carries the visitor’s source like a form enquiry does: the source, campaign, landing page and advert in the enquiry email, and the lead in EP Lead Source’s report. EP Lead Source’s consent rules apply unchanged: an advert’s click ID is only kept when the visitor allowed marketing cookies. Without EP Lead Source nothing changes.
  • Set up by your AI assistant. An AI assistant connected to your site (over MCP) can read and change the assistant’s name and greeting, persona, Knowledge text, banned words, products and offers, documents, language and live-chat hours. Every value is checked before anything is saved, every change is logged, and the latest are listed for you under Products & Offers. The API key, switching the chat on, where enquiries go and conversation logging stay yours, on the settings screen.
  • Live chat with a real person. When a visitor asks to talk to someone, the assistant can fetch you into the same chat. You answer from the new Live chats screen, on your phone or computer; the visitor sees your replies within a few seconds, with your name on them. Hand back to the assistant, or end the chat, whenever you like.
  • You choose when you are offered: only while you have the Live chats screen open, or during set days and hours. If nobody takes over within the wait time (2 minutes unless you change it), the assistant apologises and takes the visitor’s details instead, as before.
  • You are told straight away: by email, by a sound, a notification and a count in the tab on the Live chats screen, and by iMessage if you also use EP Video with its Mac helper and its iMessage number set.
  • While you have the chat, no AI is used, so it costs nothing. With conversation logging off, nothing of a live chat is kept once it ends.
  • It is off until you switch it on under Live Chat.
  • The assistant reads your website. It now answers from the text of your live public pages as well as the Knowledge box, so its answers match your site: change a price on a page and the assistant knows. Pages behind a login, or marked private, are never read. It re-reads your pages when you change one. If the Knowledge box and a page disagree, the Knowledge box wins. It is on by default; switch it off under Site Pages & Documents.
  • Add documents for it to read. Upload a price list, menu, policy or FAQ as a PDF, Word (.docx), text, CSV or HTML file, up to 10 MB. Only the text is kept, not the file, and you can remove a document at any time. Anything in a document can be repeated to visitors, so only add what you would put on your website. A PDF is read by your AI provider when it can (Anthropic or OpenAI, on your key); otherwise the plugin reads it itself, and asks for a Word or text copy if it cannot.
  • It can point visitors to the right page, by its address, when a page answers their question.
  • On a large site, each question is given the passages of your pages and documents that best match it, so the cost per message stays in check. On Anthropic, a small site’s text is cached between messages, which makes repeat messages cheaper.
  • Reply to a chat enquiry and it goes straight to the visitor. The enquiry email now uses the visitor’s own email address as its reply address, so pressing Reply answers them directly. If the visitor gave no email (a phone number only), your usual reply address stays.
  • The chat button icons show properly on every theme. On some site designs, the theme’s own button styling squeezed the chat bubble’s icon to a sliver, hid the send arrow and drew a stray line above the close button. The chat widget now keeps its own button styling, whatever the theme does.
  • A chat enquiry that fails to send is no longer reported as sent. If your email service turned an enquiry down (a refused address, a sending setting that needs fixing), the assistant still told the visitor it had been passed on, and nobody received it. Now the assistant says it could not send, offers your fallback contact or the contact page, and the conversation is not counted as an enquiry. The reason is written to your server’s error log.
  • Page buttons can open the chat on a topic, and the assistant knows it. Give any button or link on your pages a data-bot-greeting attribute (for example “Ask me about recall training”) and clicking it opens the chat with that greeting. The assistant is told which greeting the visitor saw, so a first question such as “how long does it take?” is answered about the right thing. You can switch this off under Chat Assistant.
  • Words the assistant must never use. List them under Persona & Knowledge. The assistant avoids them, even when denying something; if a reply slips, it is rewritten once, and any sentence that still carries the word is removed.
  • Extra enquiry details. Name extra details the assistant can pass on with an enquiry (such as a pet’s name or a breed). They appear in the enquiry email.
  • Enquiry marker line, for your own systems (advanced). After an enquiry is sent, the assistant’s reply can carry a line you design, filled in with the enquiry’s details, for tools that read your saved conversations. Visitors never see it.
  • Choose where the chat bubble shows. A new Where It Shows section: every page, every page except a list, or only listed pages, and whether standalone HTML pages (every page built by Page, or a hand-made dashboard) get the bubble.
  • Nothing changes after updating until you use the new settings.
  • The chat now appears on sites built from standalone HTML pages, including every site built by Page. Until now the chat bubble never showed on those pages, even with the assistant switched on. Pages built before this update pick it up automatically the first time anyone opens the site’s admin or a normal themed page after updating.
  • Switching the assistant off removes it from those pages too, and switching it back on restores it. Saving the settings is enough.
  • Fixes “Invalid request origin” on sites served from a non-standard port. Every chat message was refused on such a site (typically a local or test copy). Live sites on the usual port were not affected.

With Anthropic as the provider, the assistant now uses the Claude 5.5 models: Haiku 5.5, at about a tenth of Haiku 4.5’s price per token, or Sonnet 5.5. A site that had picked an older Claude model moves to its 5.5 successor automatically.

  • The chat copes better when the AI service is busy. When OpenAI, Claude, DeepSeek or Kimi says it is overloaded or limiting requests, the assistant now tries up to three times instead of two, and waits as long as the service asks (a few seconds at most, since a visitor is waiting) instead of a fixed two seconds.
  • No more pointless second try when your AI account is out of credit. The assistant now gives up at once, so the visitor sees your contact details straight away.
  • Nothing to do after updating. What visitors see when the assistant cannot answer is unchanged.
  • Safer links in chat replies.
  • Saved conversations are better protected. Conversations already in progress simply start a new saved conversation.
  • A limit on enquiry emails. The assistant limits how many enquiry emails it sends you, adjustable under “Most enquiry emails per day”.
  • New setting for sites behind Cloudflare or a proxy: “Visitor address comes from” lets the per-visitor limits see each visitor’s own address, so one busy visitor cannot pause the chat for everyone.
  • Lighter public pages. The status cards and saved conversations are only loaded when an admin opens the EP Concierge screen.
  • Nothing to do after updating. Conversations already in progress when you update simply start a new saved conversation.
  • Security fix: your AI provider key is now stored encrypted and shown as a password field. A key saved earlier keeps working and is moved across automatically.
  • New: a daily limit for the whole site. Set “Most chat messages per day” (500 if left blank) so the chat can never run up more than you expect. When it is reached, visitors are pointed to your contact details until the next day.
  • Fairer, firmer limits per visitor. The 25-messages-in-10-minutes limit is now counted exactly, even when lots of people chat at once, and people on modern (IPv6) connections can no longer get round it by changing address.
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Section status. Each settings section shows whether that feature is switched on. On a site that also runs an older EP plugin, the section shows its plain title instead.
  • Removes a function call that PHP 8.5 reports as deprecated, so it no longer fills your error log.
  • Fixes a doubled cache-busting tag on its stylesheet and scripts. On PageMotor 0.11 and later the page asked for each file with two version tags on the end of its address (?v=…?v=…), because the core had started adding its own tag and the plugin was still adding one too. The files loaded correctly, so nothing was visibly broken; the addresses were just malformed and every cache saw a longer key than it needed. The plugin now leaves the tag to the core on 0.11 and later, and still adds its own on older cores, where nothing else would.
  • No change to what these files do.
  • Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
  • Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
  • Visitors who were not signed in were never affected, on any version.
  • There is nothing to reconfigure, and nothing else changed.
  • Also fixes the plugin never appearing on your Updates screen. PageMotor only offers updates for a plugin that tells it where to look, and this one never did, so it has been invisible to the update check since release. That is corrected here, but the fix cannot deliver itself: to get onto this version you need to upload it once by hand. After that, updates arrive normally.