Support for your shop that answers from the order, not a script.
“Where is my order?” The AI opens the real record and answers in seconds — the status, what shipped, the carrier’s date. Your operators keep the conversations that need a person.
Free to try · no credit card · order and stock lookups on a paid plan
What actually fills a shop’s inbox.
Three questions, over and over. Every one of them is already answered somewhere in your shop — and the third one isn’t a support ticket at all, it’s a sale you either make or don’t.
Swipe — 3 of them
The question you answer more than any other
“Where is my order?” The answer is already sitting in the order record and the carrier’s tracking. Somebody copies it out of one tab and into another, all day — and the customer waited three hours for a line of text.
The return question you can’t get wrong
“Can I still send this back?” Answer it too generously and you’ve given away a refund you never owed. Get it wrong the other way and it’s a chargeback, or a one-star review that stays up for a year.
The one that isn’t a support ticket
“Is this in stock in medium?” Nobody waits for that. They ask, they get silence, and they buy it somewhere else — a slow answer here doesn’t cost you a ticket, it costs you the order.
Every answer comes from your shop, not from a script.
Connect your store once and the AI looks up the real record before it writes a word — the order, the tracking, whether the size they want is actually on the shelf.
One late order, and the one thing it wouldn’t promise.
The order, the delay and the delivery date all come out of your own systems — the AI reads them, it doesn’t invent them. The end is the more useful part: the customer asks for something the returns policy doesn’t grant, and the AI doesn’t grant it either.
Four things happened there. It asked for the order number instead of guessing at one. It read the record itself — and gave the carrier’s estimate as the carrier’s, not as a promise. It answered the part the returns policy covers and stopped dead at the part it doesn’t. And it only mentioned a person after one had actually been paged.
Illustrative conversation. The AI answers from your own data — it will not state a status, a price or a date that nothing backs up.
Build one from your own store
What it is told never to say.
Accuracy is what every vendor claims. This is the shorter list — the things this one is told never to say in your shop, and the layer that catches it if it says one anyway.
Swipe — 4 rules
It won’t invent a delivery date
It reads the carrier’s estimate and gives it as the carrier’s, or it says it doesn’t have one. “Should be there Thursday” is the sentence that writes tomorrow’s angry follow-up, and it is not allowed to say it.
It won’t say the parcel shipped
Or that a refund has gone through, or that a return was received. A status or an amount that nothing in your data supports is blocked before it is sent — whatever the assistant was told, and however the customer asked.
It won’t bend your returns policy
No goodwill discount, no waived postage, no “I’ll make an exception this once.” It answers what your policy says and hands the exception to a person, because giving away money is your call and not a bot’s.
It won’t guess whether something is in stock
If a lookup can answer it, it answers from the lookup. If nothing can, it says so plainly. What it will not do is turn “probably” into “yes, we have that in medium” — and leave you cancelling the order that answer just won you.
The first, third and fourth are instructions your assistant follows. The second is enforced by the platform: a status or an amount that nothing in your data supports is blocked before it is sent, whatever the assistant was told.
The first message is what an ungrounded assistant sends to close a refund thread. It never reached the customer. The second one did. Every block is written to an audit log and the conversation is escalated — so you find out, not your customer.
Your checkout is open at midnight. So is the assistant.
The AI takes every new conversation from the first message — it isn’t cover for when your staff are out. And a chat somebody claimed and then left is worse than one nobody touched: nothing else is going to pick it up.
Point it at your shop. It writes the knowledge base.
The first hour is usually why this never gets done. Here it’s a paste, and then an afternoon reading what it wrote.
Swipe — 3 steps
Paste your URL
It reads your public pages — your delivery page, your returns policy, your size guide, your FAQ — and writes real knowledge-base articles and real FAQ entries, plus a first draft of your assistant’s instructions, in your language.
Nothing it can’t prove
The articles are your own pages, in your own words. Where it draws a conclusion about your shop it has to point at the exact sentence that supports it — anything it can’t, it drops rather than guesses.
Connect your order lookup
Bring the endpoint your own order page already calls and we wire the lookup with you. Nothing to hand out? Point it at the tracking page instead and it reads that.
The question arrives wherever the customer already is.
Web chat, WhatsApp, Telegram, Viber, email and a hosted helpdesk, with the same assistant, the same knowledge base and the same order lookup behind every one of them. It all lands in one inbox, so nobody has to check four places to find out whether the customer was already answered.
Questions, answered.
Black Friday triples my volume for a week. What happens?
Will it give away a refund or waive postage to keep someone happy?
A customer sends a photo of a smashed mug. Can it do anything with that?
It told someone an item was in stock and it wasn’t. What then?
Half my orders come from marketplaces. Does it help there?
I sell into five countries. Do I have to write my returns policy five times?
Stop answering “where is my order?” by hand.
Point it at your shop and it writes its own knowledge base — free to try, no credit card.