Skip to content

EP CRM

EP CRM gives every person your site deals with one contact record, built from the customers your other EP plugins already hold. It never copies their data: each plugin stays the place its bookings, orders, subscriptions and tickets live, and keeps working with EP CRM switched off.

Published by ElmsPark Studio.

  • PageMotor 0.11.5 or later while PageMotor is in beta.
  • EP Connect for new activity to arrive as it happens. Without it, EP CRM still links everything in the background job.
  • EP Cron is recommended, so the background job runs on a steady schedule.
  • EP GDPR if you want export and erasure requests to include what the CRM holds.
  1. Download ep-crm.zip from your ElmsPark account.
  2. Upload via Plugins → Manage Plugins. Activate.
  3. EP CRM creates its tables on the first page load, then starts linking the customers your other EP plugins already hold.
  4. Open the Merge queue from time to time to decide on possible duplicates.

Updating from an earlier version adds any new tables or columns on the first page load after the update, keeping every contact, link and company as it was.

EP Booking customers, EP Events customers and registrations, EP Newsletter subscribers, EP Ecommerce orders, EP Helpdesk tickets, EP Email Leads (the “lead” lane only), EP Affiliate affiliates and EP Finance Invoicing invoices, and site accounts (a sign-up, and EP Membership’s email check). Install whichever you use; EP CRM links what it finds.

  • The same email address is always the same person. Addresses are compared after tidying (spaces, capitals, a trailing full stop), but anna+shop@ and anna@ stay different, and so do josé@ and jose@.
  • A shared phone number, a +tag address or the same name at the same company never merges anyone automatically. They appear in the Merge queue for you to decide.
  • An address only becomes a contact’s main email once something proves it: a payment (a completed order, a paid booking or a paid event place), a paid invoice, an approved affiliate, a member clicking the link in EP Membership’s confirmation email, or a subscriber clicking the link in EP Newsletter’s double opt-in confirmation email. A form someone filled in, a newsletter subscription that was not confirmed that way, a free booking or event place, or a site account on its own, shows as “unverified”.
  • If a member’s address is changed afterwards in the site’s user admin, EP CRM does not treat the new address as proved: EP Membership’s check was for the old one. The one case it cannot tell is a change made before EP CRM first saw that account.
  • Something unverified that matches an existing contact’s address is linked to that contact and shows in its history, but changes nothing on it: not the phone, the name, the company, the main email or marketing consent. Anyone can type someone else’s address into a form. A contact first created from something unverified does take its details. The one exception is a newsletter unsubscribe, which turns marketing consent off (see below for when EP CRM sees it).
  • A contact becomes a customer only when money was taken: a paid order, invoice, booking or event registration. A free booking or a free event place shows in the history but leaves them a lead; if that booking is paid later, they become a customer then.
Section titled “Newsletter subscribers and marketing consent”

A newsletter subscription turns a contact’s marketing consent on, and proves the address, only when the subscriber clicked the link in EP Newsletter’s confirmation email (double opt-in). EP CRM sees that click as it happens and records it straight away as “Newsletter confirmed” in the contact’s history.

These do not turn consent on and do not prove the address, whatever the double opt-in setting says today:

  • a subscription made with double opt-in off (single opt-in, EP Newsletter’s default),
  • a subscriber added by hand in EP Newsletter, or imported from a file as active,
  • a subscriber added by another plugin or through the API without double opt-in,
  • a subscriber put back to Pending by hand in EP Newsletter’s subscriber list, even if their confirmation link is then opened.

They show in the history as “Newsletter subscribed”. EP Newsletter keeps no record of who clicked a confirmation link, so EP CRM cannot tell afterwards. A subscriber who confirmed before EP CRM was installed, or while it was inactive, stays unverified until they confirm again (for example by subscribing again with double opt-in on).

