Plain
Not Just Tickets Ltd ·www.plain.com· As of: 2026-07-30
Our verdict
An inbox for customer requests is baseline equipment, and every tool in this class provides one. The reason to pick this one sits a layer deeper: companies, customer groups and service level agreements are first-class objects in the API, and customer cards pull live data from your own product into the thread. Teams that actually build that coupling turn support into part of the product. Teams that do not build it pay for an expensive inbox and could have stayed with baseline equipment. Hence core rather than baseline, but with that condition attached.
Who it fits
Solo
suitable with caveats
Thirty-five dollars for one seat does not hurt, but the structure of accounts, customer groups and response times solves a problem nobody has with a handful of customers. The API advantage requires engineering time a solo operator does not have.
Mid-market
suitable
Exactly the fit: named business customers, some of them in shared Slack channels, contractually promised response times and a product from which context can be pulled into the thread. Moving up to the plan with SLAs and a help centre costs 299 dollars a month for three seats.
Enterprise
suitable with caveats
Single sign-on and user provisioning only appear in the top tier, which carries no list price. There is no public commitment on tamper-evident audit logging, and production data sits in London, so outside the EU. For a procurement department these are three points to settle in writing before signing.
Buy, switch or build
Off-the-shelf
Established ticketing system of the broad class
The grown systems are cheaper to start with, carry more extensions and have a guide for every question. They organise work around the ticket and the channel, however, not around the account and the contract. Shared Slack channels with business customers arrive as an add-on rather than sitting at the core, and the link to your own product data stays a sidebar display instead of an object you work with.
AI-native
Resolution agent billed per resolved case
The new class bills not per seat but per deflected case, and pays off where many similar requests arrive from many end users. In business with named corporate customers the arithmetic flips: the value lies not in deflection but in the context a human with contract knowledge brings. Measuring support by resolution rate optimises the wrong number here.
Build it yourself
Shared Slack channels plus your own database
With three to ten corporate customers this is the honest route: shared channels, a spreadsheet of commitments, a model for summarising. It breaks at holiday cover, at provable response times and at the question of what actually happened last month. More importantly, the part worth building yourself is the coupling to your own product data, not the inbox. That coupling is exactly what this tool exposes as an API.
Our advice
- Solo: Stay with the shared inbox until the first customer asks about response times.
- Mid-market: Buy, but plan the customer cards from your own product data in from the start.
- Enterprise: Before signing, settle the UK storage location, audit logging and the top tier price in writing.
Who is behind it
Staying power: Funded
Six years in market, an active company with up-to-date register filings, a fifteen million dollar growth round and named reference customers. That carries for the next few years, but this is not an established vendor with proven profitability.
- Legal entity and company number: Not Just Tickets Ltd, Companies House 12736513, incorporated on 13.07.2020, status active, registered office in Altrincham (Cheshire) · Source · As of 2026-07-30
- Funding: USD 15 million growth round in February 2025, led by Battery Ventures, with Index Ventures and Connect Ventures from the earlier round · Source · As of 2026-07-30
- Ongoing register activity: Share allotment (SH01) on 29.06.2026, confirmation statement filed as at 12.07.2026, most recent annual accounts as at 31.01.2025 · Source · As of 2026-07-30
- Audit attestation: SOC 2 Type II, first attested on 01.06.2023; report available only through the trust centre on request · Source · As of 2026-07-30
- Named reference customers: Sanity, Laravel, Stytch, Raycast · Source · As of 2026-07-30
Cost of leaving: Moderate
Everything held in the system is readable through the GraphQL API, and webhooks emit more than twenty event types. There is no documented bulk export, however, so you write the retrieval yourself. On top of that, cancellation requires thirty days' notice to the end of the term, deletion happens only on request by email, and the terms let the vendor keep aggregated data and data that has become integral to the service. The real switching cost sits in the customer cards and automations you built yourself, not in the thread data.
Regulation and data
| Data processing agreement | yes, publicly available data processing agreementThe document is public without login and covers instructions, subprocessors, deletion and return. The contracting party is Not Just Tickets Ltd under the law of England and Wales.Source · As of 2026-07-30 |
|---|---|
| Storage location | Amazon Web Services, region eu-west-2 (London), so the United KingdomThe security page names the region explicitly and the API runs under the host core-api.uk.plain.com. The privacy policy speaks more broadly of servers in the United Kingdom and the EEA. A selectable EU region is not documented anywhere.Source · As of 2026-07-30 |
| Subprocessors | list exists, but not readily readable in publicThe data processing addendum points to a list in the trust centre at trust.plain.com/subprocessors. That page is rendered in the browser and could not be read without an account, so no names are substantiated here. New subprocessors are announced with a seven day objection window.Source · As of 2026-07-30 |
| Third-country transfer | yes, United Kingdom as the main location plus service providers in the United StatesFrom an EU perspective the United Kingdom is a third country, for which the Commission renewed the adequacy decision on 19 December 2025 through 27 December 2031. For the US service providers the privacy policy names standard contractual clauses, and the addendum additionally names the EU clauses 2021/914 (modules two and four) plus the UK addendum.Source · As of 2026-07-30 |
| Training on customer data | no, contractually excludedThe addendum commits that customer personal data will not be used, by the vendor or any subprocessor, to train, develop or improve any general or shared models. That is one of the clearer wordings in this class of tool.Source · As of 2026-07-30 |
| Retention and deletion | no fixed retention period for active workspaces; inactive workspaces are deleted after six months with fourteen days' noticeMessages taken from Slack are cached for no longer than seven days. Deletion requests run by email to support. The privacy policy names no concrete retention periods, and the terms expressly hold back aggregated data.Source · As of 2026-07-30 |
| Certifications | SOC 2 Type II at the vendor; no ISO 27001 certificate of its own substantiatedThe attestation dates from 1 June 2023 and covers the development process, application, infrastructure and access controls. The report is released only on request through the trust centre. ISO 27001 is named on no public page.Source · As of 2026-07-30 |
| EU AI Act, Article 50 | unclearThe product ships an agent called Ari and an assistant called Sidekick, both of which speak to customers directly. No statement on the transparency duties under Article 50 of the AI Regulation appears on the security page, in the help centre or in the legal texts.no source given · As of 2026-07-30 |
| Audit logging | unclearThe top tier lists advanced security together with single sign-on and user provisioning, but says nothing about traceable logs of access and changes. The help centre and security page name only the vendor's internal access controls, not logs that customers can review.no source given · As of 2026-07-30 |
What it really costs
Entry price
Thirty-five dollars per seat per month on the entry plan, one seat included, plus 2,000 credits a month for the assistant. A seven day trial without a payment method, viewer seats are unlimited on every plan, and young companies get a fifty percent discount.
Source · As of2026-07-30
What gets expensive
At the tier jump, not through growth. Response times, escalation paths, help centre, Microsoft Teams and the CRM connection only appear on the middle plan: 299 dollars a month for three seats, with every further seat then costing 99 rather than 35 dollars. That is close to triple the seat price for features you need the moment you have contractually promised response times. Single sign-on, user provisioning and advanced security sit in the top tier, for which no list price is published. Monthly credits expire, and only purchased ones roll over.
What it displaces
- Ticketing system without account context
- Shared inbox for customer requests
- Separate spreadsheet of response times per customer
Interfaces
- GraphQL API for customers, companies, customer groups and tickets
- Webhooks with more than twenty event types
- Customer cards that pull data from your own systems into the ticket in real time
- Slack, Microsoft Teams, Discord, email, chat and help centre
- Linear and Jira, CRM integration from the mid tier upwards
At Convios: Not used by us
Not used in our own operation. All statements come from public vendor pages, legal texts and the UK company register.
Evidence
- 1.Plans, seat prices, included credits and tier boundaries · As of 2026-07-30
- 2.Storage in AWS eu-west-2 London, encryption, deletion of inactive workspaces, Slack cache, SOC 2 Type II · As of 2026-07-30
- 3.Data processing addendum, training exclusion, standard contractual clauses, seven day objection window for subprocessors · As of 2026-07-30
- 4.Legal entity Not Just Tickets Ltd, company number 12736513, thirty day notice period, retention of aggregated data, price changes with thirty days' notice · As of 2026-07-30
- 5.Incorporated 13 July 2020, status active, share allotment 29 June 2026, confirmation statement 12 July 2026 · As of 2026-07-30
- 6.Fifteen million dollar growth round in February 2025 and named reference customers · As of 2026-07-30
- 7.Companies, customer groups, service level agreements and customer cards as first-class API objects · As of 2026-07-30
- 8.Credits are consumed only by the assistant, monthly ones expire, purchased ones roll over · As of 2026-07-30
- 9.Renewal of the EU adequacy decision for the United Kingdom on 19 December 2025 through 27 December 2031 · As of 2026-07-30
Last reviewed: 2026-07-30byDr. Oliver Gausmann, Convios GmbH
Details out of date? Let us know.