BotSupport vs Re:amaze: Which Suits Your Ecommerce Store?

What is Re:amaze, and what is it actually for?

It helps to be precise about the category, because a lot of comparison content blurs it. Re:amaze is not a widget, a quiz tool or an enterprise contact centre platform. It is a shared inbox and ticketing system with a chat widget attached. The core job it does is take every inbound message from every channel, put it in one place, and give a small team the tools to answer it consistently. Everything else, the FAQ site, the chatbots, the AI Agent, the automation rules, hangs off that inbox. If you read the rest of this comparison with that in mind, most of the differences between the two products stop being surprising.

Re:amaze reviews well, and it is worth saying so early. At the time of writing it was rated around 4.8 out of 5 on Capterra and around 4.5 out of 5 on the Shopify App Store. Ratings and review counts move week to week, so treat those as a general signal rather than a fixed fact and check the current listings yourself. What reviewers praise is consistent across both listings: the shared inbox, how quickly you can get started with the basics, the responsiveness of Re:amaze's own support team, and the way Shopify order data surfaces inside a conversation so an agent can see purchase history, spend and order status without switching tabs.

The AI Agent is a newer part of the product, and what it can do is bounded by the content you give it. Re:amaze's documentation describes it drawing on your FAQ and Help Centre articles, your saved response templates, custom AI context in the form of instructions and external URLs you point it at, and Shopify or WooCommerce product and order data. That is a genuine grounding set, and broader than a lot of bolt-on chatbots offer. The practical limit is that answer quality tracks the quality of the content you have already written, and the time you put into the AI settings, the personality and response guidelines, and the review queue for suggested answers.

The recurring criticisms in third-party reviews are consistent rather than damning, and we would rather quote reviewers than characterise the product ourselves. Reviewers on Capterra have mentioned that the knowledge base editor lacks features they expected, including direct photo uploads and syntax highlighting, that there is occasional lag, that not every social channel is covered, and that certain settings are hard to locate, with chat setup described as unintuitive for newcomers. Any of that may have changed by the time you read this, so treat those points as questions to ask during a trial rather than as settled facts about the product today.

None of this makes Re:amaze a weak product. It makes it a normal one, with the strengths and the rough edges you would expect from a mature helpdesk that has accumulated a lot of surface area over many years. The question for a buyer is not whether Re:amaze is good, because on the public evidence it clearly is. The question is whether a self-serve multichannel helpdesk is the shape of the thing you actually need.

What is BotSupport, and how does it differ from Re:amaze?

The difference is not really a feature list. It is a delivery model. Re:amaze sells you a platform and a set of capabilities, and the work of turning those capabilities into a good customer experience stays with you. BotSupport sells you the finished outcome. The build, the grounding in your catalogue, the tone, the escalation rules and the testing are done before you see it. That is the whole proposition, and if it does not appeal to you then Re:amaze is very likely the better purchase.

BotSupport is also narrower on purpose. It is an assistant on your storefront that answers product, stock, delivery, returns and policy questions using your live catalogue, and hands over to a human when it should. It is not a shared inbox, it does not triage email tickets, and it does not manage your Instagram DMs. If you want one system to run an entire support operation, that is Re:amaze territory and we will say so plainly further down rather than burying it.

Being honest about stage matters too. BotSupport is Early Access as of August 2026. There is no meaningful customer base yet, no long review history, no awards and no case studies to point at. What there is, is a build process that a person runs end to end, and pricing that reflects an early product. Anyone comparing us with an established helpdesk should weigh that properly rather than letting a comparison page talk them out of it.

It also means you should read our claims about ourselves the same sceptical way you read our claims about Re:amaze. Where we say we aim to hand over within a working day, that is a target we set for our own build process, not an average measured across hundreds of deliveries, because those hundreds of deliveries do not exist yet. Ask us how the last few builds actually went and hold us to the answer.

Who does the building and the maintenance work?

Re:amaze is explicit about its setup path in its own documentation. As documented at the time of writing, you are asked to review and customise the AI settings including personality, response guidelines, external URLs and which knowledge sources to include; to prepare your support content so that FAQ articles cover your most common customer questions and your product details are accurate; to enable the AI Agent from the bot management screen; and then to configure which channels it runs on. Every one of those steps is reasonable. Collectively they are a project, and the person doing it is usually the store owner or the one person who already answers the emails.