One case EP CRM cannot tell apart: EP Newsletter shows a pending subscriber’s confirmation token to site admins (in its subscriber list and its admin API). Someone with that access can open a pending subscriber’s confirmation link themselves, and EP CRM counts that as the subscriber’s click. Keep admin access, and admin API tokens, to people you trust with consent records.

Unsubscribes. An unsubscribe turns consent off. When the subscriber uses the unsubscribe link in an email or their email app’s unsubscribe button, or is unsubscribed through EP Newsletter’s API, EP CRM records it as it happens, with the Background job on or off. A subscriber whose status is changed to Unsubscribed by hand in EP Newsletter’s subscriber list is picked up by the Background job a few minutes later; with the Background job off it is not picked up, and if the status is set back to Active before the job gets to it, EP CRM never sees that unsubscribe. Subscribing again and confirming turns consent back on.

Double opt-in is the setting Double Opt-In in EP Newsletter’s Subscription settings. A subscriber added through EP Newsletter’s API with its double opt-in option, or imported with “send confirmation” ticked, also gets the confirmation email, and their click counts the same way. A confirmation link opened by an email security scanner counts as a click, as it does for EP Newsletter itself.

New activity arrives as it happens through EP Connect. Everything that was already on your site is linked in the background every few minutes. With EP Cron installed and pinged, EP Cron runs that job every 5 minutes. Without EP Cron, or when EP Cron has not run the job for 15 minutes (installed but nothing pings it), EP CRM runs it itself at the end of a page request, at most once a minute. Only one run happens at a time either way.

Settings > Background job switches it off. While it is off, older rows are not linked, contacts arriving through EP Connect are not checked for duplicates, erasures made in EP GDPR while EP CRM was inactive are not caught up, and a newsletter subscriber set to Unsubscribed by hand in EP Newsletter’s subscriber list does not have consent turned off; new activity still arrives through EP Connect, and newsletter confirmations and unsubscribes made through their links or EP Newsletter’s API are still recorded as they happen. An erasure made while EP CRM is active happens at once whatever this setting says. If EP CRM is busy at that moment (a merge or a burst of new activity holds it for more than 10 seconds), it finishes the erasure on its next background run, which still happens for that one job while the setting is off.

Open the Merge queue, check the two records, press Merge. The record you keep shows everything from both. Undo is available on the most recent merge of a record.

EP CRM makes a company on its own when it sees a work email address (anything but Gmail, Outlook and the other free email services). Since 0.2.0 you can also keep a company on purpose, such as a client brand, through Claude or the PageMotor API:

  • Create or edit it with crm_upsert_company: a name, the brand’s own domain (a web address is fine), an account owner and a country. Asking again with the same domain, or the same name, finds the one you already have rather than making a second. A company EP CRM made from an email domain is taken over as yours when you name its domain.
  • Tie people to it with a role (owner, approver, contact) using crm_company_contact, or contact_id and role on crm_upsert_company. Their contact record shows the company.
  • Point it at pages and orders with crm_link_to_company: a landing page is plugin PM, object content and the page’s id; an EP Ecommerce order is EP_Ecommerce, order and the order number. Each page or order belongs to one company; to give it to another company, pass move. The buyer’s own record is not changed.
  • Read it with crm_get_company: the people, the pages and orders with a one-line summary each, and counts. Pass a page or order instead of a company id to find out whose it is.
  • Two records for one brand? crm_merge_companies merges them and crm_undo_merge takes it back. Companies are only ever merged with companies, never with a person.

For plugin developers: your plugin can show its own rows on a company or contact record with a live summary. From your plugin’s init(), when class_exists('EP_CRM_Resolvers'), call EP_CRM_Resolvers::register('Your_Plugin_Class', 'Your_Resolver_Class') with a class that extends EP_CRM_Resolver. The built-in ones cannot be replaced.

