How to write an effective product feedback post

No one knows CallTrackingMetrics better than you, our users. We love hearing about how you use our tools and what would make them better. 

Here are a few guidelines on how to share product feedback, so that our Product Team can review and potentially incorporate it into the product roadmap.

Feedback and constructive criticism are welcome. Disparaging, harassing, mean, or snarky remarks about CallTrackingMetrics, its employees, vendors, partners, or other community members will not be tolerated. We’re all friends and professionals, so let’s keep it polite. We don’t like having to remove comments, but we reserve the right to do so in order to maintain a positive community experience for everyone. 

Search first

As the community grows, there's a good chance someone will have already made a suggestion similar to yours. Keeping conversations in existing threads makes them easier for others to find, and helps keep the community organized. 

Vote for suggestions you like

Votes do matter! See a post or comment you like or agree with? Use that up arrow! Post a comment to share your detailed use case.

The most helpful feedback posts are the ones that describe the nature and scope of a problem. Try to answer these questions in your post or comment: 

  • What is the problem?
  • Why is it a problem?
  • How do you solve the problem today?
  • How would you ideally solve the problem?
  • How big is the problem? (business impact, frequency of impact, who is impacted)

It's much easier for the Product Team to address a suggestion if they clearly understand the context of the issue, the problem, and why it matters to you. 

Rest assured we will read your post

We read all of the feedback that comes through this forum. Yes, really! We take feedback seriously; it's driven many of the changes and improvements to our products over the years, and we believe it's a vital part of making CallTrackingMetrics better. 

Our team members may engage in conversations, ask follow-up questions, or even start threads on topics they’re exploring. If your post or comment doesn’t receive a response, don’t worry. We’ve seen it, and we’ll let you know if and when we have any updates to share. 

We don't share timelines

Occasionally, we’ll share very general ideas of what is or isn’t on a roadmap, or roughly when you might expect to see something roll out. However, we do not share specifics, and often can’t tell you exactly what’s on the roadmap for both competitive and legal reasons. If we do provide a timeline, know that it is subject to change.

Posts may be archived

In order to keep the community manageable, any conversations that go silent for several months may be archived. They're still visible to our Product Team and your feedback will still be taken under consideration, however, posts or threads with a low level of engagement typically indicate that they're not a significant need by many users. (Voting matters!)

The purpose of collecting feedback from users is for product managers to understand how customers use our products and what problems they're running into. We do not use this forum like case resolution, it's more for discussion and understanding of challenges. 

Thank you for reading this and for understanding how we address suggestions. We value all feedback and we're happy to have a place to engage in these conversations!





Post is closed for comments.

Didn't find what you were looking for?

New post