Checks your systems
Finds the order, the charge or the account where they actually are, not in a list of FAQs.
AI agents that act in your systems and verify every change.

Hi, I was charged twice for my last order. Can you refund one?
Built for support teams in
Qopper checks your systems, applies your rules, makes the change and verifies it. All in the same conversation.
Finds the order, the charge or the account where they actually are, not in a list of FAQs.
It only does what you allow, up to the amount you set. Everything else is approved by your team.
Confirms in the system that the change went through. Only then does it tell the customer.
A chatbot answers questions. Qopper goes into your systems, makes the change and confirms it's done.
Your business's orders, charges and documents. You choose which actions it can use, and up to what amount.
Agent actions
Cap per action
Anything above it, your team approves
What needs a person lands in the tool they already use, with what it checked and what it proposes to do.
Your team sees what was looked up, what was done and how it was verified, without reading the whole chat.
Every step is logged. It only says “done” when the system confirms it.
1async function refund(charge: string) {2−return reply("I'll look into it")3+const r = await stripe.refunds.create({4+charge5+})6+if (r.status === "succeeded")7+return reply("Done, refunded")8+return escalate(r)9}
WhatsApp, email, your website's chat and your app. The same agent with the same rules, and everything lands in the same inbox.
The questions change, the work doesn't: look things up, decide and act in your systems.
Shopify, Stripe, HubSpot, Zendesk and more. And if your system has an API, it connects too.
Step by step, with your cases in front of us: the agent serves no customer until it passes your tests.
We go through your cases with you and decide what the agent resolves and what goes to your team.
We connect your systems. Every action has its permission and, if it moves money, its cap.
The agent starts as a draft and runs your test cases. If any fails, it doesn't get published.
It serves customers on your channels, and every step is logged for your team to review.
What your security team wants to know, answered from the start.
What your customers write is seen by your team and no one else. No other company can reach one of your conversations.
We don't train models on them, and the providers we use can't either.
Your customers' data and your keys never show up in any of our internal logs.
Ask for your data whenever you want. If you close your account, we delete it within 30 days, except what the law requires us to keep.
Have another question?
We go through your cases with you and tell you what's in and what isn't, before you sign anything.
Book a call with the foundersIt resolves what has a system behind it that it can look up and an action you turned on: an order, a charge, a plan change. Anything over your limit, outside your knowledge or that needs judgment reaches your team with the case already investigated and a proposal ready.
Shopify, Stripe, HubSpot, Zendesk, Intercom, Notion, Google Calendar, Slack, Jira and Linear, among others. And if your system has an API, that too: you describe the action, set its limit and test it before turning it on.
Yes. Each action is turned on or off per agent and has its own permission: automatic or with approval. Refunds have a cap: below it the agent does them on its own; above it, someone on your team approves.
It's an automated system and it can make mistakes. That's why it never says something is done until it has checked it in the system, it doesn't make up a policy you didn't give it, and everything it does is logged step by step for your team to review.
Yes. An agent starts as a draft and doesn't serve anyone until you publish it. Before that you can run your test cases on it: if any fails, it doesn't get published.
Your website chat, WhatsApp, email and phone, all in the same inbox. It speaks Spanish, English and Portuguese, and can detect the customer's language.
No. Qopper doesn't train any model on your data, and the providers we use receive each message only to answer that request, under terms that exclude training.
Answering and escalating: days. Taking actions in your systems depends on how many you connect: each one is connected and tested separately, and it isn't turned on until it passes.
Agents that resolve, not deflect: they act in your systems, verify and respond.