Connect people and companies
The intended workflow would associate a support customer with the right business relationship.
Integrations Attio
AttioPlanned
Attio relationship context, ready for support.
Plan an Attio connector for selected people, companies and custom attributes, with clear boundaries between relationship context and AI knowledge.
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.
- 01Attio
- 02Planned connection
- 03Message support
Choose relevant attributes
Custom attributes should answer a support need, such as ownership or service tier, rather than copying every field.
Keep lists in perspective
Membership in a sales list is internal context. It must not be presented as a promise or customer entitlement.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Person and company records
Selected custom attributes
Relationship owner
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose the attributes used to identify a customer and explain their service relationship.
- 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 multiple company relationships and a missing attribute before trusting the mapping.
Before you connect
Attio integration questions
Can I connect Attio 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 multiple company relationships and a missing attribute before trusting the mapping.