BotSupport vs Richpanel: A Fair Comparison for Ecommerce Stores

What is Richpanel, and who is it built for?

Richpanel is a helpdesk first and an AI product second, and it is worth being clear about that because it changes the whole comparison. The core of the product is a unified inbox, and on top of that inbox sit AI agents that try to resolve tickets without a human, plus a self-service portal where a customer can track an order, make eligible changes or ask for a person without starting a new thread. If you are shopping for a place for your team to work, that is what Richpanel is selling.

The channel coverage is genuinely broad. Richpanel's own marketing leads on website chat, email and SMS, and its integrations directory, checked on 6 August 2026, also lists social channels including Instagram and Facebook, phone support through telephony partners, and a long tail of ecommerce tooling. On the commerce side the directory names Shopify, WooCommerce, Magento and Amazon, alongside partner apps for returns, subscriptions and marketing such as Loop Returns, Recharge and Klaviyo. Integration directories change without notice, so treat that as a snapshot and check the current list for the specific tools you depend on.

Reception is good. At the time of writing Richpanel sits at roughly 4.7 out of 5 on both G2 and the Shopify App Store, across many dozens of reviews on each listing. We have linked both listings below rather than quoting counts, because those figures move week to week and the live page is more useful to you than our snapshot of it. Reviewers repeatedly praise the self-service portal, the clarity of the interface and how responsive the Richpanel team is during onboarding. Independent comparisons are less uniformly positive, and we cover what they report in the limitations section further down.

That mixture is normal for a category leader's challenger. Richpanel often appears on ecommerce helpdesk shortlists alongside Gorgias and Zendesk, which is a reasonable place for a buyer to encounter it, and the reason it belongs in a comparison like this one at all.

BotSupport is not a helpdesk and does not try to be one. It is a single AI chat assistant that answers customer questions on your website, grounded in your real products, prices and policies, and built and maintained for you rather than by you. If your problem is that you have four agents, six channels and no shared inbox, Richpanel is addressing that problem and BotSupport is not. If your problem is that the same forty questions arrive every week and nobody has time to answer them, that is the problem BotSupport is built for.

BotSupport vs Richpanel: who actually builds and maintains the assistant?

This is the axis that decides most of these comparisons, and it gets less attention than it deserves. Richpanel does offer real help at the start. Its migration page, checked on 6 August 2026, describes an assisted move from your existing helpdesk in which conversations, macros, tags, routing rules, SLAs and automations come across, and cites a go-live of about two weeks for a growing support team. The same page describes a dedicated manager running the rollout in the context of larger teams, so if a named implementation manager matters to you, confirm what is included at the size and tier you would actually buy. These are vendor claims and worth getting in writing.

What happens after go-live is the part buyers underestimate. Once you are live, the configuration surface belongs to your team. Somebody has to review what the AI answered, adjust the playbooks when a policy changes, keep help centre articles accurate because the AI reads them, prune macros that no longer apply, and fix routing when a channel misbehaves. For a support team of five that is simply part of the job, and a good platform is exactly what you want. Our view, and it is a view about self-managed software in general rather than an observation about Richpanel specifically, is that any configurable platform drifts when nobody has the time to maintain it. It is worth being honest with yourself about who will own that upkeep before you buy any tool of this kind.

BotSupport removes that surface rather than shrinking it. There is no dashboard to learn because there is nothing for you to configure. When your returns window changes from 14 days to 30, you say so and it is changed for you. When you add a product range, the assistant is reading the live catalogue rather than waiting for someone to retrain it. The work does not disappear, it moves to the supplier, and that is the entire proposition.

The honest cost of that model is dependency, and we would rather state it than let you discover it. With Richpanel you can log in at eleven at night and change a macro yourself. With BotSupport you cannot do the equivalent, because the change goes through a person and lands in working hours. If in-house control matters more to you than in-house workload, that is a perfectly good reason to prefer a platform, and no amount of managed-service marketing should talk you out of it.

How is each one grounded in your real products, prices and policies?

Richpanel is refreshingly direct about how its AI learns. Its homepage, checked on 6 August 2026, invites you to watch it read your entire website, your help centre, Trustpilot and even Reddit, with no prompt engineering and no months of tuning. That is a vendor self-reported claim, and it is a sensible approach for a large class of questions. For refund windows, delivery policies and general how-does-this-work queries, a well written help centre is a good source and using it saves you a setup project. For order-specific questions, Richpanel does the right thing and reads live order data from the connected store.

