Skip to content
⌘K
InboxAsk a human

Step 0: Setting up your Plain workspace

Updated by Dustin

To get started, you'll need a workspace. This is your support org’s homepage — in many ways, you can think of it like a computer, where components can be mixed and matched to optimize the kind of work you plan on doing. If you’re here, you likely have one that you or your agent created, or one of our Sales/Success team members helped create for you — with that said, you can follow the steps below if that ends up not being the case:

  1. Head to app.plain.com/get-started and sign up with Google or your work email.

  2. When Plain asks you to Name your workspace, type your company name into Workspace name.

  3. Click Save and continue.

Already have one? Sign in at app.plain.com and pick it from Choose your workspace.

Choose your path

Ultimately, we can distill setup to eight, simple steps:

  • Connecting your inbound support channels to Plain

  • Understanding Plain's data model

  • Enriching your data with accounts, fields, and tiers

  • Importing historical data and/or migrating from an existing support tool

  • Creating your routing/triage rules + SLA policies

  • Workflows (if you're coming from Zendesk, these are a more powerful version of automations/macros — think Zapier or n8n)

  • Configuring your internal and customer-facing AI Agents

  • Migrating your knowledge base into Plain

Again, with Plain being as flexible as it is, these steps can branch off into any number of directions. However, after analyzing our Demos, Sales calls, and Success check-ins, we've chosen to delineate these steps across the two types of functions we see that most often have the greatest difference in their setup requirements: 1. small, but mighty, teams looking to appear larger than they are, and 2. teams entering a period of hypergrowth and scale, looking to use agentic workflows to manage unprecedented volume.

Small, but mighty teams

These are teams of 1-10 people, often pulling double duty as engineers, customer success managers, and account executives. Teams in this segment are generally operating support out of 1-2 channels (usually Email and/or Slack), move fast, and are generally much closer to the product and other org functions.

  1. Step 1: Connecting your primary support channels

  2. Step 2: Understanding Plain's data model — customers, accounts, and threads

  3. Step 3: Bringing your customers and accounts into Plain

  4. Step 4: Migrating to Plain — import or fresh start?

  5. Step 5: Getting your threads to the right person

  6. Step 6: Your first workflow

  7. Step 7: Getting started with Plain AI — setting up the Customer Agent and Sidekick

  8. Step 8: Setting up your Help Center and Customer Inbox — migrating your docs and turning on self-serve

Plan on about 1-2 working days of actual configuration, including an initial backfill of historical data.

Hypergrowth + scale teams

These are actual support orgs who have more complex needs, including, but not limited to:

  • Supporting several distinct products or brands

  • Having specialized, multi-timezone, multi-lingual, and/or tiered teams

  • 3+ support channels (generally chat, email, Slack) with an interest in adding a support portal that's integrated with the product

  • More robust access controls and permissions

These teams are generally on our Horizon and/or Frontier plans.

  1. Step 1: Meeting your customer where they are

  2. Step 2: Understanding Plain's data model at scale

  3. Step 3: Aligning Plain to your CRM and/or backend

  4. Step 4: Creating your cutover plan

  5. Step 5: Handling complex routing and triage

  6. Step 6: Designing and governing a large workflow library

  7. Step 7: Implementing AI and agentic workflows

  8. Step 8: Developing your self-serve strategy

Plan on 1-2 weeks of configuration, running in parallel with an assumed 100k+ thread historical backfill.

What "done" means

Again, by no means is this a comprehensive guide for all of the things that are possible on Plain. With that said, we're confident this will enable your team to start working in Plain right now with negligible/minimal downtime and give you a better understanding of what areas you can extend/build on later.