
•
•

Summarize blog with








Customer support is one of the most critical functions inside your company. When you have superstar support teams, customers will stick with you for longer.
Support teams contribute to the success of the larger Customer Success org in a company. That said, not all support teams might be reporting to the same function.
Preflighters weigh in on org structure regarding Customer Support. They discuss questions including:
Support, Implementation, and Customer Success, including Account Managers, all report to the senior VP of Customer Success, but we call our team Client Experience. The designation of someone overseeing all these functions could be senior VP of Client Experience. Titles get changed and updated a lot within our organization.
The Chief Customer Officer is an executive that oversees all things post-sales! They are responsible for everything: customer onboarding, implementations, success, renewals, and retention; they find solutions to all the problems of larger customer experience, lifetime value, and profitability. This title is at the top of our Support, Services, and Success reporting structure. Other titles interchangeable or under whom the support org might fall are:
It’s not ideal for Support to report to Sales; the CCO would be the ideal candidate for that if there is one, else it could be a Chief of Success. That goes for Customer Success and Support—even when/if a significant component of the CSM role is upselling/expansion.
My research over the years has shown that in most cases, Support is a component of the Customer Success org, reporting to the VP of Success or the CCO if that’s where Success reports. And that is how I recommend it be done for the best usage of data, communications channels, and Support quality.
See also: Customer onboarding and the organizational chart (video)
At Recast, we have a Director of Customer Success who leads the following teams:
We're growing consistently, and some of these teams have their team leads overseeing the work of the managers.
As a Support leader, over the years, I have reported to the following people inside a company, and my opinion of reporting to each:
I prefer when Customer Success and Technical Support are sister orgs under a common VP. If that can't happen, being under Engineering has its own benefits when negotiating for bug fixes and supportability items. Operations is a peaceful parking spot where they leave you alone! Sales org is NOT the place for Support as you will always be fighting for budget.
I’d say it depends for many orgs, but a good rule to follow is to have all customer-facing, post-sale groups report to the CCO.
Do you have the same org structure, or does your support org report to a different function? How has this impacted its outcomes? Join Preflight and tell us!
Join Preflight, our private, invite-only Slack community, and join conversations like this. You will also gain access to peers and share knowledge on customer onboarding, implementation, and customer success.
What I appreciated most about Rocketlane is its seamless approach to onboarding and project management. The ability to collaborate in real-time, set clear timelines, and track progress across multiple teams makes it incredibly efficient. The built-in document-sharing and communication tools reduce the need to switch between platforms. It’s especially useful for client-facing projects, where transparency and accountability are key


AI that executes your delivery work (Add to any plan)
Most popular
Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.
Most popular
Great for teams desiring tailored workflows with comprehensive reporting capabilities.
Most popular
Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.
A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.





70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.

70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.
Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.
Get a better all-in-one PSA
Get a better all-in-one PSA
Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.






.webp)