Plugixa CRM – Contacts, Leads, Deal Pipeline, Email & Help Desk
Plugixa CRM – Contacts, Leads, Deal Pipeline, Email & Help Desk

Plugixa CRM – Contacts, Leads, Deal Pipeline, Email & Help Desk

0/5 (0 ratings) — active installs Updated Nov 11, 2026
Dashboard - open pipeline, deals won this month, overdue work and the leads worth calling, arranged in your own tabs

Dashboard - open pipeline, deals won this month, overdue work and the leads worth calling, arranged in your own tabs

🤝 Turn WordPress into a working sales and support CRM with Plugixa CRM – accounts, contacts and leads, deals on a drag-and-drop pipeline, meetings, calls and tasks on one calendar, email filed on the customer, support cases and a public help centre.

📚 Read the Documentation
🌐 Visit the official website Plugixa
✉️ Questions or support requests: Contact us
💬 Ask on the Support Forum
🚀 Upgrade to Pro

Run your CRM in 3 simple steps:

  1. Bring your customers in – add accounts and contacts by hand, import a CSV, or let a web form create leads
  2. Work the pipeline – drag deals from stage to stage, and book the meetings, calls and tasks that move them
  3. Look after them – send email from the record, track support cases, and answer questions once in the knowledge base

Records live in the plugin’s own database tables, not in posts and post meta, so lists, filters and the dashboard stay fast as your history grows.

A CRM That Behaves Like a CRM

✅ Pipeline – a kanban board where every stage carries its own probability
✅ Customers – accounts and contacts, linked with the role each person plays
✅ Activities – meetings, calls and tasks on one calendar
✅ Email – written and sent from any record, and kept on it
✅ Support – cases, a knowledge base and a public help centre

Key Features of Plugixa CRM

Records

  • Accounts: companies, with a parent account and customer, supplier and partner types
  • Contacts: people, with as many email addresses and phone numbers as they really have, one of each primary
  • Leads: capture, qualify, and convert into an account, a contact and an opportunity in one step
  • Opportunities: customisable pipelines and stages, a kanban board and stage history
  • Multiple currencies: price each deal in its own currency and see every total in yours

Working the day

  • Meetings, calls and tasks, with a calendar by month, week or day
  • Email: write and send from any record, with templates and placeholders, through WordPress’s own mail
  • A stream on every record: what changed, and what your team wrote about it
  • Follow a record, @mention a colleague, and get told in the notification bell
  • Reminders and in-app notifications

Support

  • Cases: a support queue with statuses, priorities, types and a case number that never changes
  • Knowledge base: articles in a category tree, linked to the cases they answer
  • A public help centre for the articles you choose to publish

Capturing leads

  • Web-to-lead forms, as a block or a shortcode, with a duplicate check and double opt-in
  • A REST endpoint for the forms you already have

Organising the team

  • Teams: everyone reads their team’s records and edits their own
  • CRM access: choose which WordPress users can open the CRM at all

Getting data in and out

  • CSV import: map your columns, create or update, and undo the whole run if it goes wrong
  • CSV export from any list, honouring the filter you are looking at
  • Duplicate detection and record merging, with an audit log
  • GDPR export and erasure through WordPress’s own privacy tools

Administration

  • Fast, Material UI-based admin application, with a search box that finds records and screens alike (press “/”)
  • Dashboards you arrange on tabs, with headline figures that show their trend over thirty days
  • An App manager: switch off any feature you do not use, without deleting its data
  • Tags, attachments on records and a shared document library
  • Trash: deleting a record is reversible
  • Translation-ready

Plugixa CRM Pro Features

Selling

  • Reports you build yourself, with charts and a weighted pipeline forecast
  • PDF documents from your own templates, such as quotes and proposals
  • Excel (XLSX) export
  • Dashboard templates to give the whole team the same starting dashboard

Marketing

  • Campaigns, target lists and mass email, sent in batches, with an unsubscribe that cannot be removed

Support

  • Inbound email: point it at a mailbox and messages become cases, with replies threaded onto them
  • A customer portal where your customers follow their own cases, as a block or a shortcode
  • Working hours and holidays, with free/busy that answers with the time someone can really be booked

Access

  • Roles: all, team, own or none, per entity and per action, with field-level rules and per-record sharing

Connecting

  • Webhooks
  • Google Calendar and Microsoft 365 calendar sync
  • Contact form plugins, Twilio SMS and WooCommerce

Upgrade to Plugixa CRM Pro

📊 Deals on a Board, Stages That Mean Something

Every stage carries its own probability, and every move between stages is recorded. Drag a card from Qualification to Closed Won and the open pipeline on the dashboard follows it; the stage history then tells you where your deals slow down.

🗂️ Its Own Tables, Not Posts

Accounts, contacts, deals, activities and cases are relational data, so they live in tables of their own, created on activation. Your posts table stays yours, and the lists and figures stay fast whether you have a hundred customers or a hundred thousand.

✉️ Email Filed on the Customer

Messages are written and sent from the record they are about, through WordPress’s own mail – so any SMTP plugin you already use applies. Each one stays on the contact and the account, so the history of a customer is never in one person’s inbox.

