Skip to content
Brickfyn

A1 · Document & Inbox AI

Turn emails and documents into structured actions.

Read, classify, extract, compare and route information from inboxes, PDFs and files. Add human review for exceptions or sensitive decisions.

One input, one processing step, one action.

01 · Inputs

  • Shared or dedicated mailbox
  • PDFs, scans, attachments
  • Documents dropped in a drive or portal

02 · Processing

  • Classification by type and intent
  • Extraction of the useful fields
  • Comparison against references (contract, order, price list)
  • Routing to the right team or system

03 · Human checks

  • Confidence threshold per field
  • Human review of exceptions
  • Validation before any sensitive outgoing reply

04 · Outputs & actions

  • Ticket, task or record created
  • Structured data in the CRM/ERP
  • Acknowledgement or request for additional information
  • Audit log

Today

With the system

Every email is read, sorted and forwarded by hand.

Sorting and routing are automatic; humans handle the exceptions.

Document data is retyped into the tools.

Fields are extracted and pushed into the target system with a confidence score.

Comparisons are done in spreadsheets.

The comparison table is produced and discrepancies are flagged for review.

Evidence level

E4Workflow example

A tenant email with a photo becomes a categorised, assigned and acknowledged ticket, with human review if the category is uncertain.

Illustrative example of how the process can work.

Systems typically connected

  • Microsoft 365 / Google Workspace
  • CRM
  • ERP or accounting
  • Drives and document portals

Frequently asked questions

Which document formats are supported?

Emails, native or scanned PDFs, images, Office files. Extraction quality depends on the format: we measure it on your real documents during the Discover phase.

What happens if the extraction is uncertain?

The field is flagged and the document goes to human review. The threshold is set per document type.

Can you reply to emails automatically?

Yes for acknowledgements and requests for additional information. Binding replies go through human validation, unless you explicitly decide otherwise.

Tell us what takes too much of your time.

Describe a workflow. We'll tell you whether it looks suited to automation and what the most relevant next step is.