Relay Panel answers from your products, your pages and your policies — with a link to whatever it used. The instant it cannot support an answer from your own content, or the customer asks for a person, it hands over and stops. No guessing, no loop, no maze.
Not open to signups yet. Nothing to install to look.
Not promises, and not switches an admin can flip on a bad day. Each one is a thing the software has no way to perform.
Every factual reply has to rest on something from your own site, and carries the link. If it cannot find one, it does not write a plausible answer more slowly — it hands the conversation to a person and says so.
“Talk to a person” is on screen from the first message and works on the first tap. No “let me try one more thing”, no qualifying questions, no ticket form, no hours you have to be inside. Asked for, granted.
The moment one of your team joins, the assistant stops answering that conversation — permanently, enforced in the database rather than requested in a prompt. Nobody gets handed back to the bot.
Most support questions have an answer already sitting on the merchant's own website. Those get answered in seconds, at three in the morning, without anybody being awake. The rest — the judgement calls, the exceptions, the money — go to a person straight away rather than after a bot has wasted the customer's time.
“Is this in stock?” · “What is your returns policy?” · “Where is order 1043?” · “How much to ship two of these to Springbrook?” · “How much have I spent with you?” — all of it is in your store, cited, and sent as soon as the customer asks.
“Can I get a refund?” · “What would freight to Cheyenne cost?” · “Can you do better on price?” · anything your site does not cover. No attempt, no stalling, no invented number.
And it looks before it gives up. A handoff with no search behind it is refused and handed back to try again — because “this needs a person” about something sitting on your own returns page is not caution, it is a customer waiting for nothing.
Prefer to watch it first? One setting holds every reply for approval instead. What it never does, in either mode, is answer anyway.
Most support bots are built to deflect — to keep you talking to software long enough that you give up. This one is built the other way. It tells customers what it is in plain words, offers a person before they ask, and hands over the moment anyone wants one.
It also hands over on its own: when it is not certain, when the answer is not on your site, and whenever money or a commitment is involved.
A handoff costs you a few minutes. A confident wrong answer costs you the customer.
Half the questions a chat widget receives are about whatever the customer is looking at. “Is this in stock?” — this. Relay Panel reads the page they opened the chat from and answers about it, rather than asking which product they mean and losing them at the second message.
Your team sees the same thing: whether the customer is still on the site, and the trail of pages behind them, updating as they move.
Only during a conversation, never for a visitor who has not started one, and the address is cut back to the page before it is stored — no order keys, no reset tokens, no tracking parameters.
A chat only delivers itself while somebody is standing there, and they close the tab constantly — usually while your agent is still typing. Relay Panel notices, and sends that reply to them by email instead, so it is read rather than sitting in a browser tab nobody will open again.
The composer says which one is about to happen before you press send.
The email is signed; the chat message is not. Nobody signs off a two-line chat message with a job title and a toll-free number.
northwind-supply-a83f19c204@in.relaypanel.iosmtp.yourprovider.com : 587The assistant does the reading, the looking up and the first draft. Your team does the judgement — which is the part they are good at and it is not.
Stock, policies, delivery, order status — answered and cited before anyone opens the thread. What reaches your team is what actually needs them.
Every tool it ran, how long each took, and the pages it quoted — attached to every reply, sent or held. You can audit what it told a customer and why.
Type into any conversation and it becomes yours. The customer is told a person has joined, by name, and the assistant stops on that thread for good.
When it hands a conversation over and one of your team answers, closing the thread keeps that answer. The next customer asking the same thing gets it instead of a queue.
Reject a draft and say why. That sentence goes into its instructions for your company and it reads them before writing anything else. Visible, and removable.
The inbox updates itself — no reloading to see whether a customer replied — and Chrome will tell you when one writes while the tab is in the background.
Products, attributes, stock, pages, policies. Every fact in a draft traces to something of yours, with the citation attached — and if your site does not cover the question, it says so and fetches a person instead of inventing an answer.
Claude supplies the reading and the writing. Your store supplies the facts.
Everything it doesThe absences are the design. Each is a missing code path, not a switch — because a switch can be flipped by someone who does not understand it, or talked into by a customer who does.
There is no code that moves money. A refund request gets your returns page and a person.
LTL depends on freight class, pallet dimensions and accessorials your store does not hold. It opens a task for a human instead of inventing a number.
It cannot even mark one cancelled. That is a person's call, in your store.
Ask it directly and it tells you. It has no persona designed to blur that.
Pricing and signups open when it is genuinely ready. Leave an address and you will hear once.