EP Helpdesk
EP Helpdesk is a support desk that accepts structured tickets from your customers, asks Claude to draft a reply grounded in your docs, safety-checks the draft with a second model pass, then either sends the reply automatically or flags it for a human. Live demo at help.elmspark.com.
Published by ElmsPark Studio.
Overview
Section titled “Overview”- Structured intake form with four primary categories (installing, something broken, a question, billing), each revealing a short subcategory list and category-specific context fields (plugin, version, site URL, hosting, error text).
- Auto-generated subject line from category + plugin + site, editable before submit.
- Two-pass AI pipeline. A first model drafts the reply from the customer’s question and your knowledge base. A second pass checks the draft for accuracy. A clean pass auto-sends; a failed pass regenerates once; two failures flag for a human.
- Safety net keyword blocklist. Tickets mentioning billing, refund, cancel, invoice, chargeback, legal, GDPR, complaint, lawyer, or threat never auto-send. They always wait for a human.
- Rate cap. Max 20 auto-sends per hour across all tickets. Overflow queues for human review.
- 48-hour retract window. Admin can one-click retract an auto-sent reply and send an apology within 48 hours. After that, the ticket settles to a normal replied state.
- Resubmission detection. Tickets from the same email within four days that match a prior ticket by content flag for human review, so a customer never gets two different AI replies to the same question.
- Pushover mobile notifications. Admin gets a push on every flagged ticket, QA failure, resubmission, or auto-send. Deep-links to the specific ticket in admin.
- Tracking page. Customers look up their ticket with a reference code, no login.
- Mobile responsive submission form. Works one-handed on iPhone and Android.
- Light / dark mode toggle. Sun / moon button in the topbar. Follows the visitor’s OS preference on first visit, manual override persists in
localStorage. - Docs-link hint. Once a customer picks a known EP plugin in the intake form, a gold callout offers a direct link to that plugin’s docs page. Deflects tickets whose answer is one click away.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later
- EP Email for confirmation and reply delivery
- No AI plugin to install. AI drafts run through the ElmsPark AI service. The plugin connects by itself, with a credential issued for your site’s domain.
Installation
Section titled “Installation”- Install EP Email first.
ep-helpdesk.zipcomes with an EP Suite licence — ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- Upload via Plugins → Manage Plugins. Activate.
- Place the intake form on a page with the
[helpdesk-form]shortcode. - Create a tracking page at
/track/using the[helpdesk-status]shortcode.
Shortcodes
Section titled “Shortcodes”| Shortcode | Purpose |
|---|---|
[helpdesk-form] | Structured intake form with category chips, subcategory chips, contextual fields, and auto-subject. |
[helpdesk-status] | Ticket tracking page. Takes a reference code and an email. |
The intake form
Section titled “The intake form”The form has four primary categories, each revealing its own subcategory set:
| Primary | Subcategories |
|---|---|
| Installing or upgrading | New install / Upgrading existing / Activating a licence / Removing a plugin |
| Something isn’t working | Site fully down / A feature is broken / Cosmetic / Intermittent |
| I have a question | Plugin configuration / PageMotor core / Hosting / Design / Email / Payment / Other |
| Billing, licence, account | Invoice / Licence key / Subscription / Refund / Change plan / Cancel / Other |
The form collects name, email, subject (auto-filled), and a message. Depending on category, it also asks for plugin slug, plugin version, site URL, hosting, or error text.
When a customer picks a known EP plugin in the plugin-slug field, a gold callout appears below it with a one-click link to that plugin’s docs page (https://documentation.elmspark.com/plugins/<slug>/). The matcher tolerates variants: ep-email, ep email, EP_Email, EPEMAIL, and email all resolve to ep-email. Free-typed plugin names that do not resolve show no hint (no broken links).
The auto-send pipeline
Section titled “The auto-send pipeline”When a ticket is submitted, the plugin runs these checks in order:
- Resubmission check. Same email, within four days, similar content -> flag for human.
- Keyword blocklist. Sensitive terms -> flag for human.
- Hourly rate cap. Over 20 auto-sends this hour -> flag for human.
- Draft generation. First model drafts a reply grounded in the knowledge base.
- QA pass. Second model checks the draft against the customer’s question.
- If QA passes: reply is sent automatically by email. Status is
auto_sent. - If QA fails: the draft is regenerated once with the QA feedback appended. If the second pass still fails, the ticket is flagged for a human.
The whole pipeline typically completes within 15 seconds for auto-sent replies.
Change requests
Section titled “Change requests”From 1.5.0, the support form can take requests to change a page as well as support questions. Turn it on under Settings → Change requests. It is off by default.
When it is on, the form offers Request a change, with a field for the address of the page to change. The address must start with http:// or https://.
Each request moves through four stages:
| Stage | What your customer sees on the tracking page |
|---|---|
| Requested | Request received, waiting for approval |
| Approved | Approved, we will start on it soon |
| In progress | In progress |
| Done | Done |
Move a request with the stage buttons on the ticket. Your Helpdesk list can be filtered by stage. Customers see the stage, never who moved it.
The AI never answers a change request on its own. Finished requests close themselves 30 days after you mark them Done.
Who sent a reply
Section titled “Who sent a reply”Every reply records who sent it and how: from your Helpdesk screen, from your AI assistant over the API, or automatically by the AI. The ticket screen shows it as a “Sent … by” line. Your customers never see it.
Replies from your AI assistant
Section titled “Replies from your AI assistant”An AI assistant connected to your site (over MCP or the API) can send a ticket reply. Settings → Replies from your AI assistant decides what happens then:
- Can send after asking you (the default): it sends, as before.
- Need a person’s approval: the reply waits on the ticket with a “Waiting for your approval” note. Nothing is emailed until a site admin presses Approve & Send. Your assistant also cannot mark a change request Approved; only a person can.
Ticket look-up limits
Section titled “Ticket look-up limits”The “find my ticket” form on your tracking page carries the same security check as the support form. One visitor can try at most 10 look-ups an hour, so nobody can guess their way to another customer’s ticket. The tracking link in the confirmation email always works.
Admin notifications via Pushover
Section titled “Admin notifications via Pushover”The plugin can push a notification to your phone whenever something interesting happens: a ticket is flagged, an auto-send fires, the rate cap is hit, or a resubmission is detected. Setup takes about five minutes.
1. Create a Pushover account
Section titled “1. Create a Pushover account”Go to pushover.net and sign up. Install the Pushover app on your phone (iOS, Android) or desktop (macOS, Windows, Linux) and log in. There is a small one-off fee per device type after a seven-day trial.
2. Find your user key
Section titled “2. Find your user key”On the Pushover dashboard, your User Key is at the top right. It is a 30-character string. Copy it.
3. Create an application token
Section titled “3. Create an application token”On pushover.net, go to Create an Application / API Token. Name it something like “EP Helpdesk”. You can leave the description, URL, and icon empty. Submit. Copy the resulting API Token, another 30-character string.
4. Add the credentials to your site config
Section titled “4. Add the credentials to your site config”Edit the PHP config file that PageMotor loads early (often config.php at the site root) and add:
define('EP_HELPDESK_PUSHOVER_TOKEN', 'your-application-api-token');define('EP_HELPDESK_PUSHOVER_USER', 'your-user-key');Save. The plugin reads these constants on every event, so no reload is needed.
5. Test
Section titled “5. Test”Submit a ticket with the word refund in the subject. The safety-net will catch it and fire a push to your phone. You should see it within a couple of seconds. Tap the notification to jump straight to the ticket in admin.
What triggers a notification
Section titled “What triggers a notification”| Event | Priority | Notes |
|---|---|---|
| Ticket flagged by safety net | Normal | Deep-link opens the ticket in admin |
| Ticket flagged by QA double-fail | High | Needs human review, AI was not confident enough to send |
| Resubmission detected | High | Same email, similar content, within four days |
| Auto-send successful | Normal (warm-up) | Ambient confirmation that auto-sends are firing. Revert to Low in the code once weekly ticket volume makes Normal too noisy. |
| Hourly cap hit | Normal | Investigate if this is sustained |
Turning it off
Section titled “Turning it off”Remove the two constants from config.php. The plugin silently skips Pushover when credentials are absent; nothing else is affected.
Light / dark mode
Section titled “Light / dark mode”The helpdesk form and admin both support a theme toggle. A small sun / moon button sits in the topbar.
- On first visit, the form follows the visitor’s operating-system preference (
prefers-color-scheme). - Clicking the toggle cycles through auto -> light -> dark -> auto. The choice persists in
localStorageasep-helpdesk-themeand is applied before the first paint, so dark-mode visitors do not see a flash of light. - No server side setting. Each visitor controls their own theme; no admin configuration needed.
Colours come from a single token set (--ep-* variables) with a dark override block, so a future skin change needs one file touched rather than one per surface.
Retract window
Section titled “Retract window”Every auto-sent reply is retractable for 48 hours. From the admin ticket view, click Retract and apologise. The plugin:
- Sends a short apology email to the customer (“Our automatic reply may have missed the mark, a human is taking another look”).
- Sets the ticket status back to
reviewand generates a fresh draft for your approval.
After 48 hours, auto-sent tickets transition to replied and can no longer be retracted.
Resubmission detection
Section titled “Resubmission detection”The plugin prevents the same customer from getting two different AI replies to the same question. If a customer submits a ticket, then submits another within four days with a similar subject or body, the second is flagged for human review with a reference to the prior ticket.
Matching uses a word-overlap score (Jaccard on tokens) with a threshold. Near-duplicates flag; genuinely different questions do not.
Troubleshooting
Section titled “Troubleshooting”“Nothing happens after I click Submit”
Section titled ““Nothing happens after I click Submit””Check the browser console for JavaScript errors. The chip-based progressive disclosure requires JS. Without JS, the form still submits a ticket, but the category metadata is less complete.
“The AI draft was wrong”
Section titled ““The AI draft was wrong””That is what the 48-hour retract window is for. From admin, open the ticket and hit Retract and apologise. Then regenerate the draft or write the reply yourself.
If the same kind of mistake keeps happening, add clearer guidance on that topic to your knowledge base. Settings → Knowledge base file points at a .md or .txt file inside user-content; left blank, drafts use the EP Support knowledge base.
“I am not getting Pushover notifications”
Section titled ““I am not getting Pushover notifications””- Check
EP_HELPDESK_PUSHOVER_TOKENandEP_HELPDESK_PUSHOVER_USERare both defined. - Check the Pushover app is installed and logged in on your phone.
- Submit a test ticket with the word
refundin the subject. It should fire a safety-net ping. - Check PHP error log for any Pushover failures.
“Customer submitted a ticket but didn’t get a confirmation email”
Section titled ““Customer submitted a ticket but didn’t get a confirmation email””EP Email handles delivery. Check EP Email’s log. Usually an SMTP credentials or from-address issue.
“Auto-reply went to spam”
Section titled ““Auto-reply went to spam””The site’s from-address needs SPF, DKIM, and DMARC set up. Ask your hosting provider how to configure DKIM for outgoing mail.
Feedback and corrections
Section titled “Feedback and corrections”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.
Changelog
Section titled “Changelog”- 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.
- One automatic reply per address per day. A ticket from an address that already had an automatic reply today is held for you instead.
- The ticket form’s reply no longer shows the reference number to whoever submitted it.
- You get one alert an hour when the daily automatic reply limit is reached.
A security update. Please install it.
- Reply emails no longer repeat what the sender typed. The automatic reply used the subject and name from the form, word for word, and went to an address nobody had confirmed. Someone could type any address and any text and have your helpdesk email it in your name. The reply now says “Reply to your question” with the ticket reference and greets the reader with “Hi there”.
- Screenshots and PDFs on a support request. Customers can add up to 3 files (PNG, JPEG, WebP, GIF or PDF, 10 MB each) to the support form. A screenshot of an error is often quicker than typing it out.
- Kept private. Attached files are not public. Only a signed-in admin can view them, as thumbnails on the ticket and as links in the new-ticket email. The customer’s acknowledgement email does not mention them.
- Only the files you expect. Pictures and PDFs within the size limit are accepted; anything else is turned away with a clear message, so the customer can try again.
- A person always looks first. The AI reads only the text of a request, so a request with files gets its AI draft as usual but is held for you to send, even when replies are set to go automatically. The ticket says so.
- Your choice. Settings, “Screenshots and files”: Allow (the default) or Off. The form shows the limits your server can really take.
- Deleting a ticket deletes its files.
- Needs PageMotor 0.11.5.
- Works with EP CRM. Support tickets now appear on the customer’s record in EP CRM when they are opened, answered and closed, including tickets that close by themselves after 30 days. Nothing changes if you do not use EP CRM.
- Readable in dark mode. Field labels on the support form, the “find my ticket” form, and the status line, reference, subject and “Our reply” heading on the tracking page now follow your site’s dark-mode text colour. Before, they stayed dark grey on the dark background and were hard to read.
- Clearer required-field star. The red star beside required fields is a deeper red, easier to see on a white background, even when another plugin on your site styles stars in the lighter red.
- Needs PageMotor 0.11.5.
- Change requests. Switch on the new Change requests setting and your support form offers Request a change, with a field for the address of the page to change. Each request moves through four stages: Requested, Approved, In progress and Done. You move it with one click on the ticket, and your customer sees the stage on their tracking page. The AI never answers a change request on its own. Off by default, so your form looks the same until you switch it on.
- You can see who sent each reply. Every reply now records whether it went from your Helpdesk screen, from your AI assistant over the API, or automatically from the AI, and which person sent it. The ticket screen and your AI assistant both show it. Your customers never see it.
- Make your AI assistant ask a person first. A new setting, Replies from your AI assistant, can be set to Need a person’s approval. Then a reply your AI assistant tries to send waits on the ticket with a “Waiting for your approval” note until someone presses Approve & Send, and only a person can approve a change request. Left as it is, nothing changes.
- Safer ticket look-up. The “find my ticket” form on your tracking page is now better protected against misuse.
- Needs PageMotor 0.11.5.
- Helpdesk emails can carry your logo. Acknowledgements, replies and alerts now use the email template you chose in EP Email. Set EP Email’s Default Email Template to Default and add your Email Logo and footer, and every helpdesk email shows them. Left on plain text, nothing changes.
- Needs PageMotor 0.11.5.
- Choose whether AI replies go out on their own. A new AI replies setting: Send automatically (as before) or Hold for my approval, where every AI reply waits on the ticket until you read it and send it. Useful while you are still filling in your knowledge base.
- Fewer non-answers sent to customers. A reply where the AI says it can’t give, provide or point to the steps now always waits for you, like other replies that admit they can’t answer.
- The note under Settings now describes how AI drafts actually work.
- Needs PageMotor 0.11.5.
- Works the moment it is switched on. EP Helpdesk used to set up its storage only when someone opened your site’s admin. If it was switched on by your AI or by a script, and nobody had opened the admin yet, the support form could not save a request. It now sets itself up on the first visit to your site, wherever that visit lands.
- Needs PageMotor 0.11.5.
- Cloudflare Turnstile on the support form. If EP Email has Turnstile switched on, the support form now uses it too, with the same keys. Most visitors see nothing; a visitor Cloudflare is unsure about is asked to tick a box. Bots that fail the check get a polite thank-you and no ticket is opened.
- If Cloudflare cannot be reached, the form keeps working, and its other bot checks and hourly limits still apply.
- Needs EP Email 1.11.8 for Turnstile. Without it the form works as before.
- Needs PageMotor 0.11.5.
- Replies read cleanly. The AI is told to write plain text, and any Markdown it slips in (asterisks for bold, backticks, headings, link brackets) is turned into plain text before a reply is saved or sent. Customers no longer see stray symbols.
- Readable in dark mode and with your own brand colour. Section headings, the selected category, the reference code and the “Send another request” button now stay readable on a dark page. The submit button picks dark or light text to suit whatever brand colour your site sets.
- Needs PageMotor 0.11.5.
- Run a helpdesk under your own name. A new Branding group sets the team name that signs every email, the voice AI replies are written in, what customers ask about, British or American spelling, and your own knowledge base file. Leave it blank and nothing changes.
- A support form for hosted site owners. Choose “Hosted site owners” and the form asks about the site, domain, email and billing, never which plugin or host.
- Open a ticket on a customer’s behalf. A new
create-ticketaction lets your AI, or another system, record a ticket from an email, sends the customer their reference code and alerts you. No AI reply goes out unless you ask for the automatic pipeline. - Tracking links open the right ticket. The link in the confirmation email used to land on an empty look-up form.
- Better AI replies. The reply checker now reads the same knowledge base as the writer, so it stops rejecting correct steps. A reply that says it can’t confirm or answer is never sent on its own; it waits for you.
- Every AI round is kept on the ticket, with its verdict, so you can see an earlier draft that was better.
- The thank-you shows on screen after sending, and a button lets the visitor send another request.
- Harder for bots. The support form carries a signed stamp and must be on screen for a few seconds. A new limit caps tickets per hour for the whole form (default 30). The confirmation email no longer repeats anything the sender typed.
- Busy moments are smoother. At most two tickets are drafted by AI at the same time; others wait their turn.
- Needs PageMotor 0.11.5.
AI drafting and the reply check now use Anthropic’s Claude 5.5 models (Sonnet 5.5 and Haiku 5.5).
Replies are read correctly whatever order the model returns its parts in.
- AI drafting works again when EP Support is installed but switched off. On a site where EP Support was installed but not active, a new ticket got no AI draft at all and sat in “drafting”. EP Helpdesk now reads EP Support’s knowledge base straight from its folder, so drafting works whether EP Support is on, off, or on an older version.
- A ticket the automatic pipeline cannot finish is now flagged and you are alerted. If anything went wrong mid-way, the ticket used to stay in “drafting” with no warning. It is now flagged with the error and you get the Pushover alert, the same as other tickets that need you.
- Needs PageMotor 0.11.5.
- Work your helpdesk from Claude or any AI assistant. EP Helpdesk now has its own actions in your site’s API and MCP. An assistant connected to your site can show what is waiting, open a ticket with the person’s earlier tickets, draft a reply from your knowledge base, and send it once you say yes. It can also close tickets, take back an automatic reply, or run the automatic pipeline again. Administrators only.
- Nothing reaches a customer without your say-so. Sending a reply, taking back an automatic reply, re-running the pipeline (which can reply by itself) and deleting a ticket each refuse until the assistant confirms, so it has to ask you first. It also sees the same safety warnings the automatic replies obey, such as a ticket that mentions a refund.
- A reply that could not be emailed now says so. If your email settings stop working, sending a reply tells you the email did not go and keeps the ticket open with your reply saved. Before, it looked sent. An automatic reply that cannot be emailed is now flagged for you instead of being marked as answered.
- Needs PageMotor 0.11.5.
1.2.18
Section titled “1.2.18”- Security: AI reply drafting now connects with a credential issued to your own site. Nothing to set up.
- If drafting cannot reach ElmsPark for a moment, the ticket now says so plainly instead of showing a generic error.
- If you use your own AI connection, nothing changes for you.
1.2.17
Section titled “1.2.17”- 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.
- Removes a function call that PHP 8.5 reports as deprecated, so it no longer fills your error log.
1.2.16
Section titled “1.2.16”- 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.
1.2.15
Section titled “1.2.15”- Fixes a crash on the support ticket form when an older EP plugin is installed on the same site. Submitting the form returned an internal error and nothing was saved or sent. EP plugins share one common code library, and whichever copy loads first is the one every EP plugin on that site uses, so a single out-of-date plugin could leave this one calling a spam check its copy did not have. The check now carries its own fallback and no longer depends on another plugin being up to date.
- No change on a site where this never happened: the same spam check runs, and nothing else changed.
1.2.14
Section titled “1.2.14”- Blocks a spam bot that was getting past the form honeypot. The scraper changed its network address on every single request, so blocking by address never caught it, but it always sent a malformed browser identifier that no real browser sends. Forms now reject anything carrying that signature, with the same silent response a caught bot already got.
- It was not theoretical. One client site had taken 57 fake signups before this went in, and the same bot had hit 17 sites.