Every support tool your customers touch, in one place on your own site.
Secure checkout. 14-day unconditional refund period.
Most WordPress businesses rent these one at a time and stitch them together with email. Core Support puts them under one wp-admin menu, with one brand, and every conversation that needs a person lands in the same inbox.
A shared inbox your whole team answers from.
wp-admin → Core Support
Every request becomes a numbered ticket, wherever it starts.
Your support page
Docs that answer the question before it turns into a ticket.
/docs/
Answers from your docs and products, with your own API key.
Any page, one script tag
Every release of every product, on one page.
/changelogs/
Show customers what’s planned, in progress and shipped, on your own site.
/roadmap/
Real-time conversations with a person, in the same chat window.
wp-admin → Live chat
10 sites for $69 a year, 20 for $99, or 25 for $199 once. Unlimited agents on each.
Compare the plans Or look around the live demoThe admin screens come from the demo site, which runs Core Support 1.3.3 with made-up tickets and customers. Look around the demo yourself.
This store runs on it too: the support portal, the Core Support docs, its changelog, its roadmap and the Ask a question chat in the corner of every page.
Here’s the support stack a WordPress business usually pays for, one login and one invoice at a time, matched to the part of Core Support that does the same job.
| The job | What sites usually pay for | In Core Support |
|---|---|---|
| A shared inbox for your team | A hosted helpdesk such as Help Scout or Zendesk | Helpdesk: inbox, assignment, private notes and team alerts |
| Turning email and forms into tickets | An email-piping add-on, plus a form plugin on every site | Ticketing: IMAP, Cloudflare relay, automation tools, form plugins and connected sites |
| Letting customers follow their requests | A separate customer portal or forum | A portal page, blocks and a Support tab in WooCommerce and FluentCart accounts |
| Keeping one record per customer | A CRM, or the customer profiles in a hosted helpdesk | Customers, synced from WooCommerce, FluentCart, Easy Digital Downloads and FluentCRM |
| Moving off your old helpdesk | A migration service such as Help Desk Migration | Imports from Zendesk, Freshdesk, Intercom or a CSV file |
| Answering the same question once | A hosted knowledge base such as HelpDocs or Document360 | Knowledge base at /docs/, with importers for the docs you already have |
| Answering when nobody is online | A chatbot service such as Intercom Fin or Chatbase | AI chatbot that answers from your docs with your own API key |
| Telling customers what changed | A changelog tool such as Beamer or Headway | Changelog at /changelogs/, written in wp-admin or synced from GitHub |
| Talking to visitors in real time | A live chat tool such as Crisp or Tidio | Live chat in the same window as the AI chatbot, answered from wp-admin |
| Showing what’s planned | A roadmap tool such as Canny | Roadmaps at /roadmap/, with reactions and feature requests |
| Matching your brand | Custom CSS on every hosted screen | One branding screen for the customer portal and the inbox |
Phone support isn’t included, so keep your current tool for calls.
The cheapest ticket is the one nobody needs to send. Core Support publishes your docs, lets the AI chatbot answer from them, and keeps a changelog customers can check before they ask whether something is fixed yet.
Knowledge base
A docs site that doesn’t depend on your theme: one collection per product, sections and pages, instant search, numbered steps, callouts and an On this page outline.
The importer brought in core-forms.com’s 112 pages and 4,577 blocks with zero invalid blocks in the editor.
AI chatbot
Chat answers from your docs, posts and product data using your own key from a provider such as OpenAI, Anthropic or DeepSeek. You pick the model, how long answers run and which topics it stays within.
Instructions planted in a doc can’t change Chat’s rules, and it never claims to have done something it can’t do.
Changelog
A changelog for each product plus an All releases page. Customers check what changed before they write in, and search engines get one clean page per release.
This store’s own changelog runs on it, with more than 650 releases across its products.
See this store’s changelogWhen the AI chatbot can’t help, Talk to a person brings in your team. Agents answer from the Live chat screen in wp-admin, and every message stays on the ticket.
Pick the routes that fit the mailbox and forms you already have. Replies are matched by a private reply address or the email’s Message-ID, never the subject line, and mail from a new sender waits for a person unless you choose to open those tickets automatically.
Everything below ships today and comes with every plan. Nothing is held back for a higher tier; plans differ only in how many sites they cover.
Filter by status, assignment and priority, and search by subject, ticket number, customer name or email.
Notes sit in the same thread as replies but never reach the customer or their inbox.
Every outgoing reply shows its delivery state, with retry and cancel for failures.
New tickets reach Telegram, Slack, Discord, Pushover or a signed webhook, with retries when a service is down.
Orders and licenses from WooCommerce, FluentCart and Easy Digital Downloads, and FluentCRM contacts, beside each ticket.
Bold, links, lists, code and pasted screenshots, shown the same way in the portal and in email.
The people you choose delete tests and spam for good, one ticket or a page of them at a time.
Every buyer and requester gets a customer number, found by any of their email addresses.
WooCommerce, FluentCart and Easy Digital Downloads buyers arrive with their orders, and FluentCRM fills in details.
Define fields once, map them to each source and show the ones agents need beside tickets.
Tickets, replies, private notes, attachments and requesters arrive with their original dates.
Customers or tickets from a spreadsheet, or from a helpdesk without an importer here.
Imports send no email, skip what’s already there, bring over later changes and can be undone.
Checks Gmail, Fastmail, Zoho or your host’s mailbox and imports new mail, even if someone already read it.
A Worker on your own Cloudflare account posts signed messages within seconds.
FlowMattic, Zapier, Make, n8n and Pipedream post raw email or parsed fields with a token.
Contact Form 7, WPForms, Gravity Forms and Fluent Forms open tickets per form, and Core Forms gets a ticket action.
Replies match by private reply address; new senders, auto-replies and bulk mail are held or filtered.
A ready-made support page with its own layout, independent of your theme’s header and footer.
Customer Portal, New Ticket and My Tickets blocks for pages you already have.
A Support tab in WooCommerce My Account and the FluentCart customer dashboard, plus Get help with this order.
Customers on your other sites sign in with an emailed code and see that site’s tickets.
One snippet for static sites, site builders and other WordPress installs, limited to the addresses you allow.
Send tickets from your own code with a site key, metadata and attachments.
Collections, sections and pages on standalone pages that load only Core Support’s own styles.
Instant search, an On this page outline, previous and next links, steps and callouts.
Bring docs in from a sitemap, any website, Markdown or wordpress.org, as drafts with images and links fixed.
Was this helpful? votes and a Docs insights screen point at the pages that need work.
Learns your docs and any public post type, and keeps answering while it relearns.
Prices, options, stock, subscription and license terms from WooCommerce, FluentCart and EDD products.
A model and thinking level for each task, from providers such as OpenAI, Anthropic and DeepSeek.
Answer length, topic scope, your own rules and a daily token budget.
Talk to a person opens a ticket with the whole transcript.
The AI conversation goes live with whoever is online, and every message stays on the ticket.
Waiting and live chats, the conversation, and the visitor’s orders and licenses in three columns.
A waiting chat shows in the toolbar bell and reaches team email, Slack, Telegram, Discord or Pushover.
Replies a visitor reads in the chat aren’t emailed again. Unread ones follow by email after three minutes.
A chat nobody joins within five minutes, or the wait you set, carries on as an email ticket.
WordPress delivers messages with no setup, or connect your own Cloudflare Worker for instant delivery.
A changelog for each product, an All releases page and a page for every release.
Pulls releases from GitHub, readme.txt, CHANGELOG.md or wordpress.org every 24 hours, without overwriting your edits.
RSS, a JSON API and WP-CLI for every changelog.
A drag-and-drop board across four stages, with readers’ suggestions in their own column.
Visitors react with a thumbs up or down and send feature requests from the roadmap.
Roadmaps live at /roadmap/ or an address you choose, in your branding.
Files are saved from each message and listed where they arrived, with authorized downloads.
Originals and attachments are encrypted on your server before they reach R2, S3 or Bunny Storage.
Brand name, logo, accent color, neutral palette, corner radius, font, and light, dark or automatic mode.
Send through WordPress mail or the Emailit, Resend, Brevo or SendGrid API.
Checks storage, mail connections and signatures from the admin or WP-CLI.
Poll mailboxes, import docs, test storage and move older originals out of the database.
Updates arrive in the normal WordPress update screen once a site is activated.
WordPress’s export tool lists a person’s tickets, customer record and linked orders. Erasure anonymizes the tickets and deletes the record.
Email originals and attachments start in the database. Move them to private files or object storage when the database gets heavy. The storage provider only ever sees encrypted files, and every download goes through WordPress and checks the viewer’s access first.
Run wp core-support storage migrate to move existing originals out of the database. It reads each file back before switching, and you can rerun it safely.
Core Support adds its own wp-admin menu and creates a support page on activation. Your theme and existing pages stay as they are.
Upload Core Support to a site running WordPress 7.0+ and PHP 8.2+. The inbox, the customer portal, docs and changelogs are ready straight away.
Add a mailbox under Core Support → Connections and send a test email. Import your docs from a sitemap, Markdown or wordpress.org and your tickets from Zendesk, Freshdesk or Intercom, or start fresh.
Add an AI provider key and let Chat learn your docs. Set your logo and colors, then point customers to the portal and the docs.
Email that isn’t part of a conversation
It waits in Incoming mail. An agent accepts it as a new ticket or discards it, so a forged reply can never land on someone else’s ticket.
Core Support is new. These are the edges that matter today, so you can decide before you install it.
Each plan includes the helpdesk, ticketing, knowledge base, AI chatbot, live chat, changelogs and roadmaps, with unlimited agents and client projects allowed. Plans differ only in how many sites you activate and whether you renew.
Yearly
Renews yearly until you cancel
For a business with a handful of sites or a few client projects.
Cancel anytime. Core Support keeps working.
Yearly
Renews yearly until you cancel
For agencies running support across more client sites.
Cancel anytime. Core Support keeps working.
Best value
25 sites, updates for life
Three agents on Help Scout Standard cost $900 a year. Lifetime costs $199 once.
No renewal, ever.
For comparison, Fluent Support Pro lists $249 a year for 5 sites and $399 a year for 50, and Help Scout Standard lists $25 per user per month, as shown on their pricing pages on October 14, 2026. 14-day unconditional refund period on every plan. Lifetime licenses bought before November 2, 2026 keep unlimited sites. Hosting, mailbox, storage and AI provider costs are separate. Prices in USD; checkout shows the final amount before payment.
The things worth knowing before you move your helpdesk, docs and changelog onto your own site.
Something else on your mind? Ask through product support. Incredibly fast and helpful one-on-one email and Twitter Chat support.
Everything on this page: the helpdesk, ticketing, customer records, imports from Zendesk, Freshdesk, Intercom and CSV files, the customer portal, the knowledge base, the AI chatbot, live chat with a person, changelogs and public roadmaps. New features reach every plan as normal updates, with no upgrade fee.
Yes. The Core Support docs are public, from installation to the developer reference, and each Core Support screen links to its guide.
You need an API key from a provider such as OpenAI, Anthropic or DeepSeek, and that provider bills you for usage. A daily token budget caps what Chat can spend. The helpdesk, docs and changelogs work without any AI key.
Yes. Import them from a sitemap, any website, Markdown files or a wordpress.org readme. Pages arrive as drafts, images are copied into your media library once, and links between pages point at the new docs.
Yes. Core Support imports tickets, replies, private notes, attachments and requesters from Zendesk, Freshdesk and Intercom, or from a CSV file. Imports keep the original dates, send no email, skip anything already imported and can be undone. Help Scout and the WordPress helpdesk plugins don’t have an importer yet.
Yes. Point a changelog at GitHub releases, a readme.txt, CHANGELOG.md or changelog.txt file, or a wordpress.org plugin. It syncs every 24 hours by default, private repositories work with a token, and releases you edit by hand are never overwritten.
No. IMAP polling, automation tools, form plugins and connected-site forms all work without one. The Cloudflare relay is one route among five.
Not through IMAP polling yet, because Microsoft requires OAuth for IMAP. Use the Cloudflare relay or an automation tool for Microsoft 365 mailboxes.
Yes. Every plan covers client projects: 10 or 20 sites on the yearly plans, or 25 sites with the lifetime license. Each WordPress site keeps its own tickets, settings and activation.
Core Support keeps working on your sites, tickets and all. Updates and one-on-one support stop until you renew.
Nothing. Lifetime licenses bought before November 2, 2026 keep unlimited sites and agents, with updates for the life of Core Support.
In your database by default. You can move them to private local files, Cloudflare R2, an S3-compatible bucket or Bunny Storage. They’re encrypted before upload.
No. Core Support has its own ticket form and portal. FluentCart only handles the purchase and license on this store.
It runs this store’s own support desk, docs, changelogs and roadmaps. It hasn’t handled a high-volume mailbox yet, so start on a staging site or with a small pilot, and keep your current support channel running until you trust it.
There’s a 14-day unconditional refund period. Ask for a refund within 14 days of purchase and you get your money back, no questions asked.
Install it on a staging site, connect the mailbox you already use, import your docs and let Chat learn them. Send a few test conversations end to end, then invite customers. Plans start at $69 a year for 10 sites, and every plan has a 14-day unconditional refund period.
