Find the right contact
Match an authenticated or agent-confirmed customer to the correct CRM record rather than trusting a common name.
Integrations Freshsales
FreshsalesPlanned
Freshsales context before the next reply.
Plan read-only Freshsales customer context in Message, with matched contacts, account ownership and relevant deal information.
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.
- 01Freshsales
- 02Planned connection
- 03Message support
Know the account owner
The proposed context panel would help route a support request to the colleague responsible for the relationship.
Separate sales from support
Deal notes and internal forecasts should stay with employees, not become public AI knowledge.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Matched contact
Account owner
Selected deal summary
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose which contact identifiers and deal fields your support team actually needs.
- 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
Create two contacts sharing a name and verify the proposed matching rules do not merge them.
Before you connect
Freshsales integration questions
Can I connect Freshsales 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?
Create two contacts sharing a name and verify the proposed matching rules do not merge them.