Intake channels
Work and documents enter BreezyCorp through a small set of channels. Whatever the channel, the inbound item lands on the platform, gets attached to the right entity, and starts a run — so the downstream experience is the same regardless of how it arrived.
The channels
| Channel | What comes in | Used by |
|---|---|---|
| Microsoft 365 mailbox | Statutory and agency mail, support email, client documents | Correspondence, Ticketing (planned) |
| WhatsApp (Meta WhatsApp Business Platform) | Client-sent documents and receipts | Bookkeeping ingestion |
| Client portal | Intake submissions, confirmations, approvals, uploaded files | Payroll, Bookkeeping, FS, XBRL |
| Public API / webhooks | Programmatic submissions; provider callbacks (OCR results, signatures) | Integrations |
| Folder sync (Drive / SharePoint) | Documents dropped into a watched folder | Bookkeeping ingestion |
| Manual upload | A staff user uploads a document directly | All modules |
What happens after intake
- Store — the document is stored once (one S3/object bucket, one OCR pipeline) and a record is created.
- Attach — it is resolved to a tenant, an entity (or a client match), and a module.
- Process — OCR and classification run where relevant; a run is started or advanced.
- Gate — anything regulated or external waits at the human gate.
Why it's centralised
Because every channel funnels into the same pipeline, the platform has one place to apply isolation, audit, retention, and PII handling — and you learn one mental model instead of one per product. A document that arrives by WhatsApp is handled by the same OCR and the same review surface as one uploaded by hand.
Per-module specifics
- Bookkeeping — set up channels per client; see Set up an ingestion channel.
- Correspondence — driven by the firm's mailbox; see the Correspondence handbook.
- Payroll / FS / XBRL — client submissions and confirmations arrive through the client portal.