Considerations about Baucore Inbox
Baucore Inbox automates a lot of email handling, but a handful of limits and behaviors are worth knowing before you point a team’s inbox at it — most of them are about what does and doesn’t get processed, and what a rep should expect to see when something goes wrong.
Size and attachments
- 25 MB per inbound message — this is a Salesforce Apex Email Service limit, not a Baucore-specific one, and it includes the body plus every attachment combined.
- Attachments are stored, not read. Incoming attachments are saved as
ContentDocument/ContentVersionrecords on the relatedEmailMessage, but they are not used during AI extraction — extraction only reads the email body. If a project detail lives only in an attached PDF or spreadsheet, it won’t make it into the extracted fields automatically.
Intent picklist values must stay in sync with Intent Mapping
The values available for mapping in Baucore Setup → Baucore Agents → Intent Mapping correspond directly to the picklist values on the Inbox object’s Intent field. If you need to change those picklist values, clear or update the corresponding Intent Mapping entries first — removing or renaming a picklist value out from under an existing mapping leaves it pointing at nothing.
Every Intent Mapping entry requires a description — it’s a mandatory field, not optional documentation.
Forwarded email
For a forwarded message, Baucore Inbox identifies and uses the original sender — not the person who forwarded it — as the participant on the extracted record. If your team regularly forwards project emails from a shared mailbox, keep this in mind: the participant that gets created is whoever wrote the original email, not your colleague who relayed it.
When extraction fails
Emails that can’t be extracted show an alert icon in the Inbox Navigator. Click Retry Extraction to resubmit. Users don’t have to wait around for this — closing the email while extraction is still running is fine; the results are there the next time that email is reopened in Baucore Inbox.
Credits
Every extraction — including a retried one — consumes one credit. See Baucore Inbox Credits for how the monthly allocation works and what to do when you’re running low.
Agreement and permissions
- The Baucore Agents feature (which Inbox is part of) requires a one-time per-org agreement acceptance before it can be used at all.
- Users need the Baucore Inbox permission set assigned before they can access the Inbox app or process emails.
Duplicate participants still apply
Participants created from extracted email data go through the same duplicate-prevention rules as manually created participants (same Role + Account/Contact/Lead + Project). The global bypass toggle in Baucore Setup → Participant Management works the same way here as anywhere else in Baucore — turn it on temporarily for cleanup, then back off.
A mandatory, non-automatable setup step
If Baucore Inbox stops working entirely after a package upgrade, check this first: the baucoreInbox picklist value must exist on Prov Field Mapping → Provider. This is a manual step that cannot be applied by the package installer — see the Admin Setup Guide for the exact steps.