Six questions to a scoped build.

Volume, channels, the system your jobs live in, whether you dial out, whether you handle protected health information, and how many locations. Those six answers determine the lane, the integration work, the compliance overhead, and therefore the price. The configurator does that arithmetic in front of you.

What each answer changes

• Volume sets the lane and whether the monthly is defensible at all.
• Channels decide whether this is one agent or two.
• Your dispatch or CRM decides whether integration is days or weeks.
• Outbound and healthcare each add compliance work with a real cost.
• Multiple locations means routing and per-branch reporting — a Scale build.

Why the output is a range

Integration effort is the variable that cannot be known before discovery. A documented API is days; an undocumented one behind a partner programme is weeks. The range reflects that honestly rather than quoting the optimistic end and revising after you have committed.

When it says do not buy

Under roughly 150 monthly conversations, or where the answer set shows a capacity problem rather than a coverage problem, the configurator says so and recommends nothing. That output is rare, and it is the reason the rest of its output is worth anything.