Skip to content
⌘K
InboxAsk a human

Step 1: Connecting your primary support channels

Updated by Dustin

It's always exciting to see what's possible with any new tool, but you’ll need some threads to test with first. You can do this by setting up your support channels from within your Plain workspace settings — channels are essentially any surface area/entry point where your customers can reach out to your support team. Plain Email and Slack tend to be the most common entry points amongst most customers , so we'll start with those here — again, this is just a primer, so feel free to check out our technical documentation if you have additional channels you need to set up and test.

What good looks like

What we define as "good" for this step is ultimately two round trips (an inbound thread and an outbound reply), one for each channel:

Email

  • You send a test email to your support inbox

  • The email is forwarded to Plain and ingested into your workspace

  • A response sent from within Plain to the email is received successfully

Slack

  • You receive a message from a customer (or a test account) in a connected Slack channel

  • The message is ingested into your Plain workspace as a thread

  • Responding to the thread from within Plain threads a reply to the original message in Slack

You’ll want to see a working proof of concept of Plain as your communications hub — customers write in to Slack + Email as they normally do, your team sees these messages in Plain, and your team is able to respond directly to those customers from within the workspace.

What to consider

Consider channel ownership here — both Email and Slack setup require some admin configuration, which means you may need an admin to configure both channels properly. If you're tracking against a strict timeline, make sure to give yourself 2-3 days of cushion to account for the logistics of having setup span across multiple tools and teams.

How to implement

Email

It's best to think of setting up email as two distinct steps: receiving (your mailbox forwards to Plain) and sending (your domain tells the world Plain is allowed to send as you). You'll initiate both steps within Plain, in Settings → Channels → Email, though some additional configuration will need to be handled in your email provider and DNS provider respectively.

Setting up Email as a channel also lets you set up the Support Portal for your customers via the Help Center.

email verify

Step 1: Set your customer service email address

This is your primary customer support email address — additional emails can easily be added in the future, but the primary email address is the address where your customer notifications will default to.

Your primary address must be on a domain your company owns, the same domain you chose when you created the workspace (Setting up your Plain Workspace). Public email providers (Gmail, Outlook.com, and so on) aren't accepted, and a domain can only be used by one workspace at a time.

  1. Navigate to Settings (the gear icon in the sidebar)

  2. Click on Channels

  3. Locate Email and click the Set up button

  4. In the input field, add your support email, then click Save and continue

Note: You may see an error message, stating: "This domain is already taken by a different workspace. Only one workspace can use a domain at a time. If you can’t access that workspace anymore, contact help@plain.com."

This is more common with larger orgs, who could have multiple teams with distinct workspaces on Plain. For smaller support functions, this is generally because there's a demo or test workspace with the same domain that may have been set up previously. If you run into this, please reach out to our support team over Slack or by sending an email to help@plain.com. Our team has the ability to locate and either delete these additional workspaces, or, if you'd like, share the same domain across multiple workspaces — we'll quickly get you unblocked if you let us know what path you'd like to take.

Step 2. Receiving (forwarding)

Once you've completed Step 1, you'll unlock the next block in the email setup wizard, which determines how your inbound emails get ingested into your Plain workspace. This is done via forwarding at the admin level in your email provider — though the steps differ from provider to provider, it ultimately boils down to grabbing your workspace private forwarding address (this is what we provide you in Step 2 — it looks something like something@inbound.postmarkapp.com) and setting up a forwarding rule in your email provider that auto-forwards emails from your support inbox to Plain.

There are detailed guides for how to do this in Google Admin and Microsoft 365 — if you have an email provider that falls outside these two, we provide helpful tips on how to get that set up as well.

Once the rule is in place, tick Inbound email forwarding is set up and click Save and continue. Plain doesn't test the rule for you, so this checkbox is your self-confirmation that you’ve added it.

Step 3. Sending (DNS configuration)

After completing Step 2, the block underneath will unlock to reveal two DNS records: a TXT record for DKIM (proves the mail came from someone allowed to send for your domain) and a CNAME record for the Return-Path (where bounces and complaints go). Both are issued by Postmark, the email service Plain sends through.

Why are these needed?

When you send email as support@yourcompany.com, the recipient’s mail server has to answer two questions before it trusts the message:

  1. Did this actually come from someone allowed to send for @yourcompany.com?

  2. If something goes wrong (bounce, spam report), where should complaints go?

DNS is how the internet publishes those answers for your domain. Plain/Postmark can’t “pretend” to be @yourcompany.com without your domain publicly saying that’s OK.