🛟 Support Without a Second Tool

Cases with a status, a priority, a type and a stable number your customers can quote back to you. Write the answer once in the knowledge base, link it to the cases it answers, and publish the articles you choose in a help centre on your own site.

🖥️ On Your Own Site, in Your Own Theme

The whole CRM can run on a page of your site for your staff, and the help centre and lead forms sit inside your theme. Each loads its CSS and JavaScript only on the pages where you place it; every other page on your site loads none of it.

🔐 Privacy

The plugin stores what a CRM has to store, in your own database, and sends no record data anywhere. Attached files are kept in a protected folder rather than the media library, and the plugin checks on activation that your web server really keeps that folder private.

👨‍💻 Author

Plugixa CRM is developed by Plugixa, building focused, well-documented WordPress plugins with an emphasis on performance, clean code and correct data.

Shortcode Usage

The whole CRM on a page of your site, for your staff:
[plugixa_crm_app]

The public help centre:
[plugixa_crm_kb]

A web-to-lead form:
[plugixa_crm_lead_form id=”1″]

External services

The plugin includes the Freemius SDK, described first below. Every other connection is one you switch on or set up, and no CRM record data is ever sent to Plugixa or to Freemius. The plugin also requests one test file from your own site’s address, to check that the attachments folder is not publicly readable; that request goes to your own site and nowhere else.

The plugin is published by Plugixa. Our policies are here:
Terms of Service: https://www.plugixa.com/terms-of-service
Privacy Policy: https://www.plugixa.com/privacy-policy

Freemius (an optional opt-in, and account management)

What it is: Freemius, Inc. provides the opt-in screen shown on activation and the plugin’s account page.

What is sent and when: on activation you are shown an opt-in screen. If you skip it, no identifiable data is sent. If you opt in, the data that screen lists is sent to api.freemius.com: your WordPress user’s name and email address; your site’s address and title, WordPress and PHP versions and language; the plugin’s version and whether it is active or uninstalled; and, unless you switch it off on that screen, the names and versions of your installed plugins and themes.

On the plugin’s Upgrade page only: opening it loads Freemius’s pricing and checkout from checkout.freemius.com, and Freemius’s page also loads Google Analytics (www.google-analytics.com). Both receive your browser’s IP address and the fact that the page was opened. Nothing is loaded from either unless you open that page.

Freemius Terms of Service: https://freemius.com/terms/
Freemius Privacy Policy: https://freemius.com/privacy/
Google Terms of Service: https://policies.google.com/terms
Google Privacy Policy: https://policies.google.com/privacy

European Central Bank (currency rates, off until you switch it on)

What it is: switched on under Plugixa CRM > Settings > Currency rates, with “Update automatically from the European Central Bank”. While it is off the plugin never contacts the ECB; you type in the rates yourself instead.

What it connects to: www.ecb.europa.eu, to download the ECB’s public euro foreign exchange reference rates (/stats/eurofxref/eurofxref-daily.xml). No account or key is involved.

When: once a day on WP-Cron, after the ECB publishes its rates in the afternoon (Frankfurt time), and immediately when you switch it on or press Update now.

What is sent: an ordinary HTTPS request for that one public file. Like any web request it carries your server’s IP address and a User-Agent naming the plugin and its version. No site data and no customer or record data is sent.

What is received: the day’s reference rates, which are stored as the CRM’s currency rates.

Legal notice: https://www.ecb.europa.eu/services/disclaimer/html/index.en.html
Privacy statements: https://www.ecb.europa.eu/services/data-protection/privacy-statements/html/index.en.html

Source Code

The complete human-readable source for the compiled JavaScript and CSS ships inside this plugin, with pinned dependencies (package.json + package-lock.json):

  • Admin app: assets/backend/app/ (React 19, Material UI 9, TanStack Query 5, React Router 6, React Hook Form, Recharts; TypeScript 5, Vite 8), built to assets/backend/build/
  • Public app: assets/frontend/app/ (React 19, Material UI 9, Emotion; TypeScript 5, Vite 8), built to assets/frontend/build/

Build with Node.js 20+: in each of those directories run npm install then npm run build. Both builds run tsc --noEmit before Vite, so they type-check as well as compile.

They are separate projects on purpose. The admin app carries the data grid, the scheduler and the charting library and comes to about 1.5 MB; the public app has none of them, so a page carrying a contact form downloads about 135 KB gzipped rather than the CRM.

Some front-end assets are not compiled at all: assets/frontend/*.css and the small plain-JavaScript files beside them, plus the Gutenberg block that places the lead form (assets/frontend/block/), which is written against WordPress’s own editor APIs with no build step.

The [plugixa_crm_app] shortcode mounts the compiled ADMIN app, because it is the admin app on a different page. It loads nothing at all for a visitor who does not hold the CRM capability.

Bundled PHP libraries, all shipped as readable source under vendor/:

  • Freemius WordPress SDK (GPL-3.0-only): the opt-in and account screens described under External services.
  • psr/container (MIT): the service container interface.