Six workflows, step by step - approval gates included.

01

Enquiry intake and first reply

Any business that loses enquiries to slow responses

A new enquiry arrives at 7pm through your website form. Instead of waiting for tomorrow’s inbox triage, the workflow reads it, understands it, and has a tailored reply waiting for approval before your competitor has opened the email.

1. 1

   Your systemsEnquiry lands - web form, shared inbox, or voicemail transcript
2. 2

   AIReads it: matter or job type, urgency signals, which person or office it belongs to
3. 3

   AIDrafts a substantive reply from your actual services, prices, and availability - not a template
4. 4

   You approveA person approves the reply - one click, from Slack or email
5. 5

   Your systemsReply sent, enquiry logged in your CRM with the full history

→ Enquiries answered in minutes, around the clock, in your voice.

02

Client progress updates

Conveyancing, litigation, agencies, anyone whose clients ring to ask “any news?”

Most client chasing happens because nothing told the client anything. This workflow watches for real progress in your case or project system and turns each milestone into an update the client actually receives.

1. 1

   Your systemsA milestone changes in your case management or project system
2. 2

   AIDrafts a plain-English update in your firm’s tone - what happened, what’s next, what’s needed
3. 3

   You approveApprove each one - or, once trusted, let routine updates send unattended
4. 4

   Your systemsUpdate sent and filed against the matter

→ The “any news?” calls stop, because there is always news.

03

Invoice chasing

Every business with an aged-debt column it dreads

Polite, persistent, and immune to awkwardness. The workflow watches your accounts system and runs a measured chase sequence - with the tone you approved and an escalation point where a human takes over.

1. 1

   Your systemsInvoice passes its due date in your accounts package
2. 2

   AIDrafts the chase - friendly at day 3, firmer at day 14, each referencing the actual invoice
3. 3

   You approveFirst runs are approved individually; the sequence earns autonomy with evidence
4. 4

   Your systemsChases send on schedule; payments and replies logged
5. 5

   You approveAnything disputed or past the escalation point lands with a named human

→ Debtor days fall without anyone spending Friday afternoon on awkward emails.

04

Document collection and deadline watch

Probate, conveyancing, onboarding - any process that waits on other people’s paperwork

Every matter has a checklist and every checklist has gaps. The workflow tracks what has arrived, chases what has not, and treats dates that matter as dates that matter.

1. 1

   Your systemsA new matter or job opens; its document checklist is created
2. 2

   AIMatches incoming email and attachments against the checklist automatically
3. 3

   AIDrafts chase messages for what is missing, spaced politely
4. 4

   You approveDeadline risks and odd documents are flagged to a person, never guessed at
5. 5

   Your systemsThe file completes itself; progress visible at a glance

→ No matter stalls because nobody noticed a missing document until week four.

05

Shared inbox triage

The info@ inbox nobody owns and everybody fears

A shared inbox is a job queue wearing a disguise. The workflow reads every message on arrival, routes it to the right person, drafts replies for the predictable majority, and keeps a count of what is waiting - so nothing rots unread.

1. 1

   Your systemsMessage arrives in the shared inbox
2. 2

   AIClassifies and routes it - orders, bookings, complaints flagged urgent
3. 3

   AIDrafts replies for the predictable categories, grounded in your systems
4. 4

   You approveApprove drafts; complaints and anything unusual always reach a human untouched
5. 5

   Your systemsEverything logged; the unanswered count is visible, and shrinking

→ An inbox that empties itself of the routine and surfaces only what needs you.

06

Daily operations digest

Owners and managers who want oversight without dashboards-as-homework

Every evening, one message: what the workflows did today, what needs a decision, and what changed in the pipeline. This is not a hypothetical - it is how Animus reports to its own founder, every day at 17:55.

This one runs our own company. Read client zero →

1. 1

   Your systemsThe day’s activity accumulates across your connected systems
2. 2

   AICompiles the digest: work completed, exceptions, numbers that moved
3. 3

   Your systemsDelivered where you already are - Slack, Teams, or email
4. 4

   You approveTwo minutes of reading; decisions flagged for you are one click away

→ You stay in command of an automated operation in minutes a day.