There is also an ongoing loop. Re:amaze's own material describes the AI Agent escalating to a human when it cannot answer, and then generating a suggested answer once the conversation is closed. Those suggestions sit in a review queue where you approve, edit or reject them, and Re:amaze describes answers entering the AI Agent's knowledge base only after you approve them. Re:amaze has also published limits around that queue, including skipped suggestions expiring after a period and a cap on how many answers you can save, so part of the job is choosing which suggestions are worth keeping. That is a sensible safety design. It is also a standing task on someone's list, every week, for as long as you use the product.

BotSupport moves that loop to our side of the fence. Because the assistant reads your live catalogue rather than a set of articles you maintain by hand, a price change or a new product is reflected without you rewriting an FAQ. Where policies change, you tell us and we update the grounding. We are not claiming a system that can never be out of date, because no such system exists. We are claiming that the work of keeping it current is ours rather than yours.

The trade is control. If you want to sit inside the settings and tune the behaviour yourself at two in the morning, Re:amaze gives you that and BotSupport deliberately does not. Some owners genuinely want the dials. Others discover eighteen months later that nobody has touched the FAQ since launch. Be honest with yourself about which of those you are, because it predicts which product will still be working well for you next year.

Does Re:amaze work as well with WooCommerce as it does with Shopify?

Credit where it is due. A lot of ecommerce support tools treat WooCommerce as an afterthought or a Zapier problem. On its published integration page, Re:amaze does not. It documents an agent being able to process refunds and set order and payment status from inside the conversation, which is the pair of actions that matter most on a support desk, alongside the customer context that stops an agent asking the customer to repeat their order number.

The platform differences are subtler than a missing integration, and we want to be careful not to invent a shortcoming that is not there. Re:amaze's documentation describes integration data as attributes pulled from each third-party platform's API, so the available fields naturally differ from platform to platform. That is how integrations generally work rather than evidence of a WooCommerce gap. If a specific field or action matters to you, the right move is to check it in a trial rather than to trust either vendor's summary, ours included.

What is fairly observable is community coverage. Shopify has the dedicated app listing, and that is where most of the reviews, most of the third-party guides and most of the community answers live. If you are on WooCommerce and something behaves unexpectedly, you are more likely to be reading generic documentation than a post from someone with your exact stack. That is a difference in how much company you have, not a statement about the integration's depth.

BotSupport builds the same way on each platform, so WooCommerce stores are not the second-class case. The assistant is grounded in your live catalogue whether that catalogue sits on WooCommerce, Shopify or a bespoke site, and the build work is comparable in each case. That is a less impressive engineering claim than it sounds, because the managed build absorbs the platform differences rather than eliminating them. Someone still has to do the awkward part. The point is that it is not you.

One caveat in Re:amaze's favour and against ours. If you are on BigCommerce or Magento, Re:amaze has documented integrations and we would not pretend to match that. We confirm compatibility with your site before we take money, and if we cannot ground the assistant properly on your platform we will say so at that point rather than after you have paid.

How do the pricing models compare?

The two models fail in opposite directions, which is the useful thing to understand. Per-seat pricing scales linearly with headcount, so a five-person or ten-person team pays five or ten times the seat price before any AI usage and before any annual-billing discount. That is fine when the seats are doing high-value work and expensive when you are adding a seasonal temp who logs in twice a week. Price your own team size on Re:amaze's own pricing page rather than relying on a worked example from a competitor, including ours.

The metered AI layer is the part buyers most often miss. Re:amaze's published AI pricing at the time of writing listed an included resolution allowance against each per-seat tier and a per-resolution charge above it. Confirm the current allowance and rate with Re:amaze, and in particular confirm whether the allowance is counted per seat or per account, because that changes the maths considerably. If the allowance scales with seats rather than with conversation volume, a small team on a busy store can work through it quickly. That is not a criticism of the price, which is competitive on a per-resolution basis. It does mean your monthly cost moves with your traffic in a way the headline seat price does not show.

BotSupport's flat managed subscription trades that flexibility away. Your bill does not move with conversation volume in the way a metered plan does, and it does not move as you add staff, because we are not selling seats at all. For a store with predictable, moderate volume that is simpler to budget. For a store that wants a full agent desk, the two are not really comparable products, and the price difference is not the reason to pick one.

Both offer a way in without commitment, and both should be verified rather than taken on trust. At the time of writing Re:amaze advertised a 14-day free trial with no credit card required and month-to-month billing. Confirm the current trial length, card requirement and contract terms on their pricing page before you rely on them. BotSupport includes a free trial period during Early Access; ask us for the current trial length when you enquire, and we will put it in writing.

What is the staff-time cost that buyers forget?

