Why Pengo doesn't charge per seat

Most live chat and helpdesk tools charge per agent seat. On the surface that looks fine - you pay for what you use. In practice it creates a strange incentive: every time your support team grows, so does your bill, even if conversation volume stays flat.

We saw this first-hand before building Pengo. Adding a new support hire meant a line-item conversation with finance, not just an onboarding checklist. Teams would share logins to dodge the seat count, which is worse for security and makes per-agent analytics meaningless anyway.

What we do instead

Every Pengo plan includes a set number of seats (3 on Starter, 10 on Growth, 25 on Scale). You can add your entire support team within that limit without checking a pricing page first.

The metered part of Pengo’s pricing is AI message credits: standard replies cost 1 credit, advanced actions like booking cost 10, and human agent replies are always free. You pay for automation volume, not headcount.

Why this holds up as you scale

If you’re a five-person team, the difference between per-seat and flat-tier pricing might not matter much yet. If you’re a fifty-person support org, per-seat math compounds fast. Team members should not be a variable cost center; the value they create for your customers is the point of hiring them in the first place.

We’d rather build a pricing model that gets more attractive as you scale, not less.