Recognize the relationship
Bring a confirmed customer’s company and contact context into the support workflow.
Integrations Copper
CopperPlanned
Keep Copper relationships close to support.
Plan a Copper connector that gives support staff selected relationship and opportunity context without exposing private CRM notes.
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.
- 01Copper
- 02Planned connection
- 03Message support
Find the responsible teammate
Use a selected record owner to prepare an internal handoff when an account needs personal follow-up.
Limit opportunity detail
Show only the sales context necessary to help the customer; keep internal notes out of public responses.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Confirmed contact
Company relationship
Selected opportunity fields
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Identify the Copper records and ownership fields that should guide support handoffs.
- 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 an unrecognized email and a contact linked to multiple companies before accepting a match.
Before you connect
Copper integration questions
Can I connect Copper 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 an unrecognized email and a contact linked to multiple companies before accepting a match.