We’re considering it so the sales and customer support teams can better understand each account’s questions and needs. I see a lot of potential, but I’m concerned that a space for sharing experiences could end up becoming just another sales channel.
That’s my biggest concern too. The upside is context: an account manager could see recurring questions and offer relevant help without asking customers to explain everything again. But posting about a challenge shouldn’t automatically trigger a sales call. We’d need clear boundaries around how that information gets used.
I agree! For me, the main advantage would be linking community suggestions to the companies in the CRM. We could understand which needs are shared by multiple clients. However, be careful not to prioritize only the requests from clients with larger contracts: even a small company can propose a very useful idea.
Good point! I also see a technical challenge: How do we reliably assign community members to the correct CRM contacts? Different email addresses, duplicate records, or a change of employer can quickly lead to incorrect assignments. Before we talk about evaluations, we should clarify which system is authoritative in case of conflicting data.
And we also need to define which data truly deserves to be synchronized. Does the CRM need every comment, or just a summary of the tracked topics and open requests? I would prefer to start with a small amount of useful data, while clearly explaining to members how their contributions will be used.
A limited starting point makes sense. I’d pilot it with support escalations: let a community question become a CRM case when someone needs individual help, then show an appropriate status update back in the community. That could reduce chasing, provided private customer details stay out of public replies. Who would own that workflow?
This discussion has convinced me that our first step should be a small pilot focused on support escalations. We could connect a community question to a CRM case and measure whether that helps members get answers faster. Before launching, I’d also want members to understand what information is shared and who can access it.
Pour que ce projet fonctionne, les équipes support et communauté devront définir ensemble leurs responsabilités. Il faudra notamment décider qui prend le relais lorsqu’une demande reste sans réponse ou nécessite un suivi privé. Ce serait aussi l’occasion de demander aux membres si cette nouvelle approche leur évite de répéter leur problème.
Con questi riscontri potremmo capire quali aspetti migliorare prima di ampliare l’integrazione. Il passo successivo potrebbe essere collegare i suggerimenti sui prodotti alle esigenze delle diverse aziende, senza trascurare quelle più piccole. Alla fine, considererei il progetto riuscito se rendesse più semplice ottenere aiuto e rafforzasse la fiducia nella community.
