Use case

CSM and Care: why Partoo stopped using Planhat and is betting on Salesforce, Intercom's Fin and AI

After two attempts with Planhat, Partoo favors Salesforce, Intercom, and AI for its CSM and support. Insights from its Ops Director.

Clément BouillaudClément BouillaudDirector of Operations, Partoo15 November 20269 min read
Partoo, en interne

Clément Bouillaud, Director of Operations at Partoo, discusses the two attempts to deploy Planhat, the challenges faced by Customer Success Managers, and the evolution of support tools. He explains why the company now prefers to rely on Salesforce, Intercom, management routines, and internally developed AI agents, rather than adding a new platform to its stack.


Partoo attempted to deploy Planhat, a Customer Success Platform designed to centralize customer information and track their product usage. After several months of work, the company ultimately abandoned the project. The teams did not sufficiently adopt the tool, while its deployment consumed a lot of internal resources.

This experience led Clément Bouillaud to challenge the field more: starting from the concrete problems of CSMs before choosing software. Partoo now favors targeted solutions, relying on its existing tools and the possibilities offered by AI.

Why did Partoo want to deploy Planhat?

Partoo has been using Salesforce for more than eight and a half years, both for its salespeople and Customer Success Managers. Over time, the CRM has been adapted to manage customer information, onboarding processes, and account tracking.

But in the early 2020s, Customer Success Platforms began to attract more interest in the SaaS ecosystem. Their promise is enticing: to bring together commercial data, usage information, and customer interactions in an interface specifically designed for CSMs.

At Partoo, the need is real. The teams support numerous accounts and must be able to quickly understand each client's situation: product usage, encountered difficulties, exchange history, or business development opportunities.

One of the main objectives was therefore to bring product back-office data into Planhat, to make it directly accessible to CSMs. The platform was also supposed to help identify accounts requiring special attention.

On paper, the project met several needs. But its deployment turned out to be more complicated than expected.

Two unsuccessful attempts to deploy Planhat

Partoo began working with Planhat around 2022, according to Clément's recollections. The company dedicated about six months to a year to the project, with two successive attempts.

The first did not achieve the expected adoption. Partoo then decided to try again, providing more support to managers and teams during the change. But the results did not improve sufficiently.

Clément identifies several reasons for this failure. First, the teams were not necessarily ready to change their habits and use an additional interface. Then, some aspects of Planhat's technology did not seem reassuring enough at the time.

Finally, the deployment required a lot of time from the operations person in charge of the project. An investment difficult to justify as long as the CSMs did not truly embrace the solution.

After these two attempts, Partoo decided to abandon the deployment of Planhat. In hindsight, Clément believes that the company probably chose this solution too quickly, hoping to address problems raised by the teams with a tool, without exploring simpler and more pragmatic alternatives.

Why Clément Bouillaud remains skeptical about Customer Success platforms

This experience reinforced a conviction in Clément: a Customer Success Platform is not necessarily the best answer to the difficulties of a CS team.

“Very often, a Customer Success Platform is somewhat the go-to tool that we hope will solve many problems. Whereas most of the time, when we dig into the pain points of the teams and take the top three, Customer Success Platforms are not really the answer.”
Clément Bouillaud, Director of Operations at Partoo

He has seen these platforms work in other companies. But their interest depends, in his view, on the context, the maturity of the processes, and especially the problems the teams are actually trying to solve.

The advent of AI reinforces his questions. Agents can now retrieve information from multiple systems, prepare analyses, or trigger certain actions without requiring a new business interface.

Clément thus believes that some features of Customer Success Platforms could be replicated by workflows and AI agents. At Partoo, the goal is not to completely rebuild Planhat internally, but to gradually develop solutions tailored to the teams' needs.

The main challenge for CSMs: accessing the right information

For Clément, one of the main challenges for Customer Success Managers remains accessing information. This often begins right from the handover between salespeople and CSMs.

The information collected during the sale is not always properly documented or transmitted. CSMs then have to rediscover the client's expectations, the commitments made, the key contacts, or the topics discussed during meetings.

