Dolphin finds and tracks feature requests, pain points, and customer love from your B2B calls - on autopilot. No more "what's the status of this feature?" or "just add it to Productboard".
Keep track of your customer requests and escape tracking stuff on Slack or spreadsheets. GTM teams get the insights they need to drive revenue and retention, while product teams get clear data to prioritise what to build.
Subscribe
Sign in
Pretty Prompt
We spent a year building a feedback repository. Then realized, most insights come from customer calls. So we pivoted to focusing only on this and launched the new Dolphin AI: a better way to close the loop between your GTM teams (Sales, Customer Success, Customer Experience) and your Product team.
Dolphin connects to your call recorder, and extracts feature requests, pain points, and customer love without you having to do anything. (It doesn't join any call, it pulls it automatically from Gong, etc.)
You get all insights tracked and logged by Dolphin, enriched with ARR impact, and more. Best part? Dolphin packages each insight under a shareable link with the context, customer quote, and the video snippet.
Our 3 insights:
- You don't want more feedback for the sake of it. You want insights that help you drive retention and growth. This is exactly what Dolphin pulls and tracks for you: Feature Requests, Pain Points (for Success and Product) and Customer Love (for Marketing).
- GTM teams want to be heard. Dolphin helps them build an argument on why Product should focus on their customer requests, with the business impact and revenue. (It also tracks the status to close the loop back with their customers).
- Product teams want to validate what to build based on real customer needs and impact. Dolphin helps them automatically adding ARR impact, customers, and merging similar requests with AI. Basically an intelligent backlog.
Excited to hear your thoughts!
(Give it a go - it's free to try it out).
Manna
This could save our product team hours every week! But how does it differentiate between casual feedback ("This UI is okay") versus actionable feature requests in calls?
Pretty Prompt
@desmond_ren1 Such a great question! Dolphin is trained to only look for Feature Requests, Pain Points and Customer Love.
That means that it will segment the insight into the right bucket, based on the verbatim and context - though you can always "Accept" or "Reject" the insight so it doesn't fill up with random requests :)
So true pain points will be labeled as such, while requests will be labeled as feature requests.
Requests gives a glimpse on what they are asking, but pains gives an indicator of where the opportunities might be from a product perspective. (Though is up to each team to decide what to focus on, this is supposed to be like a teammate, to work with you).
Give it a go! We're working behind the scenes to make it better and more accurate, but looks pretty accurate on our calls! If you find anything missing let me know, we'd love to get it right!
Hey Ilai, Dolphin sounds like a total game-changer for GTM and product teams—love how it bridges the feedback loop automatically. You should list it on Aixyz .Co—it's free and helps more AI-focused folks discover gems like this. Would be awesome to see it there!
Pretty Prompt
@kamruzzaman_mayed Sure! Will give it a go now!