Work out your own number rather than trusting ours. Take the person who would own the setup, take their loaded hourly cost, and estimate the hours for the initial content and configuration pass plus a modest weekly upkeep allowance. Reviewers of Re:amaze frequently describe basic setup as quick and straightforward, while also mentioning that certain settings are hard to find and that some configuration feels unintuitive at first. That is a fair description of most tools in this category, and a useful signal for where your hours are likely to go.

Then add the less visible costs. Content you have to write is content that will drift out of date. Every price change, courier change or returns policy tweak is a small amendment somewhere in the knowledge base. Maintenance work that carries any friction is the kind that gets deferred and then never done, and an assistant answering from stale articles is worse than no assistant at all, because it is confidently wrong in front of a customer.

This is the honest core of the BotSupport case, and it is narrower than a marketing page would make it. We are not claiming a better underlying AI model. We are not claiming a longer feature list, because Re:amaze plainly has the longer feature list. We are claiming that someone else doing the build, and keeping the grounding current afterwards, is worth money to a store owner whose realistic alternative is doing it at the weekend.

If your organisation has a support lead with the time and the appetite for that work, the argument is much weaker and you should discount it heavily. Some teams enjoy owning their tooling and are good at it. For them, a self-serve platform with a rich configuration surface is not a cost, it is the point.

Who should honestly choose Re:amaze instead?

The clearest case is team ticketing. If several people need to see, assign, tag and answer conversations from a single queue, with internal notes and performance reporting, that is precisely what Re:amaze is built for and precisely what BotSupport does not attempt. Buying BotSupport in the hope it will run your inbox would be a mistake, and we would rather talk you out of it now than refund you later.

The second case is channel breadth. Re:amaze describes bringing email, live chat, social media, mobile SMS, VoIP, video calls and push notifications into one platform. If customers reach you across many channels and you want them landing in one place with one history per customer, a storefront chat assistant, BotSupport included, is not a substitute for that.

The third case is platform. BotSupport works with WooCommerce, Shopify and most other website platforms, but Re:amaze documents supported integrations with BigCommerce as well, and named Magento in its 2021 acquisition FAQ. If you are on either, Re:amaze has a genuine advantage and you should confirm the current state of those integrations with them directly.

The fourth case is maturity and control, and it is fair to state it plainly. Re:amaze has been in market for years, has been GoDaddy-owned since 2021, and has a substantial public review history across Capterra, G2 and the Shopify App Store. BotSupport is Early Access with essentially no customer base and no review history at all. If a long track record is a requirement for your business, or for whoever signs off software purchases, that is a legitimate reason to choose Re:amaze today and revisit us later.

The fifth case is simply preference. Some owners want to see the machinery. If the idea of a supplier holding the configuration makes you uncomfortable, that discomfort is a real cost and it will not go away because the setup was convenient.

Is BotSupport a replacement for a helpdesk?

This matters for how you frame the whole comparison. The overlap between the two products is the chat widget and the AI answering behind it. Outside that overlap, Re:amaze does a great deal that BotSupport does not, and pretending otherwise would make this article useless to the people it is meant to help.

Where BotSupport competes directly is on the quality and currency of the answers in that overlapping area, and on who does the work of getting there. Because the assistant reads your live catalogue rather than a hand-written article, price and stock changes are reflected without anyone rewriting an FAQ. We test the assistant against realistic questions before handover, which is not the same as guaranteeing it will never get one wrong, and we would not make that guarantee for any AI system including our own.

Running both is a reasonable configuration for a store that has a support team but is drowning in repetitive pre-sales and delivery questions. The assistant handles the front of the funnel, the helpdesk handles everything that becomes a ticket. It is also, admittedly, more monthly spend than either alone, and worth doing only if the repetitive volume is genuinely eating your team's day.

How do you trial both properly, or switch between them?

Keep the test honest. Include the awkward questions, not just the easy ones. Ask about a product that is out of stock, a delivery date to a Highlands and Islands postcode, a return outside the standard window, and something your policy genuinely does not cover. What you are looking for is not whether the assistant sounds fluent. It is whether it declines cleanly when it should, and escalates to a person without the customer having to repeat themselves.

Track the setup hours as you go, because they are the number you will forget by the time the invoice arrives. Note who did the work and how long the initial content pass took. If you are trialling Re:amaze, note specifically how long it took to get the AI Agent giving answers you would be comfortable showing a customer, and how much of that time went on writing content you did not previously have.