You, your IT team, or your email admin will need to add both at your DNS provider — there are guides for DNSimple, Namecheap, GoDaddy, Cloudflare, and Route 53 — then come back to this block and click Verify DNS and continue.

Step 4. Enable email

Once both DNS records are verified, the last block unlocks with an Enable email button. Until you click it, Plain still ingests forwarded mail, but any reply you send from Plain is blocked with a "workspace email not enabled" error, so don't skip this one.

Slack

It's helpful to have a grasp of how the Slack integration works to better understand how each component works, and how they work together. The integration acts a bridge between Slack and your Plain Workspace, sending data to/from both platforms. There are 3 main points of connection: workspace, individual/personal, and channel — each of these connections are established in slightly different ways.

Workspace

This is the primary, required connection — without it, the integration doesn't work. An authorized person connects Slack through Plain (OAuth), which installs Plain’s Slack app and gives Plain a bot in that Slack workspace. When this connection is established, Plain also stores which Slack workspace is tied to which Plain workspace so events and API calls land in the right place. This connection doesn't by itself mean “all Slack messages become threads” — it only means Plain is allowed to operate in that Slack workspace.

To connect:

  1. Head to Settings (the gear icon in the sidebar)

  2. Click on Channels

  3. Locate Slack and click the Set up button

  4. Click Connect Slack workspace and follow the steps to connect

slack connect

Individual/Personal

While the workspace connection is about the app, the personal connection is about you. Slack cares which human (or bot) sent a message and has strict rules around impersonation. Plain separates the concept of “the workspace is linked” from “this Plain user is linked to their Slack identity” so replies can behave like normal Slack participation when possible.

Each teammate who wants to reply from Plain signs in with their own Slack account, either in Plain settings or from the composer the first time they reply to a Slack thread (it shows Connect to Slack to reply until they do). Plain then sends their replies from their Slack account. It also helps Plain know who you are in Slack for things like permissions and what channels you have access to see + manage — if you’re not in a channel (especially a private one), Plain still delivers your reply, but it's posted by the Plain bot with your name and avatar instead of from your Slack account. You can read Slack threads in Plain without signing in, but replying needs it: until you sign in, the composer on a Slack thread shows Connect to Slack to reply instead of a reply box.

To connect, each individual should:

  1. Head to Settings (the gear icon in the sidebar)

  2. Click on Channels

  3. Locate Slack and click the Configure button

  4. If you have more than one Slack workspace connected, click the one you want (with a single workspace, Plain opens it for you)

  5. In the Sign in to reply section, click on the Sign in button and follow the steps to connect

slack sign in

Channel(s)

If the workspace connection puts Plain’s bot in your Slack workspace, and the personal connection ties your identity in Plain to your identity in Slack, the Channel connection is about tying the bot to each individual Slack channel. Slack only lets an app see and post in channels where that app (the Plain bot) is a member — this is desirable since support often isn’t “all of Slack” but, rather, it’s “each channel where the bot was invited and Plain was told what that channel is for.”

For every channel you want connected to your Plain workspace, the Plain bot has to join that channel in Slack. There are two ways to get it there: add a rule in Plain (Add channels in your Slack settings), which joins every public channel matching the rule now and any created later, or send /invite @Plain in the channel itself. Private channels don’t get caught by the rule, so they require the invite. Once the bot has joined, it gains visibility of the channel and acts on behalf of Plain — how it acts is determined by how you've configured that channel in Plain. If the bot isn’t in a channel, then Plain has no channel-level connection there — that channel is, for all intents and purposes, invisible to the integration.

As a quick and easy way to start testing, you can click on the Create a test channel option in the Customer channels page — this will create a new channel in your Slack workspace and automatically add the Plain bot to it.

slack customer channels

Every Slack channel the Plain bot joins gets a channel type, which you manage within Plain. There are two types, plus a disconnected state:

  • Customer — messages in customer-channels become threads in Plain. These are your customer channels where your external communication happens.

  • Discussion — these are your internal channels. No customer threads are created from messages here.

  • Disconnected — Plain stays in the channel but ignores messages in it. Connect it again as a Customer or Discussion channel to use it again.

Channel type is inferred automatically when the Plain bot joins.

