Provide representative records, current ownership, approval responsibilities, integration access and the relevant contact or retention policies. Keep secrets out of documents and shared exports.
Implementation
Understand implementation for CRM with Email Campaigns.
Implementation phases
Phase 1 · Team and ERP.ai
Agree on scope
Confirm the customer workflow and public capabilities with the responsible owners.
Phase 2 · Team and ERP.ai
Prepare the workspace
Configure role membership, source identities and reference data.
| Role | Screens |
|---|---|
| Email Marketing Manager | 10 |
| Email Designer | 0 |
| Deliverability Manager | 6 |
| Marketing Operations | 4 |
| Campaign Approver | 8 |
| Viewer / Analyst | 1 |
Role permissionsRoles and permissions →
Phase 3 · Team and ERP.ai
Reconcile open work
Import actual states, ownership and prior decision evidence.
Phase 4 · Team and ERP.ai
Connect carefully
Enable each integration only after its mappings and uncertain-outcome behavior are tested.
Phase 5 · Team and ERP.ai
Practice the handoff
Run the main workflow and rejected-action cases with the people who will operate it.
Phase 6 · Team and ERP.ai
Extend gradually
Review exceptions before opening the workflow to the wider team.
Use Proto to propose a configuration change from the current system specification. Review affected records, permissions and customer promises together. Preserve earlier decisions, test the changed workflow and verify the result before enabling it for everyone.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.