an AI assistant for live support
It looks before it answers.
It answers your customers in live chat. First it checks your panel and your rules; when unsure it asks, and when the call is yours it goes to your team.
Viewing: onChanges: none
- Request status
- Pending
- Requested at
- Yesterday 21:40
- Amount
Nothing can be changed from this screen.
- Checks your panel, can’t change it
- Never quotes a figure without a source
- Hands what it can’t do to your team
Blue thread: where the answer came fromGreen: from your team (scenes 05, 06 and 08)
What does it do?
Nine headings; pick one and its screen opens below.
01
Understands text and images alike
When unsure, asks instead of guessing
18 capabilities · see the scene02
Checks your admin panel, never changes it
Sends a missing payment straight to your team
14 capabilities · 1 planned · see the scene03
Knows your site and your team’s notices
Takes rules from your site and team
16 capabilities · 1 planned · see the scene04
Talks like a person, never loses the thread
Writes briefly, drops stale replies
19 capabilities · see the scene05
Opens a work card, relays the decision
Your team’s note reaches the customer politely
25 capabilities · see the scene06
Works in the same chat as your agents
Steps aside when your agent joins
10 capabilities · see the scene07
No wrong facts, no empty promises
Every answer gets a final check
13 capabilities · see the scene08
Secure, resilient and auditable
Logs every answer, covers every outage
19 capabilities · 1 planned · see the scene09Planned
Set up around your company
A tailored setup is planned
12 planned items · see the scene
01
Understands text and images alike
It reads every message and every image first; when unsure it doesn’t guess, it asks one clear question.
One clear question
Topic
PaymentWithdrawalPromotionAccountTechnicalComplaint
Incoming image
- Document type
- Screenshot
- Requested
- Payment receipt
- Date visible
- No
- Result
- Not the requested document
02
Checks your admin panel, never changes it
When the answer lives in your admin panel, it looks there first; if action is needed, your team gets a card.
Viewing: onChanges: none
- Payment record
- Not found
- Last payment seen
- Account status
- Open
Nothing can be changed from this screen.
Sees
- Request status
- Payment record
- Account status
- Promotion terms
Never does
- Approve
- Cancel
- Change an amount
Payment not showing · a card went to your team Scene 05 →
03
Knows your site and your team’s notices
It never quotes figures or rules from memory; it reads them from your site and your team’s approved notices.
Your site · Promotion terms
Weekend promotion. To take part, a payment must have been made in the same week. Once the terms are met, our team adds the promotion to the account.
Team notice · approved · today
Bank transfer payments are closed today. Expires on its own when the time is up.
Similar chats · tone
How your agents answered this before: terms first, then open methods. Figures are never taken from here.
04
Talks like a person, never loses the thread
It writes short and clear, and knows where the chat left off, who wrote last and how much time has passed.
3 messages · one reply
3 hours later
How it writes
- Uses her name
- Greets only once
- No repeating old news
Conversation state
- Topic
- Payment not showing
- Last said
- Receipt with the team, being checked
- Last to write
- Customer
- Time passed
- 3 hours
05
Opens a work card, relays the decision
What it can’t handle reaches your team as a complete card; your team’s short note returns to the customer, politely and intact.
1A card reaches your team
#M-0000Document check
- Requested
- Payment receipt
- chat
- Received
- Receipt, two pages
- attachment
- Payment record
- Not found
- panel
- Chat summary
- Payment doesn’t appear in the account.
- customer
Receipt · page 1Receipt · page 2
2Your team decides in a short note
Your team checks the receipt on the card
- Page 1readable
- Page 2unreadable
Team decisionTeam: page 2 unreadable, reject
Closed
Decision relayed to the customer · 14:12
3Your customer gets it in plain words
Deniz, every page of the receipt has to be readable for the check. Because the second page can’t be read,1 our team couldn’t accept the request as it is. If you share a clear copy, it will be reviewed again.rulereasondecisionway out
Please look again, I did pay.Our team’s decision stands as it is. When you share a readable receipt, your request goes back to the team with the new information.
06
Works in the same chat as your agents
With a note the customer never sees, your agent can pause, steer or take over; it knows when to step back.
Hidden from customer · Agent
@ I’ll take this one
Notes to the assistant start with @; unmarked notes stay between your team.
Agent in chat
Agent wrote @ continue · assistant picked up where it stopped
Your agent can do three things
- PauseThe assistant stops writing in that chat.
- SteerIt tells the customer your note in its own words.
- Take overThe chat moves to your agent; the assistant steps back.
07
No wrong facts, no empty promises
Every sentence gets a final check; unsourced figures, unconfirmed outcomes and empty promises never reach the customer.
Draft · not sent to the customer
Your promotion has been added to your account.
Final check: unconfirmed outcome, removed
Your site · Promotion terms
Never reaches the customer
- A figure with no source
- An unconfirmed outcome
- A promise nobody will keep
Only the faulty sentence is fixed; the rest stays.
08
Secure, resilient and auditable
It protects data, never strands a customer when something breaks, records what each answer relied on and tests every update first.
- 14:02Deniz, your request is pending1Your panel · Request status
- 14:04There’s no record of this paymentYour panel · Payment record
- 14:06To join, you need to have made aYour site · Promotion termsTeam notice · approved
- 14:12Deniz, every page of the receiptTeam decision
When something breaks
- No answer could be produced
- A backup path is tried
- Handed to your team
- No customer left waiting
Pulse
- Live chat connectionwatched
- AI accesswatched
- Panel sessionwatched
- Serverwatched
Update path
- Tested first on an exact copy of live
- Goes live
- Rolls back to the previous version if needed
Data
- The database is backed up automatically every night
- Assistant memory clears after 7 days
Throughout this tour, the assistant changed nothing in your panel. It looked, it asked, it passed things on.
09
Set up around your company (Planned)
Planned
The steps below are not in use yet.
A step-by-step setup for new companies is planned, built on your own data and proven at every step.
Each step moves on only with proof
- Intake form: your details will be collected up front
- Everything specific to you will sit in one package
- With a setting missing, it won’t start; it will say which
- Your site will be scanned; rules and chat archive loaded
- An alarm drill, a test with simulated customers and a load rehearsal will follow
- Every company will get its own server and setup
- Launch will be gradual, with a closely watched first week
Other planned items
Full list.
The tour shows the highlights; everything it does today is here, with planned items marked. Pick a heading to open it.
- Tells more than 40 topics apart
- Separates what it can answer from what needs your team
- Never guesses on a vague message, asks once
- Catches the status question hidden in a message
- Notices when the topic changes and moves on
- Notices a misunderstanding and rereads the chat
- Handles the complaint first when it comes with a request
- Understands abbreviations and hurried typing
- Recognises requests that aren’t support, points the right way
- Picks the username out of the chat, not amounts
- Never asks for what it can already see
- Recognises which document an image actually is
- Reads amount, date and sender off a receipt image
- Holds back the wrong document, says what’s needed
- Never asks twice for a file already sent
- Reads an image in light of the customer’s problem
- Doesn’t pile images from closed cases onto your team
- Gives a single-use, time-limited upload link for documents
- Connects to your panel with view-only access
- Reads a withdrawal request’s status and tells it
- Reads the rejection reason; if none, invents nothing
- Checks whether a payment reached the account
- Sends a missing payment to your team immediately
- Watches payments on open cards, alerts customers still in chat
- Sees account locks and identity verification status
- Sees a promotion’s status and what’s left to qualify
- Must check the panel before opening a card
- Finds the right person, never guesses between similar names
- If the panel doesn’t answer, never says “no record”
- Alerts your team if the panel connection drops
- Keeps internal record fields away from customers
- Uses the panel record to tell new from repeat requests
- Will explain panel corrections using your site’s ruleplanned
- Learns your site whenever your team asks
- Sums up for your team what changed after each scan
- A broken scan can’t erase correct information
- No rule in a promotion’s text gets lost
- Works out promotion terms from the rule, not memory
- Suggests only payment methods that are open
- Changing figures come from one place, old ones vanish
- Gives your current official address, never makes one up
- When told “it’s on the site”, searches your rules page
- Your unwritten house rules are kept separately and safe
- Your team writes one line; approved, it applies
- No notice reaches the assistant without approval
- Time-limited notices expire on their own
- Never volunteers internal information to customers
- Takes only the tone from your past conversations
- Doesn’t trust figures found in old conversations
- Will remember customer-specific exceptions in later chatsplanned
- Writes short, clear and human
- Answers several quick messages with one reply
- Drops a stale reply if the customer wrote again
- Treats a short reply as the open topic
- Doesn’t say “hello” again mid-conversation
- Knows time has passed, doesn’t repeat old news
- Lets a waiting customer know right away it’s on it
- Never writes “please wait” a third time
- Never sends the same sentence twice in a row
- Tells thanks, okay and goodbye apart; knows when to stop
- Replies to small talk briefly and naturally
- Fixes Turkish suffix slips without changing meaning
- Uses the customer’s name, never their username
- Remembers the previous chat, doesn’t ask everything again
- Tells apart two people writing from one device
- Notices anger and escalates urgent cases to your team
- Never brushes off a customer who asks for a person
- Answers repeated chasing based on where the issue stands
- Stands behind your team’s decision when challenged
- Opens a work card readable at a glance
- Collects what’s needed before opening a card
- Every fact on a card shows its source
- Flags a name that doesn’t match the record
- Receipts and files travel with the card
- One card per issue; urgent updates are noted on it
- Only useful information reaches your team channel
- Turns your team’s short note into polite words
- Understands your team’s shorthand and one-sign notes
- Figures, conditions and direction never change in transit
- A one-word rejection never reaches customers bare
- Doesn’t push post-decision arguing back to your team
- If your team’s note is unclear, it asks them
- Also reads edited team notes and photo captions
- Same decision never sent twice; a change is flagged
- Never sends two messages that contradict each other
- A decision survives even if the customer leaves
- Doesn’t cut into another topic with a pending decision
- Your team’s reply always reaches the right customer
- Doesn’t make your team re-answer a still-valid decision
- Fetches information your team asks for and adds it
- Shows customers where to find what they can’t locate
- Hands a stuck conversation to your team by itself
- Your team gets a card report with one command
- Every finished chat arrives as a readable report
- Your agent can pause it with a note
- Relays your agent’s note in its own words
- Follows a chat-specific rule left in a note
- Stays out of notes your team writes to each other
- Knows what your agent answered and never contradicts it
- Brings information requested by note back to the agent
- Says plainly what it can’t do, never pretends
- Steps back on takeover, joins only assigned chats
- A forgotten takeover never leaves a customer unanswered
- Logs your agents’ error reports, matched to the chat
- Every reply gets a final check before sending
- Fixes only the faulty sentence, keeps the rest
- Gets a second opinion when a sentence looks doubtful
- Never states a figure without a source
- Never says “done” without your team’s confirmation
- Never presents a customer’s claim as verified
- Doesn’t decide entitlements, doesn’t promise refunds
- If it says “passed to the team”, it did
- Never closes a chat while the issue is open
- Never makes up how long something has been checked
- Never suggests closing an account unprompted
- Never sends garbled or off-language technical text
- The assistant’s internal notes never leak to customers
- Catches known trick phrasings before they reach the AI
- Never shares internal workings or system details
- Every incoming notification is verified with a secret key
- Secret keys never end up in any log
- The learning archive is built with numbers and emails masked
- Assistant memory clears in 7 days (14 with undelivered decisions)
- The database is backed up automatically every night
- If the AI stalls, no customer goes unanswered
- Not tied to any single AI company
- Switches to the next provider if one falters
- Reports faults to your team, measured and unprompted
- Keeps a constant pulse on every connection
- Watches server health, records the moment of a freeze
- The scheduled checks are themselves checked
- What each answer relied on is recorded
- A quality report card is produced every night
- Updates are tested first on an exact copy
- Confirmed mistakes become permanent test cases, rerun every night
- Tested end to end with simulated customers
- Consistency with your team’s history will be measured regularlyplanned
- The assistant’s name, tone and sign-off will match your brandplanned
- Everything specific to you will live in one packageplanned
- Missing a setting, it won’t start; it will say whichplanned
- Each company will get its own server; data won’t mixplanned
- One form will gather details; setup will go stepwiseplanned
- It will learn from your past chats and team languageplanned
- You will decide which topics it takes onplanned
- Masking personal data will be your decisionplanned
- Simulated customers and a load rehearsal will test it firstplanned
- Alarms and the emergency stop will be drilledplanned
- Launch will be gradual, with a closely watched first weekplanned
- Connections for other admin panels will be builtplanned
It doesn’t act.
It only looks at your panel. When something has to be done, it opens a complete card for your team, and your team decides.
Permissions
- Sees your panel
- yes
- Changes anything in your panel
- no
- Where figures and rules come from
- your site, approved notices, your panel, team decisions
- When unsure
- asks, or passes it to your team
Rules, panel permissions and the pre-send check are kept apart from the language model. The model is chosen by measuring it on real conversations and can be swapped; the checking layer stays the same.
Questions.
Can it change anything in our panel?
No. The assistant connects to your admin panel with view-only access, and any request outside the allowed read addresses is refused. Anything that needs action reaches your team as a card, and your team decides.
What does it do when it isn’t sure?
It doesn’t guess. If a message is vague, it asks one clear question. If the panel doesn’t respond or a record doesn’t match exactly, it never reads that as “no record”; it passes the matter to your team. Every reply gets a final check before it reaches the customer.
Where does it learn our rules?
From your site’s promotion and rules pages, from notices your team has approved, and from your written house rules. Site scans start when your team asks, and your team gets a summary of what changed. Past conversations only set the tone; they are never a source for figures or rules.
How does our team steer the assistant?
Three ways. Your team writes its decision as a short note on a card in your team channel, and the assistant relays it to the customer in plain words. Your agents can pause or steer it with a note the customer never sees. And a temporary change, say a payment method closing for the day, takes one sentence; once you approve it, every conversation follows it.
Can our agents step in?
Yes. When an agent takes over, the assistant steps back. It picks up where it stopped when the agent hands the chat back with a note, or when the chat closes; if the agent goes quiet for a long time, the customer is not left unanswered.
Which channels and languages does it support?
Today it works with LiveChat and is set up for Turkish-language support; team cards arrive in your team channel on Telegram. If you use another live chat tool or need another language, we’ll look at it together on a call.
How does setup work?
A step-by-step setup for new companies is planned, where each step will have to be proven before the next: an intake form, a package specific to you, a site scan, an alarm drill, a test with simulated customers and a load rehearsal, then a gradual launch. The steps are not in use yet; the timeline depends on your panel and your rules, and we settle it on a call.
Let the first answer come from the source.
On a short call, we’ll walk through one of your own support cases together.
Viewing: onChanges: none
- Request status
- Pending
- Requested at
- Yesterday 21:40
- Amount
Nothing can be changed from this screen.