The interesting gap is product data. Any assistant that learns from crawled page content carries the risk of lagging behind price, stock and policy changes until its knowledge is refreshed. If a price changes, a variant sells out, a size chart is updated or a line is discontinued, a content-derived answer can stay confidently out of date until someone notices. This is not an accusation about any particular vendor, it is a property of the approach, and it is a fair thing to test rather than assume. Ask Richpanel how often its knowledge is re-synced, then test it against a product whose price you changed this week.

BotSupport is built against the catalogue itself rather than a copy of your marketing pages, which is why it is designed to stay current on prices and product detail without anyone remembering to refresh it. We should be equally plain about the limits of that: no AI assistant is right one hundred per cent of the time, ours included, and grounding reduces a category of error rather than eliminating error. Test it on your own awkward cases during the trial and count the failures, rather than taking either vendor's word for it.

The design difference matters most for stores with large or fast-changing catalogues, where prices, stock and variants move faster than anyone can maintain a knowledge base. It matters least for a store with twelve products that never change, where a good help centre is genuinely sufficient and the whole question is close to moot.

Neither approach removes the need for someone to define the awkward cases: what counts as a fair exception, when to escalate, what tone to use when a delivery is late. What differs is who does that defining, and how often the assistant has to be re-pointed at reality.

Does Richpanel work properly with WooCommerce, or is it Shopify-first?

To be fair to Richpanel, the WooCommerce integration is real rather than a token listing. Its own WooCommerce integration page, checked on 6 August 2026, describes accessing and managing customer and order details from the Richpanel dashboard, updating discounts, addresses and refunds, and creating draft orders so that support can act as a sales channel. We also found Capterra reviewers using Richpanel with WooCommerce as well as Shopify. That is more than many helpdesks offer outside Shopify.

The caveat is where the surrounding ecosystem sits. The self-service portal is at its strongest when a customer can cancel, swap, return or amend a subscription without an agent, and several of those actions depend on connected systems rather than on Richpanel alone. Richpanel's own self-service page is candid about this, noting that customers can make eligible subscription changes from the portal when your subscription platform supports the action. A July 2026 guide from Engaige makes the same point from the outside, reporting that Richpanel's deepest transactional actions such as subscription edits and returns run through Shopify-side partners like Recharge and Loop, and advising WooCommerce or Magento merchants to confirm the specific actions they need before assuming parity. That is good advice and we would repeat it.

One further signal, offered as a signal rather than a verdict. When we checked the WordPress.org listing for the official Richpanel for WooCommerce plugin on 6 August 2026, it showed a low install count and a last-updated date more than a year old. This is weak evidence on its own, because stores can connect by API without the plugin and install counts understate real usage, and we would not build a decision on it. Look at the listing yourself and weigh it alongside everything else if WooCommerce is your platform.

For a Shopify brand, Shopify-first depth is a feature rather than a flaw, and it would be strange to hold it against a product that is honest about where its ecosystem lives. For a WooCommerce store, it is the practical difference between a helpdesk that reads your orders and one that acts on them, which is worth thirty minutes on a demo call with a written list of the actions you need.

How do the pricing models compare, and what does staff time actually cost?

The two models are shaped for different buyers. Richpanel's is a volume model: you pay for the humans you employ and for the conversations the AI handles, so the bill scales with the size of your operation. Richpanel argues, reasonably, that billing per conversation rather than per resolution avoids the double meter some competitors use. Its pricing page also advertises a resolution guarantee, stating that if the AI does not resolve 50 per cent of tickets in 30 days you get your money back. That is a vendor claim on a vendor page; treat the threshold, the window and the refund mechanics as things to confirm in writing before you rely on them. The willingness to publish a guarantee at all is a point in Richpanel's favour.

