Plain

What Is Plain?

The assumption that B2B software companies need a traditional helpdesk (ticket numbers, queues, macros, CSAT surveys) deserves more scrutiny than it usually gets. Plain was built on the premise that most of those conventions exist for high-volume B2C contact centres, not for software companies where every customer is a paying business and every support conversation touches a live integration or a production environment.

Plain Limited is a London company, founded in 2020 by Simon Rohrbach (formerly Deliveroo's design lead) and Matt Vagni (formerly Deliveroo's design systems lead). The product is a customer support platform that replaces the ticket-based model with a threads-based inbox, unifying Slack, Microsoft Teams, Discord, email, and in-app chat into a single interface. In February 2025, the company raised $15 million in Series A funding from Battery Ventures, Index Ventures, and Connect Ventures. Customers include developer-focused SaaS businesses such as RevenueCat, Whop, and Tigris, companies whose customers are themselves developers or technical operators.

The positioning borrows from Stripe's approach to developer infrastructure: opinionated, well-documented, and designed for teams that want to build support into their product rather than bolt a helpdesk onto it. Plain offers a GraphQL API with a complete object model (customer, thread, message, event), a CLI for local development workflows, and webhooks for every platform event. For engineering teams that treat support tooling as part of the product, this makes Plain more composable than Zendesk or Intercom.

The honest counterpart to that positioning is that Plain is deliberately narrow. There is no knowledge base builder, no AI chatbot for deflection, no community forum module, and no self-service customer portal. If those features are requirements, Plain is the wrong tool. If they are not, it may be the cleanest option available for European B2B companies in the customer support category.

Key Features

Threads-Based Inbox, Not Ticket Numbers

Plain's core structural decision to use threads instead of tickets has practical consequences beyond aesthetics. Ticket numbers create a psychological distance between support agents and customers; they signal "you are in a queue" rather than "we are in a conversation." For B2B SaaS companies where every account represents thousands of dollars in ARR, that distinction affects how support teams approach conversations.

Plain's inbox shows threads (conversations) with customer names, recent activity, and status: open, waiting, snoozed, or resolved. Assignment, labelling, and priority queuing work as expected. The difference from conventional helpdesks is the absence of ticket number generation, macros, and canned response libraries as first-class features. The philosophy is that teams should respond to the specific customer context, not to a category of ticket.

Unified Multi-Channel Inbox

Slack, Microsoft Teams, Discord, email, and in-app chat all surface in the same Plain inbox. For developer-focused products with communities spread across Discord and Slack alongside standard email support, this matters significantly. Support agents no longer need to monitor separate applications to catch inbound messages; everything routes to a single queue with full thread history.

The Slack integration is bi-directional: a customer conversation from Discord or email is visible from within Slack, and a reply sent from Slack appears in the customer thread. For engineering teams that live in Slack, this is the highest-leverage integration: on-call engineers can handle urgent support escalations without switching applications.

Customer Context and Event Timeline

Plain pulls in customer attributes and event data from the product, displaying Stripe payment history, Segment events, and Posthog feature flags alongside the support conversation. When a customer reports a billing issue, the support agent sees the relevant Stripe charges in the thread without opening a separate tab. When a bug is reported, the engineering team can see the feature flag state and recent event stream that might explain the failure.

This integration depth requires configuration; setting up the data connections to Stripe, Segment, or Posthog is not automatic. For teams willing to invest in that setup, it produces a support inbox that gives agents meaningful context before they type a single word in response.

GraphQL API and CLI

Plain's developer surface is the feature that separates it from conventional helpdesk alternatives. The GraphQL API exposes the complete object model, enabling teams to create threads programmatically from product events, update customer attributes from backend services, or query conversation history for analytics without logging into the Plain interface.

The CLI supports local development and scripting, making Plain automation testable without a UI dependency. Combined with webhooks for all platform events, the result is a support platform that integrates into engineering workflows rather than sitting beside them. Teams have used this to auto-create support threads from error monitoring alerts, escalate from status page incidents to customer-facing threads, and sync support resolution status with internal incident trackers.

Integration with Linear and Jira

B2B support frequently produces engineering work: a bug report becomes a Linear ticket, a feature request becomes a Jira story. Plain's native integrations with Linear, Jira, and GitHub allow support agents to create engineering tasks directly from customer threads and surface status updates back into the support conversation when work is completed. The feedback loop from customer report to engineering resolution to customer notification becomes part of the Plain workflow rather than a manual coordination process across three applications.

Pricing

Plain's free plan covers 3 seats, 1,000 threads per month, and all integration channels including Slack, Teams, Discord, and email. For small engineering teams managing support for an early-stage product, this is a useful evaluation environment with real features rather than a degraded demo mode.