You can set the ingestion mode for individual customer channels, which decides which messages become threads, and how those messages are grouped in Plain:

  • Time-based (default) — messages from the same person within 2 hours, or different people within 1 hour, group into one thread.

  • AI-based (recommended) — groups by meaning rather than timing. Falls back to time-based if Plain AI is disabled.

  • One-to-one — every Slack thread is its own Plain thread.

  • Manual emoji — a thread is only created when someone reacts with the chosen emoji (👀 is popular). Plain users only by default; set the channel's audience to Anyone to let customers trigger it too.

  • API-only — nothing is natively ingested; you create threads yourself through the API.

Some gotchas to be aware of:

  • Discussion channels never create customer threads. If a customer channel isn't producing threads, check its type first.

  • Messages from anyone on your own domain, or from anyone who's a Plain user, are treated as internal and don't create threads. That's by design, but it means that testing with a work account likely won't work. Use a personal email to create a thread in a customer channel, or click "Create a test channel" in the Slack setup wizard.

    slack test channel
  • Time-based and AI-based grouping stops once the last message has a reply. The next top-level message starts a fresh thread even if it's sent within the determined time period.

  • You can sync up to 25 channels on the Foundation plan — workspaces on our Horizon and Frontier plans can sync as many as possible.

How to verify if this step is working/complete

  1. Email your support address from a personal account. A thread should appear in the All Threads view in Plain. Reply to it from Plain. The reply shows up in your personal inbox, from support@yourdomain.com, and not in spam.

  2. Post in a Customer-typed channel (ideally, in the test customer channel you created during the Channel(s) step above) as a Slack Connect guest (or ask a friendly customer to — you can reach out to Plain Support to help with this). A thread should appear in the All Threads view in Plain. Reply from Plain and confirm it posts back to Slack under your name.

Troubleshooting/FAQ

Email arrives in Plain but my reply never shows up (or lands in spam).

Sending isn't verified, so the recipient's mail server has no public record that Plain is allowed to send as your support address.

Try this: Open Settings → Channels → Email and confirm both DNS records show as verified. On Cloudflare, confirm the CNAME is DNS only, not proxied. If both records are already verified, the deliverability troubleshooting guide is the next place to look.

No email arrives at all.

Plain only creates a thread from mail that reaches the Postmark inbound address, and it ignores mail sent from the support address itself. Here are the two reasons a test never shows up:

The forwarding rule isn't pointed at the Postmark inbound address

  • The rule is missing, or it forwards to an address other than the one Plain shows in the email setup.

  • Try this: Re-copy the inbound address from Settings → Channels → Email and compare it character-for-character with the forwarding rule in your email provider.

The test was sent from the support address itself

  • Plain treats your support address as the workspace, not a customer, so a message from support@yourcompany.com to support@yourcompany.com is dropped. An email coming from your personal work address is fine: Plain creates a customer record for it and a thread appears as normal.

  • Try this: Send the test from any other address, personal or work.

A Slack message didn't create a thread.

A message only becomes its own thread when Plain's bot is in the channel, the channel is typed Customer, the ingestion mode is set to create one, and the sender is a customer (not a Plain user or someone on your company's email domain). Here are the five reasons it doesn't:

Plain's bot isn't in the channel

  • Plain only sees messages in channels its bot has joined. If the bot isn't there, nothing from that channel reaches Plain.

  • Try this: Open your Slack settings in Plain and confirm the channel is listed under Customer channels. If it isn't, add a rule that matches it, or send /invite @Plain in the channel.

The channel is typed Discussion, or is disconnected

  • Discussion channels are internal, and Plain ignores messages in disconnected channels. Neither creates a customer thread.

  • Try this: Open your Slack settings in Plain and confirm the channel is listed under Customer channels, not Disconnected channels.

The sender is on your domain, or is a Plain user

  • A message from a Plain user doesn't create a thread, and neither does one from someone on your company's email domain who doesn't have a Plain login (Plain adds them as a user).

  • Try this: Post from a personal Slack account, or use Create a test channel in the Slack setup wizard.

Ingestion is set to Manual emoji or API-only

  • Manual emoji creates a thread only when someone reacts with the chosen emoji. API-only doesn't ingest messages. You create those threads through the API.

  • Try this: Open the channel's ingestion mode in Plain. If it's Manual emoji, react with the chosen emoji, and set the audience to Anyone if a customer should be able to trigger it. If it's API-only, create the thread through the API.

Time-based or AI grouping folded it into an existing thread

  • Time-based grouping puts messages from the same person within 2 hours, or from different people within 1 hour, on one thread. AI grouping does the same by meaning. Grouping stops once the last message has a reply, and the next top-level message starts a new thread.

  • Try this: Open the recent thread from that channel and confirm whether the message is already on it.