If you collect customer feedback, bug reports, or product requests in your CRM, it helps to have that information flow directly into the system your product or engineering team uses to track work. This connection makes it easier to log requests, stay organized, and keep customers informed when something is fixed or shipped.
📌 Why This Matters
Small business owners often hear valuable feedback from customers, but that information can get stuck in emails, support conversations, or notes. With this CRM feature, you can automatically turn customer feedback into tracked work items, connect those requests to the right customer record, and send updates when progress happens.
That means:
- You keep better records of bugs, requests, and customer needs.
- Your team spends less time copying information from one tool to another.
- Customers stay in the loop without requiring manual follow-up every time.
- You can see which requests matter most based on customer value, revenue, or account tier.
✨ What’s New
- Instant activity triggers: Your workflows can react when issues, comments, projects, customer records, customer needs, documents, or initiative updates change.
- Create and update work items: You can create issues, comments, attachments, labels, projects, customer records, and customer needs directly from your CRM workflows.
- Two-way visibility: Add record links to tracked issues so your internal team can quickly jump back to the customer context.
- Faster customer follow-up: Automatically notify customers when a reported issue is resolved or a request moves forward.
- Better prioritization: Track feature requests and customer needs alongside revenue or account value so important requests are easier to spot.

🛠️ How to Use It
- Step 1: Open your CRM workflow builder and choose a workflow you want to update, or create a new one.
- Step 2: Add a trigger or action related to product work tracking, such as a new issue, updated issue, new customer need, or create issue action.
- Step 3: Connect your account and choose the workspace or team you want the workflow to access.
- Step 4: Set filters so the workflow only reacts to the activity that matters to your business, such as a specific team, label, project, or status.
- Step 5: Map the details from your CRM, like customer name, message, form submission, or account value, into the issue or request you want to create.
- Step 6: Test the workflow using a recent record so you can confirm the right data appears in the right fields before turning it on.
Here are a few practical ways a small business can use this:
- Turn support requests into tracked issues: When a customer submits a bug report, your CRM can create a detailed issue and attach the customer record for easy follow-up.
- Track feature requests: When a customer asks for something new, you can log it as a customer need and connect it to their company record.
- Send updates automatically: When a bug is marked complete, your CRM can send a plain-language email or text update to the customer.
- Share progress internally: Project or initiative updates can flow into sales notes, customer communication plans, or internal summaries.
- Keep records aligned: When a new customer is added or updated, the matching records can stay consistent across your systems.

To keep your setup clean, it helps to use clear labels for workflow-created issues, test your trigger before building the rest of the workflow, and always attach the customer record link when creating a new issue. That gives your team the full picture without digging through separate systems.


💡 Pro Tip
If you connect customer feedback to tracked product work and follow up automatically when it’s resolved, you can improve retention and create more repeat revenue from customers who feel heard.