The Growth plan at $89 per seat per month (or $79 on annual billing) removes thread volume limits and adds automation rules, advanced customer attributes, SLA management, and priority assignment. For a 3-seat support team, the fully paid Growth tier costs $267 per month, significantly more than entry-tier Zendesk or comparable European alternatives like Crisp, but the comparison is imperfect. Plain's addressable market is B2B SaaS companies where a single churned customer represents months of MRR, not high-volume B2C contact centres optimising for low cost-per-ticket.

The Scale tier (custom pricing) adds SSO, advanced admin controls, custom data retention, and enterprise SLA terms. For the specific profile of company Plain targets, those features are table stakes for procurement approval.

There is no per-conversation pricing and no seat minimums; the free tier genuinely allows a single-person team to manage customer support without a credit card.

EU Compliance & Privacy

Plain Limited is a UK-registered company operating under UK GDPR, which imposes the same substantive obligations as EU GDPR. EU customer data is hosted in AWS eu-west-2 (London). The company holds SOC 2 Type II certification, which covers security, availability, and confidentiality controls.

For EU companies evaluating Plain as a data processor, the UK's adequacy decision means data transfers to Plain do not require Standard Contractual Clauses. A Data Processing Agreement is available for enterprise customers. Plain publishes a subprocessor list and maintains GDPR documentation on its security page.

The data hosting location in London is relevant for EU procurement teams that require European hosting: eu-west-2 is geographically in the EU by proximity but is an AWS UK region, not an AWS EU region. Teams with strict GDPR data localisation requirements should confirm whether AWS eu-west-2 satisfies their specific policy. For companies relying on the UK adequacy decision, there is no issue.

Open-source European alternatives exist in this space. Zammad is a German open-source helpdesk that self-hosters can deploy on EU infrastructure with complete data control. Plain's case against self-hosted alternatives is the ongoing development investment: new integrations, API improvements, and enterprise features ship regularly without requiring the buyer to maintain infrastructure.

Who It's Best For

If you run a developer tool, API product, or technical SaaS where your customers are engineers and operators, Plain's developer-first architecture fits the workflow pattern naturally. GraphQL API access, Linear integration, and multi-channel inbox unification are features that were designed for this customer profile.

If your support team lives in Slack and handles escalations from the engineering on-call rotation, Plain's bi-directional Slack integration removes the primary friction point in most B2B support workflows: switching between Slack and a helpdesk to respond to the same conversation.

If you need an AI deflection layer, a self-service knowledge base, or a customer-facing community portal, Plain does not cover those use cases. The product is focused narrowly on the agent inbox and conversation management; it expects you to handle deflection and self-service through other means.

If you are a European B2B company with procurement requirements around GDPR and data localisation, the UK entity, AWS eu-west-2 hosting, and SOC 2 Type II certification cover most standard enterprise requirements.

The Verdict

Plain makes a genuine bet that B2B software companies support customers differently from B2C contact centres, and it builds the product around that bet. The threads-based inbox, GraphQL API, and multi-channel unification are coherent expressions of that thesis. The trade-off is a deliberately narrow feature set (no AI chatbot, no knowledge base, no self-service portal), which makes Plain a poor fit for teams that need those capabilities. For developer-focused SaaS companies with a small, high-value customer base, it is the most technically composable European customer support tool available.

Frequently Asked Questions

Is Plain GDPR compliant?

Yes. Plain Limited is a UK company operating under UK GDPR, which mirrors EU GDPR requirements. EU customer data is hosted in AWS eu-west-2 (London). Plain holds SOC 2 Type II certification and provides a Data Processing Agreement for enterprise customers. The UK entity means post-Brexit data transfers are governed by the UK adequacy decision.

How does Plain compare to Zendesk?

Plain targets B2B SaaS companies with developer-heavy support workflows. Zendesk is a broader platform covering B2B and B2C at scale, with a knowledge base, AI deflection, and community forums. Plain has no ticket numbers, no knowledge base, and no AI chatbot. Its strength is in unifying Slack, Teams, and Discord with email into a developer-native inbox. For high-volume B2C support, Zendesk is the more appropriate choice.

Does Plain support Slack-based customer support?

Yes. Plain's Slack integration is bi-directional: support conversations from any channel (email, Discord, in-app chat) are surfaced in Slack, and replies sent from Slack appear in the customer thread. This lets engineering teams handle support escalations without leaving their primary communication tool.

Is there a free tier for Plain?

Yes. The free plan includes 3 seats, 1,000 threads per month, and all major integrations including Slack, Microsoft Teams, Discord, and email. It is sufficient for small engineering teams handling support for early-stage products, with no credit card required to start.

Where is Plain data hosted?

EU customer data is hosted in AWS eu-west-2 (London). Plain Limited is a UK-registered company, and the UK's adequacy status under EU GDPR means data transfers between EU companies and Plain are lawful without additional Standard Contractual Clauses. Enterprise contracts can specify additional data residency requirements.