Be careful with the exact numbers, including ours. When we compared sources on 6 August 2026, the figures did not agree. Richpanel's own pricing page showed $99 per seat per month plus $0.20 per AI-handled conversation. Its Shopify App Store listing showed plan tiers at different monthly prices again. A July 2026 comparison from Macha reported $0.20 per AI conversation with a $200 per month minimum plus $100 per seat, and a typical starting setup around $300 per month. A July 2026 review from The AI Agent Index reported per-agent plans at different prices again, and stated that all plans are annual contracts with no monthly billing option, which does not match the monthly and annual toggle we saw on Richpanel's own pricing page. Where sources disagree like this, the vendor's own page and a written quote are the only figures worth planning around, and older third-party pages quoting long-retired tiers should be ignored entirely.

BotSupport's model is fixed rather than metered, because there is only one thing to buy: a managed assistant on your site. There are no seats, because there is no inbox for anyone to sit in. There is no conversation meter, so the bill does not grow in the month a product goes viral. We are at Early Access stage, so the price is Early Access pricing and subject to change as the product leaves that stage. Ask us for the current figure in writing, including VAT status, the trial length and how long the price you sign up at is held. We would rather you had that in an email than inferred it from a blog post.

The line buyers routinely leave out of the spreadsheet is staff time. If maintaining a helpdesk and its AI playbooks takes two hours a week from someone on a modest UK salary, that is comfortably more per month than either subscription. On a platform, that time is yours to spend, and if you have a support team it is time well spent because they get a better tool out of it. On a managed service it is not yours to spend, which is the entire reason for paying someone else.

One more practical note on the metered line. Per-conversation billing means your AI cost grows as the assistant handles more volume, which is straightforward but easy to model badly. Take your actual conversation counts for the last three months, apply the current rate, and check the number against the seat costs you would still be paying. Do the same exercise for a peak month, not just an average one.

How quickly can each one be live?

These numbers are not like for like, and it would be dishonest to present them as though they were. Moving an entire support operation, including years of conversation history, agent routing, SLAs and dozens of macros, is a far bigger job than standing up one chat assistant. About two weeks for a full helpdesk cutover is a good timeline rather than a bad one, and any vendor promising you a same-day helpdesk migration would be worth distrusting.

What the comparison does tell you is how much has to be true before you get any value at all. With Richpanel, value arrives once the platform is configured, the team is trained and the AI has been through its ramp. The AI Agent Index's July 2026 review describes that ramp as roughly two weeks covering migration, team training, a copilot phase where the AI drafts replies for human approval, and then autonomous resolution. Expect resolution rates to keep improving over the following weeks as the system is tuned, rather than arriving at their final level on day one.

With BotSupport the sequence is shorter because the scope is smaller. The assistant is either answering your customers correctly by tomorrow or it is not, and you can judge it on that with your own questions. We should be plain that this is our stated target rather than a record of repeated delivery: BotSupport is at Early Access stage with essentially no customer base, so ask us to commit to a specific date before you pay anything, and hold us to it.

Richpanel's own migration guidance makes a sensible point that applies to both products, and to any support tool you have ever bought: do not take the old system offline until the new one has proved itself on a real queue with real customers. Overlap costs a little money and saves a lot of grief.

Who should honestly choose Richpanel instead of BotSupport?

There are several situations where Richpanel is straightforwardly the better purchase, and pretending otherwise would make this comparison worthless to you. The clearest is team size. Once three or more people are answering customers, the coordination problem becomes the actual problem: who owns which ticket, what was said last time, which queue is falling behind, who is on shift. That is a helpdesk problem, and BotSupport does not solve it and is not designed to.

The second is channel spread. If a meaningful share of your customers arrive by SMS, Instagram, Facebook or phone rather than through your website, Richpanel brings those into one inbox and BotSupport does not. Check the current integrations directory for the exact channels you need, because the list changes, but the shape of the product is clearly multi-channel and ours is clearly not.

The third is returns. A branded self-service returns and exchanges portal, where a customer can start a return or choose an exchange without an agent, is a real revenue-protecting feature rather than a nice-to-have, and Richpanel sells one as a paid module. If returns volume is a live problem in your business, that alone can justify the platform.

The fourth is evidence. Richpanel has a public review record on both G2 and the Shopify App Store, named customers and published compliance information. BotSupport has none of that yet. If your buying process requires references, case studies or a security questionnaire answered with existing documentation, that is a reasonable disqualifier for us rather than an unfair one, and we would rather you knew now than after a demo.

