Provide the customer moments to survey, question wording, valid scales, privacy choices, consent sources, frequency limits, account/team ownership, business-day calendar, comparison cohorts and permitted delivery/classification providers.
Implementation
Configure the survey moments, people and controls your program needs.
Implementation phases
Phase 1 · Team and ERP.ai
Map the listening program
Choose the customer decisions, instruments and moments: support CSAT, relationship NPS, journey CES or a custom program. Record what is attributable and what must stay anonymous.
Phase 2 · Team and ERP.ai
Configure people and sources
Connect the trusted CRM, employee directory and event sources. Resolve account and team ownership, current consent, delivery limits, response windows and permitted processors.
Phase 3 · Team and ERP.ai
Publish and review the pilot
Test branches, scale ranges, immutable versions and a small approved audience. Verify independent campaign review, a paused send, a repeated trigger and an opt-out arriving during delay.
Phase 4 · Team and ERP.ai
Verify response and follow-up
Test a valid response, expired token, replay, private anonymous joins and an attributable recovery task with an independent outcome decision.
Phase 5 · Team and ERP.ai
Reconcile and expand
Check sent and accepted populations, score denominators, masked themes and compatible cohorts before enabling wider audiences. Preserve the exact instrument and policy revisions as the program evolves.
Change a published instrument by creating a new version. Campaign changes require a new current-revision review. Keep accepted responses immutable, use governed invalidation with recomputation, and preserve current access rules when owners or teams change.
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.