Sylius
A chatbot on the storefront and an Email Assistant in your inbox, both answering from your live store. We connect through the Sylius Admin API you already have, so nothing ships inside your application.
A Sylius store is software your team owns, and every third-party bundle in the composer file is a thing somebody has to test on the next minor version and explain to whoever inherits the project. There is no Sensbot bundle for Sylius, and there does not need to be. Sylius already ships an Admin API, so during onboarding we connect the assistant to your store with credentials rather than code.
Once that connection is live, answers are written from real data: orders and their state, shipments and payments, products and stock, and customer records. A shopper asking where their parcel is gets the order, the shipment 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 here is coupled to your Sylius version. No bundle, no migration, no entity extension, no upgrade path to babysit. If you rebuild the storefront next year, an API client and a mailbox are still the only two things this depends on.
What works today
Connects to Gmail, Outlook or IMAP. It matches the incoming email to the order it is about, pulls the state, the shipment and the payment 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. Set up with you rather than handed over as a package to install, and delivered on the front end as a single script tag in your Twig layout.
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 state, the payment and the shipment 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 install, 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 during office hours. 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. It is not there to replace your team. It is there for the hours your team is asleep.
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 state, the shipment and the payment, 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, payment and invoice queries. The assistant finds the order the customer is writing about and answers from it.
Products, variants, prices and stock come from your store, 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 nothing goes into your composer file. Sylius already ships an Admin API, so during onboarding we connect the assistant to your store with an API client rather than a package. The only thing that touches the storefront is the script tag that renders the chat widget.
Through your Sylius Admin API, with an API client you issue and scope yourself. Once connected, chat answers and email drafts are written from live data: orders and their state, shipments and payments, products and stock, and customer records.
There is nothing in your application to break. Nothing is compiled into your build, nothing extends your entities, and no service depends on a framework version. If the API client and the mailbox still work after an upgrade, so does this.
Yes. It matches the message to the order, reads the state, 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.
Speed. Your XML feed loads the full catalogue, prices and variants on day one, which is the fastest way to get a chatbot answering product questions well. The API connection is what adds orders, stock and customers on top.
The same way. You keep the storefront, we keep the assistant, and the only shared surfaces are an API client and a mailbox. If you run several client stores, our partner program covers the commercial side.
That is enough to show you what this answers on your own build, running on your own data.
100+ customers across Europe. Every email reply is a draft until somebody on your team sends it.