Email attachment intake
Attachments should not disappear into downloads.
Invoices, forms, documents, screenshots, statements, and contracts still arrive by email. Gent keeps each file tied to the message, sender, workflow, and review path that made it matter.
The problem
Files arrive with context, then get separated from it.
People download attachments, rename them, upload them, and then hunt through email later for the sender, thread, approval, or missing detail. The file moved, but the business context did not.
Lost source
The uploaded file no longer clearly points back to the exact email and sender.
Manual naming
Operators create folder structures and file names by hand.
Review gaps
Documents that need sign-off move around without a durable decision trail.
Follow-up drift
Missing pages, signatures, PO numbers, or revised files become loose reminders.
What changes
The inbox receives the file and the work around it.
Receive
The attachment arrives with the original message, sender, and thread.
Store
Files stay attached to the message context instead of becoming detached downloads.
Classify
Labels and workflow rules identify invoices, forms, contracts, screenshots, or exceptions.
Act
The inbox can create tasks, prepare follow-up, or notify another system.
Approve
Risky or high-value cases can wait for human review before the next action.
Where it fits
Use it for document-heavy email work.
Invoice files
Keep invoices, sender context, and approval history together.
Client documents
Receive files into the client or project inbox that owns the request.
Vendor forms
Track missing details and follow-up without manual inbox watching.
Operational evidence
Preserve the email, file, decision, and follow-up path together.
Next step
Keep the file with the request that made it matter.
Start with one document-heavy workflow where downloads, uploads, missing details, and review steps should stay together.