Repetitive work runs itself — people still decide where a decision is due.
Each workflow below is owned by one business agent. It reads data inside your company's dedicated instance and stops exactly where a person has to approve. These are references to picture the work; the real scope is agreed with the implementation team.
Qualify leads and route them to the right seller
New leads are merged into the existing customer record, scored on real data and handed to an owner with a short brief.
Run byAmi Sales- Starts when
- A new lead is recorded in CRM
- Output
- A lead with a brief, a priority and an owner
- Data from modules
- Sales & CRMMarketing
- Boundary
- Never quotes, discounts or commits to terms — those belong to the seller.
Steps
- Merge into the existing recordA lead that matches a phone number or email joins the customer already on file, with its deal history and the campaigns that reached it.
- ScoreIndustry, size and readiness are checked against the criteria your company approved to set a priority.
- Brief and suggest a next stepNeed, context and open questions are packed into a few lines, with a suggestion on how to reach out.
- Assign the right personThe lead follows your existing assignment rules; deals above the threshold you set are flagged to the team lead.
After hours, a lead writes in: they need a management system for a three-store chain and are about to open a fourth.
Next morning the lead sits at the top of the owner's list with a three-line brief, high priority and a nudge to call early — nobody has to start the conversation over.
An illustrative scenario, not customer data.
Take in and resolve after-sales requests
Customer requests are classified, checked against orders and internal knowledge, and come back as a sourced answer or a summarised case.
Run byAmi Care- Starts when
- A customer sends a request or question after purchase
- Output
- A suggested answer with its source, or a summarised case for a person
- Data from modules
- Sales & CRMDocument Management – EDM
- Boundary
- Never promises compensation or returns outside policy; an upset customer always goes to a person.
Steps
- Classify the requestStatus question, complaint or how-to — each type follows a path you have defined.
- Look it up in existing dataCustomer history, orders and approved guides are read within the on-duty agent's own permissions.
- Suggest an answerThe answer cites its source document; within the delegated scope it is sent, beyond it it waits for the person on duty.
- Hand over with contextComplex cases, negative tone or a service commitment about to be missed go to a person with the full history.
After hours, a customer asks why an order placed early in the week has not arrived.
The order status is answered straight from delivery data; the customer sounds frustrated, so the case is marked priority for the support team first thing in the morning.
An illustrative scenario, not customer data.
Supplier invoices: read, three-way match, propose the entry
Supplier invoices are read, matched against the purchase order and goods receipt, and become a proposed journal entry awaiting accounting approval.
Run byAmi Documents- Starts when
- A new supplier invoice or document arrives
- Output
- A proposed entry; mismatched lines flagged for review
- Data from modules
- Finance & AccountingProcurementInventory & Warehousing
- Boundary
- Never posts a mismatched line and never guesses at an illegible document.
Steps
- Read the documentText is recognised on the scan or PDF, extracting supplier, items, quantities and unit prices against your catalogue.
- Three-way matchThe invoice is checked against the purchase order in Purchasing and the goods receipt in Inventory.
- Propose the entryMatching lines become a proposed journal entry, linked to all three source documents.
- Flag exceptionsQuantity or price differences, and anything not read with confidence, go to the accounting review queue.
The supplier invoice says 50 cartons; the goods receipt records only 48.
A proposed entry for the 48 cartons that match the purchase order; the 2-carton gap is flagged with the three related documents for accounting to decide.
An illustrative scenario, not customer data.
Scheduled receivables follow-up
Ageing is updated from recorded payments, reminders are drafted from approved templates, and items that need intervention are raised to the chief accountant.
Run byAmi Receivables- Starts when
- A daily schedule, or a change in payment status
- Output
- Reminder history on the customer record and a watch list of items
- Data from modules
- Finance & AccountingSales & CRM
- Boundary
- Never extends, writes off or negotiates a debt.
Steps
- Update ageingEach receivable gets its due date and ageing bucket recalculated from the payments already recorded.
- Rank the riskEach customer's payment history shows which items to remind early and which need a phone call from a person.
- Draft the reminderReminders follow the approved template and cadence; every reminder is saved to the customer record.
- Raise what needs a personRequests for more time, unusual items or repeat late payers go to the chief accountant.
An invoice is due today with no payment recorded; this customer has paid late twice before.
A first reminder is drafted from the template and saved to the record; because of the late-payment history, the item joins the chief accountant's watch list.
An illustrative scenario, not customer data.
The morning management briefing
The numbers already sit on one data layer, so nobody has to collect them from spreadsheets — the agent drafts and sends the briefing before the meeting.
Run byAmi Analytics- Starts when
- Every morning, ahead of the management meeting
- Output
- A one-page briefing: key figures, changes and flags, each figure with its source
- Data from modules
- BI & AnalyticsSales & CRMInventory & WarehousingFinance & Accounting
- Boundary
- Never draws conclusions for management and never acts on a flag by itself.
Steps
- Read the closed figuresYesterday's sales, stock and receivables are read straight from the modules, within each recipient's own permissions.
- Compare and detectFigures are compared with last week and the same period last year; changes beyond your threshold are flagged.
- Draft the briefingKey figures, what moved and why the number changed, on a single page.
- Send to the right peopleEach recipient sees only their own scope — a branch director never sees another branch's figures.
A fixed schedule every morning before the leadership stand-up.
A one-page briefing with key figures, a seven-day comparison and two anomalies, each figure stating which module it came from.
An illustrative scenario, not customer data.
Summarise applications and invite to interview
Applications are summarised against the criteria in the job description; the recruiter chooses, and the agent drafts the invitations and replies.
Run byAmi Hiring- Starts when
- A new application arrives in a hiring round
- Output
- Criteria-based summaries, a shortlist chosen by a person, and draft invitations
- Data from modules
- Human Resources – HRM
- Boundary
- Never uses sensitive criteria and never decides to hire or reject.
Steps
- Collect applicationsApplications for one hiring round land in a single list in the HR module, with duplicates merged.
- Summarise against criteriaEach application is summarised against the approved criteria in the job description — no pass or fail score.
- A person picks the shortlistThe recruiter reads the summaries and decides who is invited; the agent does not rank candidates for them.
- Draft the messagesInterview invitations and courteous replies to candidates not taken forward are drafted and wait for approval before sending.
A round for an accountant role receives 40 applications in one week.
40 summaries against the same five criteria; the recruiter picks six, invitations are drafted for approval, and every other candidate has a reply waiting.
An illustrative scenario, not customer data.
Bring one of your real workflows to the demo.
We rebuild it on sample data: which agent owns it, where it stops for approval, and what the audit log records.