Lifecycle: Prevent users from manually changing Contact Lifecycles in respond.io
W
Wilson Tan
Business problem:
- In some cases, Lifecycles within respond.io are synced with external CRMs, where the CRM serves as the single source of truth for the lifecycle of a contact.
- However, there is currently no mechanism in place to prevent users on respond.io from manually changing the lifecycle of a contact.
- This could lead to inconsistencies between respond.io and the CRM, resulting in data discrepancies and misaligned customer journeys.
Desired outcome:
We need a permission control system that allows owners and managers to restrict who can change the lifecycle of a contact within respond.io. This feature is essential to ensure the lifecycle data remains consistent with the CRM and prevents manual overrides that could cause inaccuracies.
Specifically, we would need the ability to:
- Restrict agents from changing the lifecycle of a contact in respond.io.
- Optionally, restrict all users from making changes to the lifecycle, ensuring that the CRM remains the single source of truth.
This solution will help maintain data integrity and ensure that lifecycle updates are properly synced between respond.io and external CRMs.