Pylon Review: The Help Desk That Followed Your Customers Into Slack

It's 11:47pm, and the biggest account just found a bug.

They didn't open a ticket. Nobody opens tickets anymore. They typed it into the shared Slack channel — the one with twelve people from their side and six from yours — as a reply, in a thread, three messages under somebody's GIF.

By morning, three people had seen it. All three assumed one of the others had it. Nobody replied.

That's the quiet failure mode of modern B2B support, and it isn't a people problem. Support moved into group chats years ago. The help desk never followed.

Pylon is what happens when someone builds the help desk inside the group chat instead.

So what is Pylon?

Pylon is a customer support platform built specifically for B2B companies — the ones whose customers are other businesses, not individual shoppers. Three engineers started it in 2022 — Marty Kausas, Advith Chelikani and Robert Eng, previously of Airbnb, Samsara and Affinity. The Information has covered it under the label "self-described 'Zendesk killer'", which is either bold or foolish depending on the week.

Here's the distinction that makes the whole thing click.

Zendesk and Intercom are a shop counter with a take-a-number dispenser. Brilliant design — for strangers. Someone buys sneakers, has one problem, complains once, disappears forever.

B2B support isn't strangers. It's the same twelve people from the same company, in the same channel, for three years, asking increasingly technical questions about an account worth six or seven figures. Same word, "support." Completely different physics.

Investors bought the argument: $51 million raised in total, with Andreessen Horowitz and Bain Capital Ventures co-leading a $31M Series B in August 2025. Linear, Airtable, Cognition, AssemblyAI, Retool and Hightouch all sit on the customer wall.

How it actually works

First, it goes to them. Pylon plugs into shared Slack channels, Microsoft Teams, Discord, email, chat widgets, web forms, Telegram, WhatsApp, SMS and — since the end of March 2026 — actual phone calls.

The part that's easy to miss: the customer never learns anything new. They keep typing in Slack exactly as before. On the support team's side of the glass, that messy thread quietly becomes a tracked ticket with an owner, a status and an SLA clock. Nobody has to say "could you please file that in our portal?" — a sentence that has never once improved a business relationship.

Second, it knows who's talking. Account Intelligence pulls CRM records, product usage logs, past conversations and even code into the conversation. The gap between that and a normal ticket queue is roughly the gap between a vending machine and a bartender who already knows the order.

Third, the AI layer. On July 15, 2026, Pylon relaunched around what it calls agentic support: a Support Agent that answers customers directly, an Assist Agent that investigates and acts on a human's behalf, Background Agents that run tasks on their own, a Slack Agent that lives inside Slack, and Skills — reusable written instructions that work like a playbook the AI actually follows. Since March 2026 those agents can also read connected tools like GitHub, Linear and Notion.

Kausas framed the point well: "The goal is not to deflect a few more tickets. It is to change what support teams do all day."

One caveat before getting excited: the whole agentic platform shipped as a beta. Twenty customers got early access before launch, it opened up five days later — and the docs for every one of those agents still carry a banner saying access is limited to beta participants.

What it looks like when it works

• Sardine cut first response time from 35 minutes to under 3.5 minutes.
• AssemblyAI resolves about half of eligible support inquiries with no human involved.
• Wispr Flow got 8x faster resolutions while ticket volume grew 76%.
• One team in the July launch post cut tier-one-to-tier-two escalations by 70%; another absorbed its volume without the three or four extra hires it had expected to make.

Fair warning: all four are Pylon's own case studies — useful for direction, not audited. The more independent signal came from The Information, which reported the company nearing $10 million in annual recurring revenue at 158% net revenue retention. That second number means existing customers spend more each year than they did the year before, which is usually a sign nobody's quietly hating the product.

Where it falls down

There's no mobile app. The most repeated complaint in real reviews. A senior director of customer support, on G2: "The biggest issue at the moment is that there's no mobile app, and the browser experience is challenging on a phone." Reviewers score Pylon 6.9 out of 10 on mobile support; rival Thena scores 8.4. For a product whose whole premise is meeting customers where they already are, that's an odd blind spot.

