Start with one agent. Scale into full support operations.
Pagerox pricing maps to how support teams actually mature: more agents, more interactions, more knowledge, and more team ownership as the operating model proves itself.
Plans
The current product already has a concrete plan model.
These limits come directly from the billing layer in the codebase and map to how Pagerox tracks usage today.
Feature breakdown
See how access expands as the support operation grows.
Pagerox pricing is tied to the main operating surfaces in the product today: agent count, support volume, knowledge footprint, team access, and the deeper rollout support larger teams usually need.
FAQ
Questions about limits, upgrades, and plan fit.
The easiest way to choose is to match the plan to how many support lanes, sources, and team members you expect to run in the near term.
What makes Pagerox different from a generic support bot?
Pagerox is organized around scoped agents, shared organization integrations, grounded knowledge retrieval, reviewed learnings, and operational analytics. The product is built for support operations, not just conversational output.
Can teams start with one narrow rollout first?
Yes. The platform is a strong fit for starting with one support lane, one agent, and one clear set of sources and channels before expanding to more surfaces.
How do learnings work?
Pagerox can turn resolved conversations into candidate facts, corrections, preferences, patterns, and escalations. Teams can review those learnings and decide what should stay active.
What kinds of systems can Pagerox connect to?
Today’s codebase already supports communication surfaces, engineering systems, knowledge sources, and Supabase-based data access, with organization-level connection ownership and agent-level bindings.
What happens when a team hits a limit?
The billing and limits layer is already built to track current usage against plan allowances for agents, interactions, knowledge items, and team members, which makes upgrade decisions visible inside the product.
Can teams start free and expand later?
Yes. The product model clearly supports that path, and the plan ladder maps directly to growing agent count, support volume, knowledge footprint, and team size.