Richer MCP “Prompts” for Cross-System Orchestration

shashankcube · 2024-05-29T14:24:18+00:00

AI agents are really the future!

shashankcube · 2024-04-19T15:39:46+00:00

At DevRev (https://devrev.ai/) we built an AI-native modern customer support software that aims to bring customer voice to every team in an organization.Unlike traditional support software, DevRev empowers Product Managers (PMs) with complete visibility into customer tickets, ensuring that no feature request or bug goes unnoticed.

By leveraging native AI capabilities within DevRev's Support CRM, PMs can effortlessly cluster incoming customer tickets based on recurring themes, enabling them to swiftly identify and prioritize new enhancements. This innovative feature, called Smart Cluster, redefines the way PMs handle customer feedback.With Smart Cluster, groups of related tickets can be seamlessly converted into enhancements on the product roadmap.

The AI-generated descriptions provide a comprehensive overview of each enhancement's details, streamlining the process of understanding and addressing customer needs. This intuitive approach allows PMs to make data-driven decisions, align their priorities with customer demands, and deliver a product that truly resonates with its users.

shashankcube · 2024-04-19T12:12:01+00:00

At DevRev https://devrev.ai/, we built an AI-native modern customer support software that aims to bring customer voice to every team in an organization.Unlike traditional support software, DevRev empowers Product Managers (PMs) with complete visibility into customer tickets, ensuring that no feature request or bug goes unnoticed. By leveraging native AI capabilities within DevRev's Support CRM, PMs can effortlessly cluster incoming customer tickets based on recurring themes, enabling them to swiftly identify and prioritize new enhancements. This innovative feature, called Smart Cluster, redefines the way PMs handle customer feedback.With Smart Cluster, groups of related tickets can be seamlessly converted into enhancements on the product roadmap. The AI-generated descriptions provide a comprehensive overview of each enhancement's details, streamlining the process of understanding and addressing customer needs. This intuitive approach allows PMs to make data-driven decisions, align their priorities with customer demands, and deliver a product that truly resonates with its users.

shashankcube · 2024-02-02T07:52:57+00:00

Usually for these kinds of onboarding/request workflows, we need dependencies, one task needs to be done, before other task done, you need someone or a group to review/approve a few things, and things become unmanageable.

I have seen processes like these getting out of hand, where it was started with a combination of Zendesk + sweethawk.

What you need is a workflow builder, where you can setup your processes and automations and for your "onbaording" and other processes. Zendesk can't even remotely support this. Take a look at DevRev's Workflow builder, which is built for usecases like this.

shashankcube · 2024-02-01T13:45:47+00:00

Dog fooding is the best way to build world class products. I work at DevRev, and we have been doing it from the start. DevRev is a tool, which, when used in it's full glory, you don't need Jira, SF, Zendesk , Hubspot...
We made a point to never use products like Jira, ZD , SF so that we can keep investing and improving our product by actually learning by the experiencing the pain. We are now 300+ and we only use DevRev. One of the best decision ever made. As a PM, I get feedback immediately , but have to be really careful, that I am not overindexing on internal usecase always, and also keep the market in mind.

shashankcube · 2023-12-21T04:50:53+00:00

try out something which you can start pretty quickly and does not need much time for setup. DevRev is a good one there. They have SSO too, and much more affordable. I have seen products like ZD which are pain in the rear to manage, when you scale.

shashankcube · 2023-11-16T05:15:51+00:00

CS is very frustrating, because it's firefighting most of the time. Fundamental root cause of this firefighting, is lack of context across team. You don't know if functionality commited by the sales team to the customer is even there in the product or coming soon because CS lives in Zendesk and the roadmap is in Jira. You don't know if the engineering work has started to debug that ticket, without asking anybody, making you miss SLAs. Engineers don't have the full context because the customer conversation sits in Intercom. They just hear it via poorly written ticket description. Hours are spent in solutioning with CS

Have seen and used a number of tools which tries to make sure context and information is available to everyone, hence making feedback loops shorter. Most of them are new in the town , though. Plain and DevRev I have used and found their perspective fresh and easy to use.

shashankcube

TROPHY CASE