Switching in either direction should be manageable, but check the specifics rather than taking a comparison article's word for it. At the time of writing Re:amaze advertised month-to-month billing with cancellation at any time, so confirm the current terms on their pricing page before you plan around them. Check the export options in each product before committing, so you know what leaves with you.

Moving from Re:amaze to BotSupport means the knowledge base articles you wrote remain useful reference material for the build, and we would rather work from them than start from a blank page. Moving the other way means exporting your policy content and rebuilding it as FAQ articles inside Re:amaze, which is real work and worth scoping before you commit to the move.

One piece of generic housekeeping that applies whichever tool you are switching off. Check where your help centre images and attachments are actually hosted, and make sure you have copies, so your archived content stays intact after the account closes.

Where these figures came from, and how to check them

We have tried to keep a clear line between three different kinds of statement in this article. Facts sourced from Re:amaze's own material are described as documented or published, and dated. Opinions and criticisms drawn from third-party reviews are attributed to reviewers rather than asserted as product facts. Our own claims about BotSupport are marked as targets and intentions where we do not yet have an operating record to point at, because we are pre-launch and it would be dishonest to imply otherwise.

We have also avoided worked examples of what a competitor's bill would come to. It is easy to build an arithmetic example that quietly assumes the most expensive tier and ignores the annual discount, and the result flatters whoever wrote it. Your own team size, plan choice and billing cycle are the only inputs that matter, and they are ten minutes' work on Re:amaze's own pricing page.

If you find something on this page that is out of date or wrong, tell us and we will correct it. That includes corrections from Re:amaze. We would rather run an accurate comparison that sometimes points readers at a competitor than an inaccurate one that wins on paper.

Sources

1. Re:amaze pricing page — Vendor self-reported, checked August 2026. Source for Basic $29, Pro $49, Plus $69 per team member per month, around 10 per cent off annual billing, Starter $59 flat with a 500 responded conversation cap, the per-tier AI resolution allowances and per-resolution overage charge, the 14-day free trial with no card required, and month-to-month billing with cancellation at any time. Figures may have changed since.
2. Re:amaze AI Agent documentation — Vendor self-reported, checked August 2026. Source for the AI Agent's knowledge sources (FAQ articles, response templates, custom AI context including instructions and external URLs, and Shopify or WooCommerce product and order data) and the customer setup steps: review AI settings, prepare support content, enable the agent, configure channels.
3. Re:amaze blog: a fresh set of AI customer support tools — Vendor self-reported, checked August 2026. Source for the escalation-to-human behaviour, the suggested-answer review queue with approve, edit or reject, the statement that answers are added to the knowledge base only after approval, and the stated expiry and saved-answer limits on that queue.
4. Re:amaze WooCommerce integration page — Vendor self-reported, checked August 2026. Source for WooCommerce capabilities: total orders, total spend and customer lifetime, order line items and value, shipping and billing addresses, customer notes, order and payment status, processing refunds, setting order and payment status, and adding public or private notes.
5. GoDaddy newsroom: Re:amaze Joins the GoDaddy Family — Primary source for the acquisition, announced in a press release dated 6 April 2021, and for the description of Re:amaze unifying email, text, chat, social, voice and video in one shared inbox.
6. Re:amaze and GoDaddy (Re:amaze support article) — Vendor self-reported, published around the 2021 acquisition. Source for Re:amaze's statement at that time that the acquisition would not affect existing subscriptions, and that Re:amaze and GoDaddy would continue to support customers on Shopify, BigCommerce, WooCommerce and Magento. Treat as a 2021 statement, not a current commitment.
7. Re:amaze on Capterra — Third-party review aggregator, checked August 2026, when the listing showed a rating of around 4.8 out of 5. Source for commonly cited reviewer pros (ease of use, shared inbox, Shopify order data in conversation, value, responsive support) and cons (knowledge base editor lacking photo upload and syntax highlighting, occasional lag, social channel gaps, settings that are hard to locate). Scores and review counts change continuously.
8. Re:amaze AI Helpdesk and Chat on the Shopify App Store — Third-party marketplace listing, checked August 2026, when it showed a rating of around 4.5 out of 5 and the $29 to $69 per month plans plus the $59 Starter plan shown to Shopify merchants, with a 14-day free trial. Scores and review counts change continuously.
9. Re:amaze homepage — Vendor self-reported, checked August 2026. Source for channel coverage (email, AI-powered live chat, social media, mobile SMS, VoIP, video calls and push notifications), the integration list including Shopify, BigCommerce, WordPress, Stripe, Zapier and others, and the beta labelling of the AI Agent at the time of checking.

Details on Re:amaze 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.