• You have a support team of three or more agents who need one inbox, routing, assignment and reporting. BotSupport does not replace a helpdesk and will not manage tickets.
• Your customers reach you on SMS, Instagram, Facebook and phone as well as your website. Richpanel brings those channels into one inbox; BotSupport is a website chat assistant that hands off to your existing email or helpdesk.
• You want a branded self-service returns and exchanges portal, which Richpanel offers as a paid module.
• You are on Shopify with subscriptions or a returns app such as Recharge or Loop Returns, and you want customers to make eligible changes themselves without an agent. Confirm which actions are supported for your exact stack.
• You need documented compliance for procurement. Richpanel publishes compliance information on its own site and app-store listing; request current attestation documents directly from them rather than relying on any third-party summary, including this one.
• You want proof from other buyers before committing. Richpanel has public review listings on G2 and the Shopify App Store. BotSupport has no such record yet, and no case studies to point at.
• You specifically want to configure and control everything in-house, at any hour, without asking a supplier to make the change for you.

How do you trial both fairly, or move from one to the other?

Start by pulling your last 50 customer emails or chats and sorting them into buckets: where is my order, product and sizing questions, stock and availability, returns and refunds, delivery times and costs, and everything else. That distribution tells you which tool you actually need, and it takes about an hour. If most of your volume is order status arriving across several channels, you have a helpdesk problem. If most of it is pre-purchase product questions on your website, you have a chat assistant problem. Plenty of businesses have both, in which case the question becomes which one is hurting more this quarter.

For Richpanel, ask whether the trial lets you run a pilot on a single queue while your existing helpdesk stays live, because that is much the safest way to evaluate a platform and you should not assume it is available by default. Then test the things independent reviewers raise rather than the things a demo shows you. A July 2026 comparison from Macha reports that reviewers found no internal notes or collision detection for looping a teammate into a live conversation, and that some flag inconsistent analytics data. We have not verified either point and both may have changed, so treat them as questions rather than findings: ask Richpanel to demonstrate internal collaboration on a live conversation, and reconcile the reporting against your own ticket counts before you use it for staffing or SLA decisions. That second piece of advice is worth following with any helpdesk you buy.

For BotSupport, the test is simpler because the work is done for you. Ask for the assistant to be built on the live catalogue, then put 20 real customer questions to it, including three awkward ones about prices, three about stock on specific variants, and three where the correct answer is to hand over to a human rather than to attempt an answer. Count wrong prices and invented policies. Those are the failures that cost you customer trust, and they are the only numbers in a trial that really matter.

On switching, the two directions are not symmetrical. Adopting Richpanel means replacing your helpdesk, which is a genuine migration with conversations, custom fields, attachments, automation rules and knowledge base content to preserve. Richpanel runs that migration for you, which is a real advantage over attempting it yourself, but plan for it as a project with a named owner and a date. Adopting BotSupport does not involve moving any tickets, because it adds a layer to your website rather than replacing a system, though it does need a snippet installed on your site and access to your catalogue, and it needs testing on the live site before you point customers at it. Nothing is entirely free, but the risk profiles are very different and that asymmetry is worth weighing.

What are the honest limitations of each?

Taking Richpanel first, and being careful to separate what we have checked from what others report. A July 2026 comparison from Macha reports that reviewers found no internal notes or collision detection for looping in a teammate on a live conversation, and that some flag inconsistent analytics data. We have not tested either claim, vendors ship features like these continuously, and it may well have changed by the time you read this. If internal collaboration or reporting accuracy matters to your team, ask Richpanel to demonstrate both directly rather than taking our word or anyone else's.

The same comparison rates Gorgias as having a notably larger set of native Shopify actions than Richpanel, while crediting Richpanel with covering the core ecommerce workflows well. Other published comparisons reach similar conclusions, but this is a moving target and depends entirely on which actions you need. The practical response is to write down the specific Shopify actions your team performs each week and ask both vendors to demonstrate each one on a call.

Two further points are structural rather than allegations. Per-conversation AI billing means the AI line on your invoice grows as the assistant handles more volume, so model it against your real conversation counts including a peak month. And Richpanel is a replacement rather than an addition: adopting it means moving your support operation, which makes evaluating it a bigger decision than evaluating a chat widget, and rightly so.