The flagship is a beta. Open beta, but a beta — and Pylon's own docs still describe agent access as limited. Buying today for the July 2026 vision means buying a roadmap, at roadmap risk.

The AI's ceiling is your documentation. This one deserves a highlighter. From a mid-market reviewer: "It depends on documentation being excellent, but unfortunately, we don't have excellent documentation." An AI agent working from thin docs is a new hire who got a three-page onboarding packet and was pointed at the phones. The tool is a mirror, not a magician — and that's true of every AI support product, not just this one.

Reporting is thin. One reviewer: "Dashboard setup is not user-friendly, creating and editing views requires more effort than it should." Deeper analytics and data-warehouse sync are pitched as enterprise capabilities, not defaults.

Teams is the weaker sibling. Slack is clearly home turf. One Microsoft Teams user: "The Teams integration is extremely wonky, and it's hard to avoid opening tickets that are not actual tickets."

There are a lot of buttons. As a head of customer success wrote: "The interface can sometimes feel a bit tricky to navigate, especially when there are many options shown at the same time." Teams with support-ops experience will be fine. Teams without will feel it.

Context on the scores: 4.7 out of 5 on G2 across roughly 111 reviews — and none of those reviewers work at enterprises. Three quarters are small businesses. This is a startup and scale-up tool right now.

What it costs

Pylon removed public pricing in mid-2026. The pricing URL now redirects to a demo booking form, which is its own kind of answer.

Its own AWS Marketplace listing is still live, though, and still shows real numbers on monthly terms: Starter $70, Professional $118, Enterprise $167 per seat per month, with annual contracts advertised as saving up to 25%. The same listing prices the add-ons separately — AI Assistant at $50 per seat, AI Agents from $100 each — and phone with SMS is another $35 per seat, no per-minute fees.

Those add-ons are the detail that matters, because of this number: procurement platform Vendr reports the median Pylon buyer pays $93,383 a year, in a range from roughly $16,000 to $105,000. A handful of Starter seats costs a couple of thousand a year. Almost all the distance between those two figures is add-ons and scale, not the sticker price of a seat.

A useful contrast: Intercom's Fin bills per outcome — about $0.99 a pop, and a handoff to a human can count. Pylon bills for capacity. Which is cheaper depends entirely on volume.

The fine print, in plain English

Pylon reads customer conversations, CRM data, product usage and code, so this part isn't optional reading.

The posture is strong: SOC 2 Type II, ISO 27001:2022 and ISO 42001 — the last being the standard for managing AI systems, which is the relevant one here. GDPR and GLBA compliant. AES-256 encryption at rest, TLS 1.2+ in transit. Single sign-on, automated user provisioning, exportable audit logs, annual third-party penetration tests.

The AI line is the one to read twice: Pylon states it holds zero data retention agreements with all AI providers, and that "your data is never used to train or improve AI models." Deletion on request happens within 72 hours.

Three things to raise before signing. All data sits in AWS data centers in the United States — a real question for anyone with EU or UK data residency rules. Healthcare agreements are "on request" in the docs but tied to the enterprise plan on the marketing site, so ask which it is. And granular access controls are pitched as an enterprise capability, not a default.

The verdict

Pylon answers one question very well: how do you run support when customers live in your Slack instead of your ticket portal?

Inside that lane it's excellent. The channel coverage is unmatched, the account context is real rather than decorative, and the agentic layer aims at the right target — changing the work, not inflating a deflection stat. Outside it, the case thins fast: no mobile app, thin reporting, a flagship still in beta, and an AI capped by whatever docs already exist.

It doesn't make support disappear. It stops support from living in forty unread threads.

If customers message in shared Slack or Teams channels, this earns a demo. If they file tickets like normal people, Zendesk is cheaper and finished.