Advice on Building a Customer Support Department

[u/BakerSave]

Hi everyone!

I’m looking for some advice on building a Customer Support department completely from scratch.

I’m about to start a new role as Head of Customer Support, and in this case “from scratch” really means from scratch. The product hasn’t launched yet, so there are no customer requests, no existing support processes, no CRM/helpdesk system, no knowledge base, basically nothing.

I’ve been asked to put together a rough plan for how I would build and organize Customer Support before the actual customer-facing work begins.

That’s honestly a little intimidating, because there’s very little real data to work with at this stage. For the first period, I’ll also be doing everything myself until the workload grows enough to start building a team.

For those of you who have built or helped build a Customer Support function from the ground up, what would you focus on first?

What would you try to have in place before launch, and what would you deliberately leave until you actually have real customers and support data?

I’m doing my best to prepare properly, but I’m worried that the pressure of having such a blank slate might make me overthink things or miss something important.

Any advice, examples, frameworks, mistakes to avoid, or resources would be greatly appreciated!

[u/VA_Network_Nerd]

https://www.gartner.com/reviews/market/crm-customer-engagement-center

https://www.gartner.com/reviews/markets/customer-relationship-management

You need to crawl into bed with a CRM solution.
You might find a CRM that can integrate technical support resource management, or you might choose to maintain separate systems that interact.

SalesForce has a complete solution, but make sure you understand their pricing models.

Understand how Sales Operations is thinking about selling and tracking sales to feed back into the General Ledger.

It's nice if there is some kind of connectivity between the CRM and the Sales Management platform, but it isn't critical.

Unless you have very specific needs, I'd totally SaaS the CRM and I'd encourage the Sales Order Platform to be SaaS as well.

[u/OkStatistician9190]

I’d keep the pre-launch work to a thin operating skeleton: one intake channel, clear severity and priority definitions, initial response targets, an escalation path, and a small internal knowledge base with known issues and runbooks. Test it with 10 to 20 fake tickets based on the main product flows. Pick a basic shared inbox or helpdesk only when it helps you capture tags and response times; don’t overbuild a CRM or a library of macros before you have real volume. After launch, review contact reasons weekly and let actual patterns drive automations and hiring.

[u/817654]

One thing worth clarifying, is this B2B or B2C? The org structure and response time expectations are wildly different. For B2B you probably want to define SLAs before launch even if they're rough. For B2C its more about self-service coverage.

[u/BakerSave → u/817654]

Thanks! From what they tried to explain to me, it’s a B2B SaaS e-commerce product for marketing. But honestly, that still doesn’t give me that much inform. Or rather, it feels like this information won’t really change many of the decisions I’ve already made

[u/Nauas_ark]

Couple of points I would suggest (from tech background):

- You will need a ticketing platform or CRM to handle inbound customer queries. If you are new to ticketing systems, allocate some time to researching which one would work best for you, also look at cost, capabilities and integrations. Configuring and learning a new ticketing system may also take some time, so be mindful of that.

- Depending on what business you are in, sit down with your tech team to review how certain queries will get escalated ( if it's a technology app, how bug reports or other tech issues will be handled), compliance department to review complaint escalation timeframes & complaints handling etc etc...

- build a strong Knowledgebase and document everything. As Head of Customer Support, everybody will be looking to you for answers( your new team, your customer), so be sure to know the products inside out and know who to reach out to in case you don't have an answer

- once you hire your new team, be sure to invest quality time and effort into training them. Having a knowledgeable and resourceful team will take a lot of burden off your shoulder so you can focus on what really matters. Have training materials and coaching plans in place, it will make a big difference.

Hope this helps. Even if you don't have it all figured out, don't worry. You will learn as you go and you will be fine! Good luck!