The inbox as the front door
Client statements, engagement letters, invoices, document requests, replies that change a job's status, nearly all of it arrives the same way: as an email. For most firms, Outlook is already the point where the vast majority of back-office work effectively begins, whether or not anyone thinks of it that way.
What can actually trigger from an email
A rule that watches for a specific sender, a subject line pattern, or an attachment type can kick off a chain: file the attachment, log it against the right client, notify the person who needs to act on it. That's the same mechanism described in document intake automation, applied specifically to the inbox as the entry point.
The inbox already receives almost everything that starts a back-office process. The only question is whether something acts on it automatically or waits for a person to notice.
Where this goes beyond a simple rule
A basic Outlook rule can move a message to a folder based on the sender. Bespoke agentic code goes further: it reads what's actually inside the attachment, classifies the type of document, and routes it based on content, not just who sent it, an invoice gets treated differently from a signed engagement letter, even from the same client.
What this requires
None of this works without precisely defining what should trigger what, and which cases need a human to step in instead. That's the same underlying discipline as any of the automation covered in this pillar: the routing logic has to be specified accurately once, so the inbox can act on it consistently every time after.
Related: SharePoint as the single source of truth for client files →