How it works
From your handbook to an employee on the job.
Amino turns the documents you already have into Operating Procedures, a role charter and a set of skills. Then it puts the employee on a desk where you can watch it work.
PDFCompany DNASupport-Handbook.pdf48 pages · refund policy · tone guide
Role charter · drafted
- Acts alone · refunds ≤ €100
- Asks first · over €100
- Never · changes prices
Pell · Customer SupportOn its desk · supervised
01Hiring in five steps
Hire it like you’d hire a person.
If you can brief a new hire, you can direct an Amino — no coding, no prompt engineering. Hand over the same docs you would give a person, and watch it get to work.
- Step 01
Upload your docs
The handbook, role instructions, and real scenarios — the same brief you would hand a human hire. - Step 02
Define the role
Write it from scratch, or start from a pre-trained role in the Instant Hire Library and reshape it. Amino adapts to your roles. - Step 03
Shape its skills
Compose abilities like building blocks — Amino suggests the first set straight from the docs you uploaded. - Step 04
Watch it work
Live on its own Digital Desk — approve the risky steps while it earns your confidence. Nothing happens in a black box. - Step 05
Graduate to autonomous
Supervised becomes self-directed — with a full trace of everything it did, and a memory that never resets.
- Minute 5onboarded
- Hour 1first real task
- Week 1half the repetitive work gone
02Company DNA
Teach it once. It follows it always.
Drop in the docs you already have. Amino reads them into Operating Procedures you can review and adopt, then suggests the skills to carry them out.
Operating Procedures
- ✓AdoptedTicket triage rules — priority by plan & sentimentSupport-Handbook.pdf · §2.1
- ✓AdoptedRefund approval flow — thresholds and sign-offRefund policy & tiers · §4.2
- Pending reviewEscalation ladder — when to loop in a humanEscalation examples · case 7
Suggested skills
- ✦ Zendesk triage
- ✦ Refund lookup
- ✦ Tone guide
- CSAT digest
03Reflexes
Work arrives on its own schedule. So does an Amino.
A role comes with a queue, and a queue fills up on its own schedule. When a ticket lands, an error dialog appears or a file shows up, the employee who owns that work sees it on its screen and picks it up.
Monday, 09:00–10:00
Prompts sent: 0- 09:04 · HelpdeskNew ticket: order arrived damagedPell · SupportChecked the order, refunded €48, replied
- 09:17 · CRMDemo request from Halden Co.Merrow · SDRResearched the account, booked Thursday 10:00
- 09:31 · OrderDesk · no APIError dialog: invoice failed to postPell · SupportFixed the address field, re-posted, noted it
- 09:40 · CalendarAn interviewer called in sickThatch · Recruiting CoordinatorMoved three interviews, emailed the candidates
- 09:52 · WarehouseNightly load finished lateArden · Data AnalystRe-ran the readout, flagged the delay
04Skills · Building blocks
Skills snap together.
Every role is assembled from skills. Pick them up ready-made, pull them from the marketplace, or write your own. Skills are portable, so you can export them too.
- Ready-madeCore abilities every role can pick up on day one — no setup.
- From the marketplaceSpecialist skills built by others, dropped straight into your role.
- Defined by youYour playbooks, your policies, your voice — written once, followed always.
Customer Support · Pell
- Ticket triageReads, tags, and prioritizes every incoming ticketReady-made
- CRM syncKeeps customer records current across your toolsMarketplace
- Refund policy repliesAnswers refund requests exactly the way you wrote itYours
- Escalation handoffFlags edge cases to a human before actingReady-made
05The formula
We build employees, not
assistants.
- 01
Company DNA
Your docs, policies and voice. - plus
- 02
Procedures
Reviewed rules it follows. - plus
- 03
Skills
The abilities that carry them out. - equals
- 04
An employee
A colleague your whole team can hand work to.
Give it a role. It takes it from there.
We’re onboarding teams from the waitlist in order, starting with support queues.