AI automation
The busywork, built out of your week.
Five automations — documents, support, leads, integration and internal knowledge — engineered into the tools you already run, with a person kept in the loop wherever the system is not sure.
01 How they are built
Five jobs. One engineering spine.
Every automation we build follows the same five steps. That is deliberate: it makes each one predictable to run, easy to combine, and honest about uncertainty.
- IntakeWhatever channel the work arrives on — inbox, form, scanner, API.
- UnderstandClassify it, read the fields, detect intent and urgency.
- ValidateConfidence scores, cross-checks and your business rules.
- ActPost, route, assign, reply or sync — in your systems.
- Human reviewAnything uncertain waits for a person. Nothing is written silently.
02 The five
Pick one to see how it runs.
Each shows the job it takes over, the workflow it runs, and what it looks like in use.
DocTrace — invoices, forms, delivery notes
You know this onePaperwork reaches you five different ways, and somebody retypes the same fields into whichever system needs them. A mistyped digit surfaces at month-end.
What changesDocuments are read, checked and filed automatically. The only ones a person opens are the ones the system flagged.
- Document arrivesEmail, scanner, upload or phone photo
- AI extractionType detected, the right fields read
- ValidationConfidence per field, totals cross-checked
- Business rulesYour thresholds and approvals
- RoutingTo the owning system — or a reviewer
- System updatedAccounting, ERP, HR, inventory
SupportRoute — email, forms, tickets
You know this oneEvery channel lands in one pile. Agents read everything to find the urgent message, and simple questions wait behind complex ones.
What changesEach message is read for intent and urgency the moment it lands, routed to the right person, and arrives with a drafted reply to approve.
- Customer messageEmail, web forms, helpdesk
- Intent detectionWhat the person actually wants
- ClassificationBilling, delivery, technical, sales…
- PriorityUrgency and customer value
- Knowledge retrievalYour policies and past answers
- Reply or escalateDrafted answer, or straight to a person
ProspectRoute — every enquiry to the right owner
You know this oneEnquiries arrive through the website, email and the phone. Some sit in a shared inbox over the weekend, and nobody knows which good ones went cold.
What changesEvery enquiry is captured, scored against your ideal customer and assigned within minutes — with a clock on it, so nothing waits unnoticed.
- Lead arrivesForm, email, call notes
- QualificationCompany, need, size, budget
- ScoringAgainst your ideal customer profile
- RoutingTerritory, product, availability
- CRMContact and deal created
- SalespersonNotified with context and a deadline
- Follow-upEscalates if the clock runs out
UnifyCore — two systems, connected both ways
You know this oneTwo systems that cannot talk to each other, and someone who exports a spreadsheet every Monday to keep them roughly in step.
What changesThey sync in both directions, with retries, a review queue for anything that does not match, and an alert instead of silence.
- Multiple systemsStorefront, ERP, accounting, CRM
- ConnectAPIs, databases or scheduled exports
- NormaliseFormats, units, currencies, names
- StructureRecords matched and mapped
- UnifyBoth sides kept in step, both ways
- IntelligenceClean data ready to report and ask
- order.created → mapped
- customer matched · existing record
- invoice created in accounting
- SKU BX-12 unknown → review queue
- retry scheduled · alert sent
KnowledgeAssist — answers from your own documents
You know this onePolicies live in PDFs, shared drives and a few senior people’s heads. Everyone asks the same colleague, and the answer depends on who you ask.
What changesStaff ask in plain language and get the answer — with the exact section it came from, and only from documents they are allowed to see.
- Your knowledgeDocuments, SOPs, policies, past tickets
- Permission checkOnly what this person may see
- Secure retrievalThe passages that actually apply
- AI reasoningAn answer drafted from those passages only
- Answer + sourcesCited section and a confidence level
03 Side by side
Compare the five.
Timelines are typical ranges from signed scope to running in your systems. Your written scope states the exact figure before you commit.
| Automation | Takes over | Lands in | Typical build |
|---|---|---|---|
| DocTrace | Reading and retyping invoices, forms and delivery notes | Accounting, ERP, HR, inventory | 4–8 weeks |
| SupportRoute | Sorting, answering and escalating support messages | Helpdesk, CRM, on-call rota | 4–10 weeks |
| ProspectRoute | Capturing, scoring and assigning enquiries | CRM, sales tasks, email | 3–8 weeks |
| UnifyCore | Moving data between systems by export and paste | Both systems, in both directions | 3–8 weeks |
| KnowledgeAssist | Answering the same policy questions every week | Chat, intranet, helpdesk | 4–8 weeks |
Connects to tools like these. Anything else with an API or export is confirmed during assessment
- Excel & Google Sheets
- HubSpot
- Salesforce
- Zoho
- Odoo
- Tally
- SAP
- QuickBooks
- Xero
- MySQL
- PostgreSQL
- SQL Server
- Zendesk
- Freshdesk
04 Questions
Questions teams ask about automation.
Do we need the SolmiriX platform to use these?
No. Each automation is engineered around your own tools. Some UnifyCore work connects your systems into SolmiriX, our AI analytics platform; most automations connect your tools directly, with no platform involved.
Can we start with just one?
Yes. Each of the five stands alone. You can start with the one workflow that hurts most, and add a second once the first is running.
How are price and timeline set?
After a free discovery call you receive a written scope with a fixed price and timeline. As a guide: DocTrace and KnowledgeAssist usually take 4–8 weeks, ProspectRoute and UnifyCore 3–8 weeks, SupportRoute 4–10 weeks.
Are these built for one industry?
No. They are built around operational patterns — documents piling up, inboxes flooding, leads going cold, systems that do not talk, the same questions asked every week — and tuned on your own records during the build.
What happens when the system is not sure?
It stops and asks a person. Every automation has confidence thresholds and a review queue you control; nothing uncertain is written into your systems silently.
05 Not sure automation is the answer?
Other ways in.
AI analytics
SolmiriX
If the problem is not knowing — numbers spread across systems, answers that take a week — start with the platform.
Explore SolmiriXData & BI
Reports your team trusts
If the same report is rebuilt by hand every month, we build it once on the BI tool you already pay for.
Data engineering & BINot sure where to start?
AI readiness & consulting
If you are not yet sure what to build, a readiness engagement ends in a costed roadmap before you spend on anything.
AI readiness & consultingTell us which job you want off your team’s plate.
In 30–45 minutes we will tell you whether it is worth automating, which of the five fits, and roughly what it would take.