Automations and workflows
Concrete examples of work moving between the inbox, website, CRM, documents and internal systems, with a person kept in control where judgement matters.
Map an automation
Automation works best where the trigger, expected result and exception are clear. AI becomes useful when the input is less structured, such as an email, call or document, but it still needs a defined job and a safe stopping point.
The patterns below show the shape of the work. The final design depends on volume, existing software, data quality and the cost of getting something wrong.
Workflow catalogue
Each row is a pattern to assess, not a claim that every business should implement it.
Before
A website form reaches a shared inbox and waits for somebody to notice.
After
Classify the enquiry, create or update the CRM record, assign an owner and prepare the first reply.
Human checkpoint
Approve unusual replies and commercial commitments.
Before
Quotes are sent, then follow-up depends on memory.
After
Schedule reminders, record responses and surface quotes that need a personal call.
Human checkpoint
Choose the message and handle negotiation.
Before
An unanswered call becomes a number with no context.
After
Capture intent, contact details and preferred time, then create an actionable callback request.
Human checkpoint
Return sensitive, urgent or unclear calls.
Before
Invoices, forms or applications are read and re-entered by hand.
After
Extract the required fields, validate basic rules and prepare a structured record for review.
Human checkpoint
Confirm exceptions and final submission.
Before
The same routine questions are answered repeatedly across email and chat.
After
Draft from approved policies and product information, route by topic and flag anything uncertain.
Human checkpoint
Approve customer-facing answers until quality is proven.
Before
Weekly figures are copied from several systems into one spreadsheet.
After
Collect the sources on schedule, calculate agreed measures and prepare a commentary draft.
Human checkpoint
Interpret the numbers and decide what changes.
Before
Staff ask the same person where a policy, price or previous decision lives.
After
Search approved internal material and answer with a link back to the source.
Human checkpoint
Own the source documents and resolve conflicting guidance.
Before
Reviews are noticed late and responses are inconsistent.
After
Monitor new reviews, classify the issue and prepare a response in the business voice.
Human checkpoint
Approve complaints, disputes and anything personal.
The control point
A useful automation moves routine work forward, but it also knows when to stop and ask.
Work enters from an inbox, form, schedule or connected system.
Defined rules handle the routine steps and keep the record moving.
Missing information, low confidence or a consequential action pauses for review.
The outcome is delivered and written back to the right record or log.
How we compare
Doing it yourself is cheap until it breaks without anyone noticing. Development agencies often build more than you need. Add-ons do one thing their own way. We build the smallest automation that does the job, with a safe way to stop.
| Recommended Astraeus Rules, AI and agents, with a person in control | DIY in Zapier or Make | Development agency | Off-the-shelf add-on | |
|---|---|---|---|---|
| Looks at the job before picking a tool | We check how often it happens, what it costs and what could go wrong | You start with the tool | Often starts with a specification | A fixed feature set |
| Uses the simplest thing that works | Simple rules where they work, AI only where it helps | Limited to what you know | Often custom code by default | One fixed approach |
| A person checks anything that needs judgement | Built into every automation | If you think of it | Varies | Rarely configurable |
| Knows what to do when something goes wrong | Unusual cases are passed to a person to decide | Can fail without anyone noticing | Usually | Limited |
| Keeps a record, and someone is in charge of it | You can always see what it did and why | Basic run history | Usually | Vendor logs |
| Works with the tools you already use | Ready-made connections first, custom work only when needed | A wide connector library | Often custom builds | Only its supported apps |
| Costs what the job is worth | We build only what the job needs | Low cost, but your time | Usually costs more to build and maintain | Ongoing subscription |
| Your team is shown how it works | Written guide and training included | Often only in one person's head | Technical documents | Vendor help pages |
| Discuss a first automation |
Based on how these options usually work. Individual providers vary.
Discuss a first automationBest for predictable triggers and structured data. Reliable, explainable and usually cheaper.
Best where a person benefits from classification, extraction, summarising or a first draft.
Best where work crosses several steps or tools and needs controlled decisions along the way.
Required for sensitive exceptions, commitments, disputes and decisions with material consequences.
A clear route back to manual handling when a system, connector or model fails.
A named person who receives exceptions and knows when the workflow needs attention.
Enough evidence to reconstruct what happened without collecting unnecessary data.
Documentation, training and a clear statement of ongoing support responsibilities.
The honest boundary
These are examples, not guaranteed packages or savings claims. A workflow is only worth building after its frequency, friction, value and failure cost are understood.
Direct answers
Usually the one with high frequency, clear inputs, measurable delay or effort, and a low-cost failure path. The loudest complaint is not always the best first build.
No. If rules can handle the task reliably, normal automation is the better choice. AI is useful for language, documents and variable inputs, not as decoration.
Often yes through built-in connectors, APIs or webhooks. Custom integration is used only where ordinary connectors are not enough.
A production workflow needs an exception queue, a manual route and a named owner. Failure handling is part of the build, not a later add-on.
Yes. One bounded workflow with a clear measure is the normal starting point.
We will map the trigger, systems, exceptions and expected result before recommending a build.
Map an automation