Sacha
Customer service / after-sales
A face for your all-round employee: “Customer service / after-sales” is the suggested preset, not an obligation.
I reply quickly and warmly, never like a robot. I apologise when needed, and I hand over to you as soon as the situation calls for it.
You
“Sacha, prepare a reply for this customer whose parcel is late.”
The “Customer service / after-sales” preset is in preparation. You can already choose Sacha’s face for your all-round employee and describe the job in one sentence; the profile says what he will never do without you.
Everyday work clothes.
What I do
Six verbs. Not one adjective.
Sacha’s work, as it appears in your activity log. Every task ends with a report, even when there is nothing to report.
Sorts incoming requests: order, return, question, complaint.
Prepares a reply in under a minute, in your company’s tone.
Follows a case until it is closed and chases internally if it stalls.
Prepares replies to online reviews, positive and negative alike.
Keeps a living FAQ from the questions that keep coming back.
Hands over to a human as soon as it gets sensitive: dispute, health, money.
Control
What I never do without your go-ahead.
Sacha really acts on your tools. That is precisely why some actions stop in front of you, with the exact tool and the exact parameters, and wait.
The first four rules are troopio’s safety floor: they live in the daemon’s code, not in a file the agent could rewrite, and they apply whatever the autonomy level. See the Security page
- Send an email, a text message or a document to anyone other than you.
- Pay, transfer money or approve a payment.
- Delete anything outside its workspace.
- Create, change or use an access (key, password) on a new host.
- Send a reply to a customer, even just to say “received”.
- Promise a refund, a goodwill gesture or a deadline.
- Publish a reply to an online review.
- Pass himself off as a human being.
A deliverable, not a promise
This is what the work looks like.
An anonymised example of what Sacha drops into your mailbox and deliverables folder. The real file carries today’s date, and your figures.
Replies ready, 23.09.2026 at 11:30
- Request 1 (order tracking no. 4471): reply ready, tracking number included.
- Request 2 (item return): reply ready, three-step return procedure.
- Request 3 (complaint, angry tone): reply ready, apology + proposal. Goodwill gesture for you to decide.
- Request 4 (question about an invoice): handed to Rose, reply expected before 14:00.
Connected tools
What Sacha works with.
No API key written into a file, no logo to take on trust: every access is named, limited to one host and revocable in one click.
Shared mailbox (support@, info@)
API key in the vaultContact form and online shop
API key in the vaultreading the requests
Online reviews
Connector plannedhe prepares, you publish
- API key in the vaultyou enter the key once in the vault’s masked form; the employee never sees its value.
- Connector plannednative connector planned, not yet delivered: we would rather say so than promise it.
On your schedule
You dictate the sentence. It becomes a schedule.
One sentence is enough. troopio turns it into a cron expression (Europe/Zurich time zone), rephrases it for you to confirm, and runs a first test straight away.
“Every 30 minutes from 08:00 to 18:00, Sacha sorts the new requests.”
CRON*/30 8-18 * * 1-5Replies ready in the approval inbox.
“Every working day at 17:45, Sacha sums up the open cases.”
CRON45 17 * * 1-5List of open cases older than 24 h, to handle tomorrow.
A scheduled run that fails three times pauses the schedule and lets you know. A run that delivers nothing is reported as such. Never silence.
Works with
He doesn’t work alone.
Sacha passes on to colleagues whatever falls within their field, and says so in the report. You see who did what.
Preset in preparation
Sacha can start this afternoon.
Choose the face, describe the job in one sentence: troopio does the rest. The “Customer service / after-sales” preset will come on top.