You · 09:14
Where is order SHOP-1001? Phone +1 (555) 010-4567.
AI support for online stores
It resolves what your data can answer. It invents nothing.
The agent looks into your orders, stock, or shipping and answers with specifics. Your team is left with only the cases that really need a person.
Create an account, paste your store address, and the agent reads your public pages. Connect orders and stock whenever you are ready.
- Sees your orders
- No repeating for the customer
- What is missing goes to engineering
- No per-agent fees
Interface illustration
Where it usually breaks
Support keeps failing in the same places.
-
It answers from the help center
The customer asks about their order and gets a generic article. Nobody ever looked inside your systems.
-
It would rather make it up
With no real answer, it fills one in. The customer leaves with a date or a price that exists nowhere.
-
The operator starts from zero
The customer explained everything to the bot. The operator then reads the whole chat to learn what the customer already said twice.
-
You cannot trace what it did
A customer says the bot promised something. The transcript will not tell you whether it pulled that from your data or made it up.
-
Nights and weekends wait
The question arrives at ten in the evening, the answer goes out in the morning. The customer has time to order elsewhere.
-
Closed before the customer finished
Someone ticks the conversation off as resolved because it counts nicely. The customer writes again, angrier this time.
One case, three roles
What the customer says once, nobody digs up again.
One story from three sides: what the customer sees, what the operator gets, and what engineering takes away.
Customer
The customer asks where the order is. The bot looks it up. It cannot cancel, so it says so and hands off. No invented happy ending.
Interface illustration
Operator
The operator does not open a blank chat like a detective. They get a summary: what she wanted, what the bot tried, where it stopped.
Inbox / ConversationJana · 09:14
Cancel it and refund me. I changed my mind.
Summary · 09:14
TranslatedJana wants to cancel order SHOP-1001 and get a refund. Identity checked with order number and phone. The parcel is in transit with DPD. Order status came back. The agent cannot cancel or refund. Next: an operator decision.
Interface illustration
Engineer
What the bot could not do does not fall through the cracks. Engineering sees how often it happened and what to build.
Missing
Cancel in-transit order and refund
Seen 14 times
- 01
Problem
Support can look up an order, but cannot cancel or refund when the customer asks after shipment.
- 02
Implement
Add cancelOrder(orderNumber, phone) and refundOrder, gated on fulfillment status.
- 03
Acceptance
A verified customer can cancel an eligible order without an operator, or the bot transfers instead of guessing.
Maybe resolved
Looks like cancelOrder covers this. Enable it for customer chat, then mark the ticket done.
Interface illustration
Inbox for the team
Every conversation has an owner and a status.
A handoff from the AI does not land on a shared pile nobody picks up. It lands on one person, and it is clear where the conversation stands.
On the inbox
Two people online
Queue
Jana · SHOP-1001
Wants to cancel an order
Internal note · Klára · 09:14
@petr Jana still has an open complaint from last week, handle both together.
Interface illustration
Assignment and statuses
New, waiting on the customer, resolved. You see who owns it, so nobody answers the same thing twice.
Who is on the inbox
You see who is signed in. A handoff from the AI lands on whoever has the fewest open conversations.
Internal notes
A note stays inside the team, the customer never sees it. Mention a colleague and they get a notification.
What Cusu does
For customers, the team, and management. Not just a chat window.
Customer
Answers from your data
Order status, stock, shipping. Not a generic help article.
Chat, dictation, call
Customers can talk instead of typing. Same agent everywhere.
The customer’s language
It answers in theirs, you read the thread translated.
Operator
A handoff with a summary
The operator knows what happened before writing a word.
Work sharing
A handoff lands on whoever has the fewest open conversations.
Data on the ticket
The operator sees exactly what the agent found in your systems.
Management
Metrics
How many conversations the AI closed and how many people did.
Tags from a rule
Write the rule as a sentence and tags land on their own.
Several shops
Each with its own language, voice, and inbox.
Engineering
Connect your systems
Orders, stock, shipping. Method by method.
Missing capabilities
They land as specs, with a count of how often they were needed.
A rule in one sentence
Write it in the internal chat, it holds from the next conversation.
Control and logging
You see what the agent did. And what it may not do.
The agent is not a black box. Every answer carries a record of where the data came from, and you decide what it may touch at all.
You can trace every answer
For each answer you see where the agent looked, when, and what your systems returned. When a customer quotes it back, you can find it.
You decide what it may do
The customer agent and your internal team have different rights. What you do not allow, the agent will not do.
It changes things only on request
Reading data is one thing, changing it is another. It makes a change only where you allowed it and where the customer clearly asks.
Lookup record
Order SHOP-1001
Customer chat · 09:14
GET /orders/SHOP-1001
240 ms 200Status: in transit · DPD
GET /shipments/15501234567890
180 ms 200Tracking found and sent to the customer.
POST /orders/SHOP-1001/cancel
BlockedNot enabled for customer chat. The agent said so plainly and handed off.
It changes things in your systems only where you allowed it.
No long project
Four steps. A few minutes, not a quarter.
-
The site is fetched automatically
Tone, hours, policies, contacts from the public pages. The agent is not allowed to invent the rest. When something changes on your site, you refresh it in one click and see what gets overwritten before it happens.
-
Say what it may do
Connect orders, stock, shipping. For each, choose whether it can use that with customers, with your team, or both. Nothing else.
-
Write it once
You write the rules once. “Always collect order number and phone. Never guess.” The next customer already gets that.
-
Put it on your site
Your developer adds one line to the site. Chat, dictation, and calls are the same agent.
Libraries for Swift, Kotlin, React Native, and Flutter are on the way.
import Cusu from '@cusuai/web-sdk';
Cusu.initialize({
group: 'your-group',
apiUrl: 'https://api.cusu.ai',
apiKey: 'pk_…'
});Pricing
Five cents a conversation. Not a dollar a resolution.
Top up credit and two things come out of it: what the AI consumes at cost and $0.05 for every conversation a customer opens. Nothing else. The big tools today typically charge about a dollar per resolved conversation, plus a monthly fee for every operator.
- No fee per resolution
- No per-agent fees
- No setup fee
Credit
$86.40
Spent this month
$13.60
- AI usage $9.25
- 87 conversations × $0.05 $4.35
What the AI usage is made of
- Chat $5.98
- Voice $1.90
- Translations $0.82
- Dictation $0.55
Questions we get
What people ask before they try it.
- Does it answer at night and on weekends?
- The agent runs the same way around the clock, so a question at ten in the evening does not wait until morning. What it cannot finish goes to the inbox with a summary, so the team does not find a bare unread email.
- Can the customer reach a person?
- A handoff is a normal end to a conversation, not a failure. When the customer asks for a person, or when the agent cannot handle the request, the conversation moves to the inbox and the AI stops replying in it.
- What if the agent gets something wrong?
- It does not guess. When the answer is not in your data or on your site, it says so and hands off. Every answer also keeps a record of where it looked and what your systems returned, so you can check it afterwards.
- We have no connection to orders. Is it worth starting?
- It is. The agent can answer from your website and from rules you write as plain sentences. Orders, stock, and shipping can be connected later, operation by operation.
- Does it work on email or inside Shopify?
- Not yet. Today it runs as chat, dictation, and calls in the widget on your site. Email, a Shopify app, and mobile libraries are on the way and we do not present them as done.
- How long does it take to launch?
- The site is fetched while you create the account and the agent goes through dozens of pages. You then review what it found and tick off what should hold. Your developer puts it on the site with one line.
- What language does the agent answer in?
- You set the default language per shop, voice included. The operator reads a foreign-language thread translated and answers in their own language.
- What happens to customer data?
- Conversations and whatever the agent pulled from your systems stay in your account. The agent only reaches operations you switch on, and every call shows what it asked for. Processing terms come with the contract for the app.
On your site
Start with the site you already have.
Onboarding fetches your public pages; orders and stock come next. The address from this field travels with you into onboarding.
We pass the address to onboarding, where the site gets fetched. Nothing is crawled from this page.
Cusu is new. This page describes what the product does today, not what we plan.
Interface illustration