Modjo helps improve this transmission. Thanks to recordings and transcriptions of sales conversations, a CSM can find out what was actually said during the sale, rather than relying solely on the notes entered in Salesforce.

But the problem goes beyond the sales history. CSMs also need to understand how their clients use Partoo's products: level of adoption, performance, features used, or difficulties encountered.

However, this information is scattered between Salesforce, product back offices, and support tools. Manually gathering them can take a lot of time. This was precisely one of the problems that Planhat was supposed to solve.

AI agents for preparing quarterly and annual presentations

Recently, Partoo has started exploring another approach: developing AI agents capable of retrieving the necessary information for a specific use case, without trying to centralize everything in a new platform.

One of the first projects involves preparing quarterly and annual presentations for clients.

Historically, CSMs spent a lot of time collecting data, analyzing results, and building their materials. Partoo is now developing an internal AI agent, still being consolidated at the time of the interview, to automate part of this work.

“Today, we are able, with AI, to prepare these presentations without adding another software layer. AI can find the right information in the right place, as long as we give it the directions.”
Clément Bouillaud, Director of Operations at Partoo

The benefit is simple: instead of constantly copying all Product data into an additional platform, the agent retrieves the information when the CSM needs it, then facilitates its integration into the presentation.

This solution is still in development, but it illustrates the direction Partoo is taking: using AI to simplify certain tasks for CSMs without multiplying software.

Salesforce: prioritizing useful signals over a health score

Salesforce remains the central repository for a large part of commercial and client tracking at Partoo. However, the company does not aim to bring all available information into it.

Some data exchanges are relatively simple. Intercom has an integration with Salesforce, which notably allows sharing information about client tickets. Other flows go through data tools. Clément mentions the use of a data warehouse and reverse ETL mechanisms to circulate information between product back offices and Salesforce.

But beyond the technical aspect, Clément emphasizes one point: adding data to Salesforce is only useful if it helps CSMs make better decisions.

He gives the example of the last login of a client's account administrators. At Partoo, org admins have administrative rights on their company's account. If an administrator hasn't logged in for a while, it can be a sign of disengagement. The CSM can then contact the client to understand what's happening.

This information is useful because it triggers an action. Conversely, bringing up dozens of usage metrics without knowing how to interpret them mainly risks complicating the teams' work.

This also explains Clément's reservations about automated health scores. The idea, regularly discussed at Partoo, would be to assign each client a synthetic score reflecting their health status. A platform like Planhat could have facilitated this calculation by aggregating different data.

But Partoo has never actually deployed an automated health score. Clément remains skeptical about the ability of a single indicator to accurately represent a client's situation, and especially to be actionable.

He prefers to identify specific risk signals: an administrator who no longer logs in, a product difficulty, or a concerning exchange with a client. This information is easier to understand and allows teams to know how to react.

This does not prevent automating certain alerts. But Partoo favors a limited number of understandable and directly actionable indicators, rather than a global score that is sometimes difficult to interpret.

Weekly portfolio reviews to better anticipate churn

One of the significant changes described by Clément does not concern software, but the organization of teams. Partoo has strengthened the management routines of its Customer Success Managers, notably through weekly portfolio reviews.

Each week, the CSMs and their managers review the clients' situations, discuss identified risks, and update their forecasts. The information is then gradually consolidated at the company level.

The goal is to build a more reliable churn forecast, relying on the field teams' account knowledge.

According to him, this management discipline can bring as much value as a new software platform. Responsibilities are clearer, risks are regularly discussed, and managers have better visibility over their portfolio.

Why Partoo kept Intercom and abandoned Zoho Desk

In terms of customer support, Partoo has been using Intercom for about ten years, even before Salesforce arrived in the company.

When Salesforce became the central CRM, the question of migrating to Salesforce Service Cloud could have arisen. But Partoo already had a functional tool, well integrated into the teams' habits. Changing platforms would have required rebuilding part of the support processes. Clément also considered Intercom as a specialized solution particularly suited to these uses.

