If you are deciding
The agency’s correspondence with an applicant is part of the file, not part of one employee’s inbox.
If you use it daily
Open an engagement and the thread is there. Reply from it, with a draft that already knows the file.
If you are doing diligence
Read-and-send only. No write-back to the mail provider. Sync is a poll roughly every ten minutes.
Threads bond to records
When a thread arrives, StreamBuild matches its participants against the contacts you hold. A match bonds the thread to that contact’s organization and to its open engagements. Correspondence stops being a parallel silo and becomes context the record can show, and that a draft can be given.
Attachments are files
Attachments are stored as real files, not links back into the mailbox. A signed agreement that arrived by email can be attached to the engagement it is evidence for, and it stays there if the mailbox is later disconnected.
Governed drafting
A reply drafted with AI is governed like any other output. You choose what the draft may read, it states what it assumed, and send is refused until each assumption has an owner.
What this does not do
- StreamBuild reads your mailbox and sends. It does not manage it: there is no mark-as-read, archive or move written back to your mail provider.
- Sync is a poll, roughly every ten minutes. It is not instant.
- A thread whose participants match no contact is not bonded to anything until someone links it.
- It is not a replacement for Outlook or Gmail, and is not designed to be.