WFD EMAIL ENGINE

Turn every inbox
into a process.

Give every process its own email address, connect the mailboxes you already use, or do both. Email Engine captures the message, attachments, links and context, prepares documents for processing and gets the right work moving automatically.

Dedicated addresses Microsoft 365 Google Workspace POP / IMAP
@
invoice@vendor.co.ukInvoice 47281
PDF
@
orders@customer.comNew purchase order
LINK
@
onboarding@partner.netSupplier documents
3 DOCS
Email Enginecapture · understand · prepare
PROCESS READY
Context captured
Documents prepared
Workflow started
↓
THE PROBLEM

Email was never designed
to be a workflow.

Shared inboxes quietly become manual process queues. Someone has to open the message, work out what it is, download the attachment, follow the link, save the file, decide where it belongs and remember to tidy the inbox afterwards.

Each action is tiny. At volume, the friction is not.

01Open email
→
02Read context
→
03Download
→
04Decide route
→
05Move email

Email Engine removes the repetitive micro-decisions between receiving work and starting work.

PURPOSE-BUILT INTAKE

Give every process
its own front door.

Create dedicated addresses for invoices, orders, claims, onboarding or any other email-driven process. Messages arrive already aligned to the work they belong to.

  • Separate email entry points for separate processes
  • Clearer ownership and less inbox triage
  • Processing behaviour can be configured around the use case
AP
invoices@Accounts payable
→
SO
orders@Sales orders
→
CL
claims@Claims intake
→
ON
onboarding@New starters & suppliers
→
Email Engine
ADOPT WITHOUT DISRUPTION

Keep the inboxes people already know.

Dedicated addresses are the cleanest destination. Getting there does not have to be a big-bang change.

TODAY
M
Microsoft 365ap@business.co.uk
G
Google Workspaceorders@business.co.uk
@
POP / IMAPAny compatible mailbox
CONNECT DIRECTLY
OR
FORWARD DURING TRANSITION
EMAIL ENGINE
purpose-built@Clean process entry point
Move at your pace. Existing senders do not need to change on day one.
Monitor multiple connections, mailboxes and folders / labels at the same time — across teams, functions or business units.
CONTEXT BEFORE CONTENT

The email is part
of the data.

Who sent it, where it came from, who received it, what the subject says and what the body contains can all remove decisions later in the process.

For an AP invoice, a recognised sender domain can identify or narrow the supplier before data capture starts — and can help select the right extraction rules.

sender domain Northshore Supplies recipient AP process subject invoice rules supplier profile
DOCUMENT PREPARATION

Make every document process-ready.

Real-world email brings real-world inconsistency. Email Engine can align incoming content before it reaches downstream automation.

PDFprotected XLSworkbook EMLemail file IMGscan
prepare validate · convert · sanitise
Validatedusable document
Normalisedexpected format
Unblockedprocessing barriers removed
Small document issues cause large automation failures. Something as simple as a PDF protection setting can stop data capture before it begins. Prepare once, then let downstream processes focus on the work.
SHAPE THE TRANSACTION

One email.
One process. Or many.

Different processes need different transaction boundaries. Keep multiple documents together, split them into separate work items, include the email body as supporting context, or use linked documents when no conventional attachment exists.

Email Engine turns the message into the process input your downstream system actually needs.

1 email3 documents + body
Transaction 01
PDFPDFIMGBODY
FROM INBOX TO ACTION

Email Engine captures and prepares.
What happens next is your choice.

Use Email Engine on its own and hand the result into your existing solution — or combine it with Routing Engine to orchestrate the wider process.

Email Engineprocess-ready input
RRouting Enginedecide what happens next
DCData Capture
CEContent Engine
APApproval Workflow
↗Your System
STANDALONECapture. Prepare. Hand off.Use Email Engine independently with your existing systems.
TOGETHERCapture. Route. Orchestrate.Combine focused WFD Engines to build a wider solution.
CONTROLLED EXCEPTIONS

Exceptions need
a route too.

Automation should not mean silent failure. When a message cannot be processed automatically, Email Engine can move it into a controlled handling path with the original context intact.

  • Keep unprocessable work visible
  • Preserve the original message and context
  • Separate happy-path throughput from the work that genuinely needs attention
✓
Invoice + valid attachmentContinue automatically
→ PROCESS
!
No usable document foundRequires attention
→ REVIEW
Manual handling1 item waiting · context retained
CONTROL SURFACE

One place to configure
how email becomes work.

Manage source connections, select mailboxes and folders, control polling, choose downstream workflows and see the current operating state.

email-engine / configuration
CONFIGURATION

Mailbox monitoring

1
Ingress modeChoose how mail enters Email Engine
APIMAILBOXBOTH
2
Source connections3 connections · 7 mailboxes
Accounts PayableFolders / labels
3
Routing workflowsChoose published workflows
↗
AP Invoice IntakePublished · v12
✓
↗
Customer OrdersPublished · v4
✓
4
RuntimeCurrent production state
AutomaticPolling
7Mailboxes
EnabledTelemetry

Illustrative marketing representation based on the Email Engine control surface. No live customer data is shown.

ONE ENGINE. MANY SOURCES.

Watch the inboxes your business depends on.

Email Engine is designed to manage multiple connections, mailboxes and folders at once — not just a single shared inbox.

FINANCE
AP invoices
Credit control
SALES
Orders
Customer docs
HR
Onboarding
Forms
OPERATIONS
Claims
Service inbox
Email Enginemany sources · one controlled intake layer
USE CASES

Email is still where
a lot of work begins.

Use Email Engine anywhere a business process starts with a message, an attachment or a link.

AP

Accounts payable

Capture supplier invoices, identify useful sender context and prepare documents for extraction or approval.

PO

Purchase orders

Receive order documents and route them into the process without inbox monitoring and manual downloads.

SO

Sales orders

Collect customer orders from attachments or links and feed them into fulfilment workflows.

CL

Claims

Turn incoming forms, evidence and correspondence into controlled case inputs.

ON

Onboarding

Collect employee or supplier documents and start the correct onboarding route automatically.

CS

Customer service

Use sender, subject and message content to help classify correspondence and start the right response process.

WFD ENGINE ECOSYSTEM

Focused Engines.
Better together.

Use Email Engine independently, or combine it with other focused WFD Engines to build a complete solution without buying another monolithic platform.

See where email fits in a real solution →
Email Engine Routing Engine Match Engine Accounts Engine Content Engine Integration Engine Telemetry Engine Cardiograph
A REAL SOLUTION

See where email fits.

STEP 01

Email Engine

Capture incoming documents and message context from dedicated addresses or existing mailboxes.

Email Enginecapture
Routing Engineorchestrate
Data Captureextract
Match Enginecompare
Accounts Engineprocess
Integration Engineconnect
Content Engineretain
WFD EMAIL ENGINE

Stop managing inboxes.
Start moving work.

Tell us where email enters your process today. We’ll show you where Email Engine can remove the manual steps.