Receipt · #4821
- Trigger
- Helpdesk notification
- Charter
- Support v3 · act alone
- Procedure
- Refund policy §4.2
- Evidence
- OrderDesk REF-99120
- Actions
- 6 · timestamped
AI employees for teams
Don’t install an agent. Hire an employee.
An Amino owns one job on your team. When something changes in its queue, it acts within the role you defined, in whatever app is on its screen, old ones included. Everything it does comes with a receipt.
- Owns a role
- Acts on its own, inside a charter you wrote
- Receipts by default
- Trigger, procedure, sources and outcome on every task
- Legacy-ready
- Works through the screen, on its desk or yours
Owns a roleActs when something changesWorks inside a charterA receipt for every actionIts own desk, or your computerThe old systems too
01Assistant or employee
An assistant can act. An employee owns.
AI assistants now use computers, work in the background and remember what you like. That progress is real, and Amino builds on it. What a business still needs is someone accountable for a part of the work.
| Personal assistant | Amino employee | |
|---|---|---|
| Works for | One person, in their session | A role on the team, for anyone who needs that work |
| Starts when | Someone hands it a task | Something changes in the queue it owns |
| Knows its limits from | The prompt it was given | A role charter you wrote, with approval gates |
| Leaves behind | A conversation and a result | A receipt: trigger, procedure, sources, verified outcome |
| Works on | Your computer, under your login | Its own desk with its own logins, or a machine you give it |
If one person wants a better tool, an assistant is the right purchase. If a team needs work owned, contained and provable, that is a different one.
02Role charter · Autonomy
Autonomous inside the lines. You draw the lines.
Every Amino works from a role charter: what it is responsible for, which queue it watches, what it may do alone and what needs a person. Inside those lines it doesn’t wait to be asked. At the edge, it stops and escalates.
The charter is written in plain language, drafted from the handbook and procedures you already have. Nobody edits a prompt.
Customer Support · PellRole charter v3 · adopted 2 Oct by Maya (CX lead)
- Owns
- The support queue: refunds, order questions, delivery changes
- Watches
- Helpdesk, OrderDesk, #cx-ops
- Acts alone
- Asks first
- Never
- Discloses
- Signs every reply as an AI employee; hands off to a person on request
- Follows
- Support handbook · Refund policy §4.2
Trust ladder
Consequential steps stay gated at every level
- Week one
Supervised
Every step waits for approval while it learns how you work.
All steps gated · full trace
- As it earns trust
Assisted
Routine work inside the charter runs on its own.
Risky steps gated · full trace
- On its record
Autonomous
It owns the queue end to end, inside the lines you drew.
Your gates only · full trace
03Reflexes
It doesn’t wait for a prompt. It notices.
A role comes with a queue, and a queue fills up on its own schedule. Each run below starts the way real work does: something changes on the screen, and the employee who owns that work picks it up. Pick a desk to watch.
Pell’s deskLive
Zendesk · Refund queue
- #4821Refund request · €48Refunded
- #4826Wrong size, wants exchangeReplied
- #4830Refund request · €640Gate
- #4833Where is my order?Working
- 09:02⚡ New ticket #4821 in Zendesk · noticed
- 09:02Checked the order in Stripe · €48, within policy
- 09:03Issued refund · replied in your tone
- 09:05◆ GATE — #4830 is €640, above limit · sent to Jonas
- 09:06Back to watching the queue
04Provenance
Receipt · Ticket #4821
Pell · Customer Support · 14:02:11–14:02:31
- Trigger
- Helpdesk notification · new ticket
- Charter
- Support v3 · refunds ≤ €100 act alone
- Procedure
- Refund policy §4.2 · adopted 2 Oct
- Sources
- Ticket #4821 · OrderDesk ORD-58213
- Approval
- Not required · €48 within limit
- Outcome
- Refund REF-99120 confirmed in OrderDesk
Provenance is standard. Not an add-on.
Critical work needs more than a result. Every task an Amino completes is tied to what started it, the rules it followed, the sources it used and the system that confirms it. That record exists on every plan, from the first task.
- Source-linked memoryWhat it knows about customers and decisions carries where it learned it, shared across the team instead of one person’s chat.
- Done means confirmedA task is marked complete when your system of record says so, not when the model thinks it is. When unsure, it escalates.
- Watch live, replay laterEvery click and keystroke on its desk is timestamped and tied to that employee.
05Where it works
The old systems too. Same charter, same receipts.
Some of the systems your business depends on have no API and never will. An Amino uses them through the screen, the way a person does, and is held to the same rules there as anywhere else.
Option AAmino cloud
Its own desk
An isolated computer for one employee, with its own identity and scoped logins. If something goes wrong, the reach is one sandbox, never your laptop or your network.
Option BAmino desktop app
A computer you already have
For software that only runs on-site, connect a machine on your network. You grant what it may see and do, and you keep the Stop button.
- TN3270Green-screen terminal
- ERPOn-prem ERP
- DESKTOPAccounting suite
- WEBVendor portal without an API
- INTERNALHome-grown admin tool
- XLSMMacro-heavy spreadsheets
- CITRIXRemote desktop apps
06Hiring in five steps
Hire it like you’d hire a person.
If you can brief a remote hire, you can deploy an Amino. No coding, no prompt tricks, just onboarding.
Upload your docs
Handbook, role instructions and example scenarios.Define the role
Start from the library or write your own. Amino drafts the charter.Shape its skills
Amino suggests abilities from your docs. Add or remove any.Watch it work
Open its desk and see the work happen in real time.Graduate to autonomous
Start supervised. Widen the charter as its record grows.
- Minute 5Onboarded, reading the help docs
- Hour 1First ticket, supervised
- Day 1Routine queue on its own
- Week 1Graduated for routine work
- Month 1Part of the team
Target timeline for a support hire, Pell. Actual timing depends on the role and your documentation.
07Instant Hire Library
Start from a role. Or write your own.
Each role ships with a draft charter and skills. Reshape it to match how your team works, or start from a blank job description.
01
SDR
Qualifies leads, books meetings, sends follow-ups, keeps the CRM clean
02
Customer Support Agent
Triages tickets, answers FAQs, remembers history, escalates hard cases
03
Data Analyst
Builds reports, tracks KPIs, maintains dashboards, surfaces trends
04
Bookkeeper
Processes invoices, categorizes expenses, reconciles accounts
05
QA Tester
Documents bugs, runs test cases, verifies fixes
06
Research Analyst
Monitors competitors and sources continuously, tied to your goals
07
Social Media Manager
Schedules posts, replies as a labeled AI account, tracks metrics
08
Recruiting Coordinator
Schedules interviews and keeps candidates updated. People make every hiring decision
09
Content Moderator
Reviews submissions against your guidelines, escalates borderline cases
10
Community Manager
Moderates channels, welcomes members, runs virtual events
11
Documentation Specialist
Writes Operating Procedures and keeps the knowledge base current
Hired, not promptedAutonomy you can auditRole charters, not promptsReceipts on every planWorks the old systemsHire a team, not a tool
08Questions
Ask us the hard ones.
Give it a role. It takes it from there.
We’re onboarding teams from the waitlist in order, starting with support queues.
Join the waitlist
Tell us which queue you’d hand over first.
No spam. One email when your desk is ready.