Collect customer feedback from Copper and sync customer properties

What is Copper?

Copper is a CRM tool that integrates seamlessly with Google Workspace, helping you manage customer relationships and sales processes directly within your existing workflow.

Why should you connect Copper to Cycle: Key benefits

For product teams:

1. Get access to sales notes to find product concerns that lead to lost deals.
2. Slice & dice customer feedback data based on CRM properties such as revenue, deal stage, renewal date, etc.
3. Give sales teams an incentive to submit feedback by closing the loop with them when you ship something related to their requests

For sales & CS teams:

1. Easily report product objections to the product team to unlock deals
2. Get automatic status updates when the product team acts on your feedback, without leaving Copper or needing to ping someone.
3. Re-engage customers and lost opportunities with every product update

How the Copper integration works

After a discussion with a prospect or customer, the Cycle integration makes it easy to forward product objections, bugs, and feature requests from Copper to the product team without leaving Copper. The feedback stays tied to the corresponding customer record in your CRM, and customer properties such as revenue and company lifecycle stage can be synced to the Cycle customer voice dashboards. This integration allows sales teams to effortlessly send customer feedback to the product team and get automatic status updates on the feedback they submit.

Quick setup

1. Create an API Key: In Copper, go to your settings and generate a new API key.
2. Set Up Webhooks: In Copper, create a new webhook to trigger on ticket creation with specific properties.
3. Configure in Cycle: In Cycle, go to Integrations, select Copper, and enter your Copper API key and webhook URL.
4. Test & Activate: Test the integration to ensure it's working correctly, then activate it.

Import historical data from Copper to Cycle

Cycle's graphql API lets you easily import feedback in bulk. If you're migrating from another feedback tool or would like to create multiple feedback items at once, use the createFeedback mutation.