Use this guide with any AI assistant
Download it as a prompt file, paste it into Claude, ChatGPT, Gemini or any LLM, and it will walk you through every step interactively.
Chatbots for PageMotor: what ElmsPark has built
Six shipped plugins that put AI to work on a PageMotor site, plus one route that needs no install at all. This page tells you which one fits the job you have in mind.
“Chatbot” covers a lot of ground. A bubble that answers your visitors’ questions is a different animal from a box that answers your own how-to questions, different again from an assistant that can actually edit your site, and different again from AI that quietly works your inbox. ElmsPark has built all four kinds for PageMotor. Here is the line-up, what each one actually does, and where to read more.
▶ The whole line-up in 5 minutes 59 seconds, narrated, with captions — and the one line that decides between the two that look most alike.
Read the narration instead
The shape of it. Six shipped plugins that put AI to work on a PageMotor site, plus one route that needs no install at all — and how to tell which one fits the job you have in mind.
Four different animals. A bubble that answers your visitors is a different thing from a box that answers your how-to questions; different again from an assistant that can edit your site; different again from AI working your inbox. They look alike from the outside and are nothing alike underneath. Pick by the job, not by the word.
EP Concierge is the visitor-facing one: a floating bubble on the public site that knows the business from its settings plus live booking data, answers questions, points people at the booking page, and emails the owner when a conversation becomes a lead. The only bot your site's public talks to, and read-only by design — it knows only what you give it.
EP Support points the other way, at you. A chat panel inside the Admin with a curated knowledge base covering the whole EP Suite. It can see which plugins you have installed, so it tailors answers rather than guessing, and it gives code samples and paste-an-error debugging. The documentation site, but talk-to-able. It never appears to visitors.
EP Assistant is the deep one: a chat interface wired to real server-side tools, so you run the site in plain English. Write a page, check today's enquiries, send a follow-up, update the brand colours. Because they are real tools, they have real gates — file access sandboxed to the site root, SQL on whitelisted tables with an automatic backup before any write, and every tool call logged to an audit table.
The line that decides it. EP Support answers questions. EP Assistant takes actions. That is the whole distinction, and it is the one people get wrong when choosing. If you want a bot that can safely change the site, it is EP Assistant — which needs VPS hosting rather than shared, plus EP Email for its send-email tool.
EP Studio Assistant answers your business data in plain English: how is revenue this month, who is about to churn, who has not signed a waiver before tomorrow's class. Deliberately read-only — a fixed allowlist of query tools and nothing else. The loop runs on your own server, so your key never reaches the browser and your data never leaves except as the answer.
Or no install at all. If you already have a Claude account, free plan included, you need neither a plugin nor an API key. PageMotor speaks Claude's connector language natively: add your site as a custom connector, sign in as your own admin, and ask. Read-only, about five minutes, and it has its own walkthrough.
Drafts, and a bouncer. EP Email AI Reply drafts a reply to a contact-form submission in the editor, answering what was actually asked — you review, edit and send, and a human presses send always. EP Email AI Triage classifies what survives the free heuristics as real, spam, hostile or unclear. Confirmed spam gets the same friendly thank-you as everyone else, so spammers cannot tune around it, and it fails open: a classifier error or timeout delivers the message with a review prefix rather than losing it.
Your key, your server. Every one uses your own API key with the provider you choose — no metered middleman, no per-message fee. Keys stay server-side and never reach the browser. Read-only bots get a fixed allowlist; writing bots are sandboxed, backed up first and audit-logged. And the AI features degrade gracefully, so a missing or broken bundle can never take the site down.
Pick by job
| You want to… | Reach for |
|---|---|
| Put an AI chat bubble on the public site that answers visitor questions and captures leads | EP Concierge |
| Ask how-to questions about your PageMotor site and its plugins, inside the Admin | EP Support |
| Manage the whole site by conversation: write pages, change styling, check enquiries | EP Assistant |
| Ask your business data questions in plain English (revenue, churn, schedule) | EP Studio Assistant |
| The same business Q&A, but with zero install, on your own Claude account, free plan included | The Claude connector route |
| Get AI-drafted replies to contact-form enquiries, ready to review and send | EP Email AI Reply |
| Keep intent-aware spam out of your inbox without blocking real customers | EP Email AI Triage |
EP Concierge: the visitor-facing chat bubble
The classic website chatbot, done properly. A floating chat bubble on the public site that knows the business (services, prices and FAQs from its settings, plus live booking data), answers visitor questions, points people at the booking page, and captures enquiries.
- Visitor-facing. The only bot in this line-up your site’s public actually talks to.
- Knows only what you give it. Read-only by design: it has no access to the site or its data beyond the knowledge you configure for it.
- Captures enquiries. When a conversation turns into a lead, the details are emailed to the owner, and conversations can be logged for review.
- Three providers. Anthropic (Claude), OpenAI or DeepSeek, on your own key.
See it working on a live client site: thesighthoundguy.com (the chat button). Currently at v1.3.0. Full docs: EP Concierge.
EP Support: the support chatbot
A floating chat panel inside the PageMotor Admin, for you as the site owner. Ask it how to do something (“How do I set up Stripe in EP Booking?”) and it answers in context, with a curated knowledge base covering every EP Suite plugin built in.
- Admin-only. It never appears to site visitors.
- Aware of your site. It can see which plugins you have installed and tailors its answers.
- Practical output. Code samples for customisations, and paste-an-error debugging help.
Think of it as the documentation site, but talk-to-able. Currently at v1.1.20. Full docs: EP Support.
EP Assistant: manage the site by conversation
This is the deep one. EP Assistant puts a chat interface in the Admin and wires it to real server-side tools, so the site owner can run their site in plain English. Write a new page. Check today’s enquiries. Send a follow-up email. Update the brand colours. All through conversation.
- Real tools, with safety gates. File read/write is sandboxed to the site root; SQL runs against a whitelisted set of tables with an automatic backup before any write; every tool call is logged to an audit table.
- It can restyle the site. CSS recompiles and theme imports are tools the model can call.
- Nine LLM providers. Claude, GPT, Gemini, Mistral, DeepSeek, Groq, Grok, Together and Fireworks, swappable in a dropdown. Bring whichever key suits your budget.
Not a support bot. EP Support answers questions; EP Assistant takes actions. If you want a bot that can safely change the site, this is the one.
Needs VPS hosting rather than shared, and EP Email for its send-email tool. Currently at v1.0.9. Full docs: EP Assistant.
EP Studio Assistant: ask your business data
An “Ask” box inside the Admin for sites running the EP studio suite. The owner types “how is revenue this month”, “who is about to churn”, or “who has not signed a waiver before tomorrow’s class”, and Claude answers from the studio’s live data.
- Deliberately read-only. The model is handed a fixed allowlist of query tools (dashboard overview, members at risk, schedule, revenue, passes, waivers, payroll) and cannot call anything else. It shows you what is happening and points you at the right screen to act.
- Server-side loop. The Anthropic tool-use loop runs on your server; your API key is stored server-side and never sent to the browser, and your data never leaves the server except as the model’s answer.
Currently at v1.0.3. Full docs: EP Studio Assistant.
The no-install route: your own Claude account
If you already have a Claude account, free plan included, you do not need a plugin or an API key to talk to your site’s data. PageMotor speaks Claude’s connector language natively, so you add your site as a custom connector in claude.ai, sign in as your own admin, and ask away. Read-only, five minutes to set up.
That route has its own walkthrough: Ask your studio with Claude.
EP Email AI Reply: drafts, not autoresponders
An extension to EP Email’s contact-form inbox. Open a submission, click Draft reply with AI, and a proposed reply appears in the editor: professional tone, answering what the customer actually asked. You review, edit and send. The reply goes out through EP Email’s normal delivery, so it is signed, tracked and deliverable.
A human presses send, always. Currently at v1.0.6. Full docs: EP Email AI Reply.
EP Email AI Triage: the bouncer
Not a chatbot you talk to, but the same machinery pointed at your inbox. Every contact-form submission that survives EP Email’s free heuristics (honeypot, time trap, URL count, keyword filter, rate limit) is classified by an LLM as real, spam, hostile or unclear, with a confidence score, and a configurable decision matrix decides what happens next.
- Silent blocks. Confirmed spam gets the same friendly “thank you” as everyone else, so spammers cannot tune around the filter. Blocked messages sit in a quarantine you can audit.
- Fail-open. If the classifier errors or times out, the message is delivered with a
[REVIEW]prefix. A real enquiry is never lost to an API outage.
Currently at v0.1.9. Full docs: EP Email AI Triage.
How they are all built
A few principles run through the whole line-up, and they are the answer to the questions people usually ask next:
- Bring your own key. Every plugin uses your API key with your chosen provider. There is no metered middleman and no per-message fee to ElmsPark.
- Keys live server-side. API keys are stored on your server and never shipped to the browser.
- Least privilege by design. Where a bot only needs to read, it gets a fixed read-only allowlist. Where it can write, writes are sandboxed, backed up first and audit-logged.
- Fail safe. AI features degrade gracefully: triage fails open, and a missing or broken AI bundle can never take the site down.
Getting them
All six are EP Suite plugins, supplied directly by ElmsPark with a licence: see EP Suite plugins. Once installed, they update through your site’s own Updates screen via the ElmsPark update channel.