Integration · Revenue
Why didn’t this person get the email?
Brigham.ai reads the full trail for a contact and gives you the reason, not a guess.
What it checks
1
Enrollment
Was the person enrolled, and in which sequence?
2
Sends
Which steps went out, and when?
3
Engagement
Opens, clicks and replies that followed.
4
Consent and suppression
Whether consent or a suppression stopped the send.
Scopes and access
- Connects as
- The erp.io sequences module, within each person’s permissions
- Access
- Read-only by default
- Reads
- Enrollments, sends, engagement, consent, suppression
- Writes
- None by default
- Needs approval
- Enrolling a contact in a sequence (sensitive action)
- Visibility
- Follows CRM permissions
- Availability
- Available
Enrolling is sensitive.
Putting a person into a sequence means messages go out in your name. Brigham.ai can propose it. A human approves it.
Ask it
- ›“Why didn’t Priya get step two?”
- ›“Who replied to the onboarding sequence this week?”
- ›“Which contacts are suppressed and why?”
- ›“Enroll these five people in the demo follow-up sequence.”
Questions, answered.
Can Brigham.ai enroll people on its own?
No. It can propose an enrollment, and the approval engine requires a person to approve it.
Keep reading.
CRMBrigham.ai reads the whole erp.io CRM and, once an admin allows it, makes reversible changes: tasks, notes, field updates and stage moves.Read →
Email deliveryBrigham.ai reads your email provider’s events and reports what really happened. A provider’s 202 means accepted, not delivered.Read →
ApprovalsEvery approval is bound to the exact payload hash. Change the action and you approve again. Email links confirm on click, never on open.Read →