Map your modules
Customized CRM fields need an agreed mapping before they can reliably guide a support response.
Integrations SugarCRM
SugarCRMPlanned
SugarCRM account history, within support’s reach.
Plan a SugarCRM connector for selected account and contact context, with explicit module mapping and employee-only access.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
CRM
What we’re planning to connect.
- 01SugarCRM
- 02Planned connection
- 03Message support
Understand account relationships
The proposed context would distinguish a person from the account or organization they represent.
Respect restricted records
Support access should not widen visibility to private notes or records an agent is not entitled to use.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected contact and account modules
Approved custom fields
Record access
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose the modules and custom fields your team uses for customer identification.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test restricted records and two accounts with similar names before enabling contextual lookup.
Before you connect
SugarCRM integration questions
Can I connect SugarCRM to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test restricted records and two accounts with similar names before enabling contextual lookup.