Now BotSupport, stated just as plainly. It does not do ticketing, agent seats, SLAs or routing, so it is not a Richpanel replacement for a team that needs those things. There is no free DIY tier and no way to build it yourself, because the managed model is the product rather than a delivery option. It is at Early Access stage, which means no meaningful customer base, no public review scores and no case studies to send you. Changes go through a person, so a 2am policy edit waits until working hours. Early Access pricing is Early Access pricing and is not a permanent commitment, so get the current figure and the terms in writing.

If a comparison article published by a vendor admits nothing, it is marketing rather than analysis. These are the trade-offs as they stood when we checked on 6 August 2026, from public sources we have linked so you can check them yourself, and both lists are worth taking to whichever demo you book.

Sources

1. Richpanel pricing page — Accessed 6 August 2026: helpdesk seats at $99 per seat per month, AI agents at $0.20 per AI-handled conversation, returns and exchanges module from $99 per month, 17 per cent annual saving, and a stated money-back guarantee tied to 50 per cent of tickets resolved in 30 days. Pricing changes often; check the live page.
2. Richpanel homepage — Accessed 6 August 2026: vendor statement that the AI reads your entire website, help centre, Trustpilot and Reddit with no prompt engineering and no months of tuning, plus a headline 50 per cent AI resolution claim.
3. Richpanel integrations directory — Accessed 6 August 2026: ecommerce platforms Shopify, WooCommerce, Magento and Amazon; channel integrations including Instagram, Facebook, Gmail and phone via telephony partners; plus returns, subscription, marketing and loyalty apps such as Loop Returns, Recharge and Klaviyo. Directory contents change without notice.
4. Richpanel WooCommerce integration page — Accessed 6 August 2026: access to customer and order details from the Richpanel dashboard, updates to discounts, addresses and refunds, and draft order creation.
5. Richpanel migration page — Accessed 6 August 2026: vendor claim of going live in about two weeks for a growing support team, with conversations, macros, tags, routing rules, SLAs and automations migrated; a dedicated manager is described in the context of larger teams.
6. Richpanel self-service portal page — Accessed 6 August 2026: self-service actions covering order tracking, eligible order changes, subscription management through connected platforms, and handover to a person. Subscription changes are stated to depend on the connected subscription platform supporting the action.
7. Richpanel on the Shopify App Store — Accessed 6 August 2026: roughly 4.7 out of 5, a 14-day free trial, plan tiers priced differently from the vendor's own pricing page, and published compliance information. Check the live listing for current ratings, pricing and terms.
8. Richpanel reviews on G2 — Public review listing, reported elsewhere as roughly 4.7 out of 5. We were unable to load this page directly on 6 August 2026, so check the live listing for the current rating and review count.
9. Richpanel reviews on Capterra — Review listing including merchants using Richpanel with WooCommerce as well as Shopify; ease of use and support rated highly, with pricing among the more commonly raised complaints.
10. Gorgias vs Richpanel comparison, Macha (13 July 2026) — Independent comparison reporting that reviewers found no internal notes or collision detection for looping in a teammate, that some flag inconsistent analytics data, that Gorgias has a notably larger set of native Shopify actions, and pricing of $0.20 per AI conversation with a $200 per month minimum plus $100 per seat. Not verified by us.
11. Richpanel review, The AI Agent Index (23 July 2026) — Independent review reporting per-agent plan pricing that differs from the vendor's pricing page, a claim that all plans are annual contracts with no monthly billing option, a roughly two-week onboarding ramp including a copilot phase, and a smaller review base than category leaders.
12. Best Richpanel alternatives, Engaige (8 July 2026) — Independent guide reporting that Richpanel's deepest transactional actions such as subscription edits and returns run through Shopify-side partners like Recharge and Loop, and advising WooCommerce or Magento merchants to confirm the specific actions they need before assuming parity.
13. Richpanel for WooCommerce plugin, WordPress.org — Checked 6 August 2026: low active install count and a last-updated date more than a year old. Weak evidence on its own, since stores can connect by API without the plugin. Check the live listing.

Details on Richpanel reflect its public documentation and independent reviews as of August 2026 and change frequently. This comparison is published by BotSupport, so read it as a vendor comparison and check the alternative for yourself. If something here is out of date, tell us and we will correct it.