Magento
A chatbot on the storefront and an Email Assistant in your inbox, both answering from your live store. We connect through your Magento REST API during onboarding, so nothing is installed in the application.
Magento stores are heavy, and every extension is a thing somebody has to regression-test before the next release goes out. There is no Sensbot extension, and there does not need to be. Magento already ships a REST API, on Open Source and on Adobe Commerce alike, so during onboarding we connect the assistant with an integration token instead of code.
Once that connection is live, answers are written from real data: orders and their status, shipments and tracking, credit memos and refunds, products and stock, and customer records. A shopper asking where a parcel is gets the order, the carrier and the date. An operator opening the inbox finds the reply already written around it.
Two products run on top of it. The Email Assistant reads the mailbox your team already answers from, over Gmail, Outlook or IMAP, and leaves the drafted reply in your drafts folder. The Chatbot answers on the storefront, in the customer's own language, at whatever hour the question arrives.
Nothing is deployed into your codebase, so nothing has to survive your next upgrade. An integration token and a mailbox are the only two things this depends on, whether you are on Magento Open Source or Adobe Commerce.
What works today
Connects to Gmail, Outlook or IMAP. It matches the incoming email to the order it is about, pulls the status, the shipment and the credit memo from your store, and writes the reply into your drafts folder. Tone comes from your site content, your policies and the replies your team has already sent. Your operator reviews and sends.
Answers product, availability, shipping, returns and payment questions from your catalogue and your live stock, across every store view you run. Set up with you rather than handed over as an extension, and delivered as a single script tag in your theme.
Show first
Both examples are written for this page. They are not customer transcripts, and no customer data appears anywhere on this site.
The order, the credit memo and the refund date are read from your store at the moment the draft is written. Nobody opened the admin panel to look them up, and nothing was guessed.
Done for you
There is nothing to deploy, so setup is a short piece of work we do with you and your developers.
Plans start at €49 a month and are listed on the pricing page. Because the connection is set up rather than self-served, most stores on this route start on done-for-you, from €390 a month, where we set it up, tune it and keep it running.
Why it pays
The question that decides a sale rarely arrives at eleven in the morning. It arrives late in the evening, from somebody who has already filled the basket and wants one detail confirmed before paying. Is it actually in stock. Does it ship before Friday. Can I send it back if it does not fit. Nobody is at the desk, the answer does not come, and the tab closes.
A chatbot that can see your stock and your delivery terms answers that in seconds, at any hour, in the customer's own language, and on a multi-store-view Magento build it answers from the right catalogue and the right policy each time.
The second place is the morning queue. Support mail repeats itself, and almost every case starts with the same unpaid work: find the order. When the draft already carries the status, the shipment and the refund, that work is gone, and the job becomes reading replies, fixing the few that need it, and sending.
What changes
Delivery questions, dispatch dates, shipment tracking, credit memos and refund timing. The assistant finds the order the customer is writing about and answers from it.
Products, variants, prices and stock come from your store, per store view, so an evening availability question gets a real answer instead of a promise to check tomorrow.
Every email reply lands as a draft in your drafts folder. Nothing goes to a customer that somebody on your team has not read first.
No, and you do not need one. Nothing is deployed into your codebase. Magento already ships a REST API, so during onboarding we connect the assistant with an integration token created in your admin panel. The only thing that touches your storefront is the script tag that renders the chat widget.
Through the Magento REST API, using an integration you create under System, Extensions, Integrations and scope yourself. Once connected, chat answers and email drafts are written from live data: orders and their status, shipments and tracking, credit memos and refunds, products and stock, and customer records.
Yes. The REST API and the integration flow are the same on both, and the connection is made the same way. Where your edition adds features on top, we cover what your API actually exposes and we agree that at the start rather than assuming it.
Yes. It matches the email or chat message to the right order, reads the status, the shipment and the tracking number from your store, and writes the reply. For email that reply waits in your drafts folder until an operator sends it.
Yes, and it is one of the better reasons to do this. The assistant answers in the language the customer wrote in, from the catalogue and the policies that belong to the store view they bought from. More on that in multilingual support.
Plans start at €49 a month and are on the pricing page. Since the store connection is set up with you rather than self-served, most Magento stores start on done-for-you, from €390 a month, where we set it up, tune it and keep it running.
That is enough to show you what this answers on your own store, running on your own data.
100+ customers across Europe. Every email reply is a draft until somebody on your team sends it.