Skip to content
⌘K
InboxAsk a human

Welcome to Plain

Updated by Dustin

👋 I’m Dustin, a Customer Enablement Engineer here at Plain — welcome, and excited to have you on board! I've spent more than a decade building out support teams for some of the most successful tech companies in the world and have had the privilege of seeing a transformational shift in how companies approach how to run their respective support functions. As any tenured support person would likely tell you, orgs have historically measured the success of their support agents based on the speed, efficiency, and accuracy in which they address customer questions — therefore, the vast majority of teams were built to close things, rather than to learn from them.

We, here, at Plain believe this is a missed opportunity.

As we’re seeing and hearing more and more often, the modern support function isn’t a cost center — it is the elevator; it is the multiplier.

Why Plain?

Every conversation has the potential to make the next interaction just a little bit better, whether that's a fix that ships, a doc that gets written, or an answer that never has to be asked for again. That's why we'd rather your customers need less support over time, even if that means fewer conversations running through Plain — it's also why we think of support as part of your company's culture rather than the siloed responsibility of a single team.

Plain is the infrastructure that makes that possible. It's ready to use from day one, but it's also yours to build on and extend in an incredible number of ways — it matters more than it sounds, because no two teams support their customers quite the same way.

What does “good” support look like?

One of the overarching philosophies that guides how we continue to build the product is that, unlike other customer-centric functions like CS or Sales (which have fairly translatable runbooks), what "good" support looks like at one company could look and feel vastly different compared to another, even within the same industry.

Rather than trying to standardize "good" support and force a certain way of working, we, at Plain, embrace the concept that support leaders know how best to support their own customers — we simply provide the building blocks that allows them to bring that vision to life.

But, when you can build anything (and we really mean quite everything — our customers have easily extended the platform to meet their own unique use cases), it, ironically, becomes the bottleneck as you try to perfect your workflow right off the bat. Building is best as an iterative process, but you’ll need to get past the start line in order to start building some momentum.

That's what this series is for — think of it as a quick start primer for getting your Plain workspace set up for success by giving you an understanding of how Plain works underneath the hood. While it's not meant to be a comprehensive be-all, end-all resource (we have our technical docs, api docs, and our wonderful support + solutions teams to help with that), it will do a great job at getting you unstuck and, hopefully, spark some ideas that better inform your questions later on in your journey here at Plain.