Partoo therefore preferred to keep both software, each with its role: Salesforce for commercial and client tracking, Intercom for support interactions.

For a period, the company also used Zoho Desk alongside Intercom. Both tools were used to distribute certain communication channels, notably emails and chats. This organization was implemented at the initiative of an employee.

After his departure, Partoo decided to simplify its operations by consolidating interactions in Intercom.

The abandonment of Zoho Desk did not stem from any particular dissatisfaction with its features. It was mainly to avoid maintaining two different tools for similar needs.

Intercom thus became the central platform for the support teams again.

How Partoo professionalized its use of Intercom

For a long time, Intercom was configured directly by the business teams, without any real centralized technical management.

Employees adapted the settings and processes as needed. This organization accompanied Partoo's growth, but it also showed its limits.

About three years ago, the company began to take the tool's configuration more seriously. For the past two years, this work has become a priority, with one goal: to improve the productivity of the Customer Care teams.

Clément acknowledges that Partoo has long responded to the growth of its client portfolio by increasing support staff.

The company is now looking to better organize ticket processing, simplify processes, and automate certain requests, rather than systematically responding to increased volumes with new hires.

It is in this context that Partoo began deploying Fin, Intercom's AI agent.

Fin: between 30 and 40% automation in equipped areas

Fin allows certain support requests to be handled automatically, without human intervention.

At Partoo, the goal is to automate the questions most suited to this type of processing while maintaining a quality of service consistent with the expectations of different clients.

Clément mentions an initial estimate of the results obtained:

“We must be at 30 or 40% automation when Intercom's Fin AI is deployed. I think it's an area where we have great potential to improve internal efficiency, but we also realize that it's quite a dense subject.”
Clément Bouillaud, Director of Operations at Partoo

Because automating support is not just about activating an AI agent.

Teams must determine which requests can be handled automatically, which require human intervention, and how to adapt these rules according to client profiles.

It is also necessary to improve the instructions given to Fin, structure the available knowledge, and regularly analyze the relevance of the responses.

Clément appreciates the features offered by Intercom to evolve these automations and monitor their quality. But he emphasizes the configuration and continuous improvement work that this represents.

Support automation requires as much work on processes as on technology.

Modjo, Ringover, and Qobra: sales tools extended to CS teams

Beyond Salesforce and Intercom, Partoo uses several cross-functional tools that increasingly concern Customer Success teams.

Modjo allows the retention of recordings and transcriptions of client meetings. CSMs can thus find important information in conversations, better prepare their exchanges, and understand an account's history.

Partoo is also exploring the possibility of leveraging these transcriptions to detect commercial expansion opportunities.

For example, a client might mention a new need during a meeting without an opportunity being immediately created in Salesforce. Analyzing conversations could help identify these situations and bring them to the teams' attention.

For phone calls, CS teams also use Ringover.

Finally, Partoo plans to extend Qobra to Customer Success Managers. Already used to calculate sales commissions, the software should simplify the management of variable compensation for CS teams.

Today, these calculations are performed on a quarterly basis and require several steps of consolidation and validation. The goal is to ensure the reliability of the commission history and reduce the time spent on their calculation.

Summary of the software this article mentions in Partoo's stack

StatusWorkflowToolUsage
ReplacedCustomer Success PlatformPlanhatReplacedTwo deployment attempts abandoned. Data centralization and CS tracking
In useCRMSalesforceCommercial and client repository, account tracking
In useCustomer supportIntercomManagement of interactions and customer tickets
In useConversation intelligenceModjoRecordings, transcriptions, and exploration of expansion signals
Replaced by celui-ciCustomer supportZoho DeskReplaced by celui-ciFormer tool used alongside Intercom, then abandoned in favor of it
In useAI support agentFinAutomation of customer responses, progressive deployment
In useTelephonyRingoverCalls from Customer Success teams
In useCommission managementQobraSales commissions, planned extension to CSM for variable compensation

See Partoo full stack →

Sign up to keep reading

It's free, and gives you access to the rest of this use case and every other article we publish.

Sign up

Already on Soft Atlas? Log in