When EP GDPR erases someone, EP CRM erases their whole record: every address and phone number you have merged into it, not only the one in the request. Names and contact details are removed, notes, tasks and merge suggestions deleted, their ties to every company removed, a company created from their own email domain that nobody else belongs to is deleted (one you created or took over, or one holding pages or orders, is kept: it is the business’s record), and the history is kept only as “[erased]”. Those addresses and numbers are kept out of the CRM from then on, even when another plugin still holds older rows for them, and an address EP CRM had not yet linked is kept out the same way. Other plugins erase only the address in the request: an unmerged second address, and anything another plugin holds under it, stays where it is, so erase each address the person used. If the same person comes back later and books or buys again, they get a fresh record. An order that was still settling when they were erased does not count as coming back. EP Helpdesk keeps its own copy of tickets, and the record marks those links “plugin keeps its own copy”. EP Ecommerce (0.1.48 or later) erases or anonymises orders, keeping only orders still settling or held by a shop extension until they settle; an older EP Ecommerce keeps its own copy and is marked the same way.

Claude (or any MCP client) can use crm_search, crm_get_contact, crm_timeline, crm_log_activity, crm_add_note, crm_create_task, crm_complete_task, crm_upsert_contact, crm_merge_suggestions, crm_merge, crm_undo_merge and, since 0.2.0, crm_search_companies, crm_get_company, crm_upsert_company, crm_company_contact, crm_link_to_company, crm_unlink_from_company and crm_merge_companies. On PageMotor’s own MCP connection they appear as EP_CRM__crm_search and so on. Reading (crm_search, crm_get_contact, crm_timeline, crm_search_companies, crm_get_company) needs a producer token; anything that changes data, and the merge queue, needs an admin token, and a producer connection does not see those tools at all. Changes made through them are written to PageMotor’s audit log. The same actions are on the PageMotor API under the crm family of EP_CRM, plus crm_backfill_tick and crm_diagnostics for operators (API only, not MCP tools).

Deals and pipelines, custom fields and segments, and a company screen in the admin arrive in later versions. Companies are managed through Claude and the API for now.

  • Companies you keep on purpose. A client brand, or any company, can now be created and edited by hand, with a name, its own domain, an account owner and a country. Before, a company only appeared when EP CRM saw a work email address. A company EP CRM had already made from an email domain can be taken over as your own record.
  • People at a company. Tie a contact to a company with a role such as owner, approver or contact, and mark it as their main company. The contact’s record shows it. A person’s merged records count as one.
  • Pages and orders against a company. Point a company at a landing page (any PageMotor page), an EP Ecommerce order, or a row from any other plugin. Each row belongs to one company at a time; moving it to another company is a deliberate step. The company record lists them with a live one-line summary, and you can look up which company holds a given page or order. The buyer’s own record is not changed.
  • Merging companies. Two records for one brand can be merged, and the merge undone. A company is never merged into a person: company merges only ever touch companies.
  • New AI assistant tools. Claude and the PageMotor API can now search, create, edit, link and merge companies. Changes that merge or remove company links need administrator access and are recorded in the audit log.
  • Other plugins can now teach EP CRM to show their own rows (a page, an approval) with a live summary, instead of a plain “Page #12”.
  • GDPR. EP GDPR’s export now also lists the companies a person is tied to and their role. An erasure still removes the person’s ties to every company and still deletes a company made from their own email domain that nobody else belongs to. A company you created or took over, or one holding pages or orders, is kept, because it is the business’s record rather than the person’s.
  • Updating from 0.1.0 adds the new table and column on the first page load after the update, keeping every contact, link and company as it was.

The contact spine: one contact per person, linked by pointer to the customers in EP Booking, EP Events, EP Newsletter, EP Ecommerce, EP Helpdesk, EP Email Leads, EP Affiliate and EP Finance Invoicing, with a timeline, notes, tasks, an undoable merge queue, GDPR export and erasure, and the whole record over MCP. This version was not offered on the update channel; 0.2.0 is the first.