Start your phone flow

Build greetings, IVR menus, and after-hours flows with a guided product path instead of a telecom project spiral.

Product

The guided setup, examples, and voice direction layer behind phon.ist.

How it works See the guided setup, output bundle, and compatibility story. Templates Browse the core template library and open the right preload path into the studio. Examples Browse real caller situations before you open the studio. Voices Preview curated voice directions for inbound phone flows.
Solutions

Start from the operating reality you already have instead of a generic blank state.

Hotels Reservations, front desk, and multilingual guest routing. Multi-location One inbound layer across sites, teams, and schedules. IT resellers Scope faster and hand off clearer into implementation. Service business Cleaner first contact, queue messaging, and after-hours logic.
Resources

Structured reference surfaces for teams that need more context before they open the studio.

Guides Operational guidance for teams rolling out greetings, IVR, and after-hours flows. Docs Product and deployment reference for the guided setup and output model. API Integration and delivery context for partner and reseller workflows.
Pricing
Pricing
Start your phone flow
Pricing

Flow-based pricing for teams that need the output to ship.

phon.ist is packaged around the caller flow and its delivery bundle, not around seats, agents, or platform migration theatre.

Start your phone flow Talk about rollout
Piggy bank illustration used in the pricing hero.
Plans

Three plans for three levels of caller-flow depth.

The structure is deliberately flow-based: start from one caller moment, expand into routing, then move into rollout-grade delivery when the scope requires it.

Best for a single greeting Starter
$9 / flow

A light entry point for one clear caller moment and a quick first deployment.

  • 1 spoken output language
  • Standard voice direction
  • Greeting or short after-hours flow
  • WAV export package
  • Template-led kickoff
Start starter flow Good for a first release or one clean caller moment.
Recommended for most teams Pro
$19 / flow

The main plan for greeting, IVR, and a more complete operational caller path.

  • 2 spoken output languages
  • Premium voice directions
  • IVR menu builder
  • Export pack bundle
  • Queue and after-hours handling
Start pro flow Built for the full guided-setup story: greeting, routing, and handoff.
For broader delivery scope Business
$49 / flow

For multi-location, partner-led, or premium rollout contexts that need more depth.

  • Multi-location and reseller fit
  • Priority rendering queue
  • Advanced export variants
  • Expanded language coverage
  • Implementation-ready handoff notes
Contact for business Best when one flow has to support rollout, teams, or partner delivery.
Compare

What expands as the flow becomes more operational.

The comparison focuses on delivery scope, languages, routing depth, and the quality of the handoff that comes out of the guided setup.

Capability Starter Pro Business
Greeting setup Included Included Included
IVR menus Light Full Full
After-hours handling Short fallback Structured Structured
Queue / wait messaging Optional Included Included
Languages 1 2 Flexible
Voice directions Standard Premium set Premium set
Output bundle Core package Expanded package Advanced package
Export variants Basic Expanded Advanced
Flow handoff notes Short Detailed Deployment-ready
Review depth Self-serve Guided review Priority review
Support fit Single site Main team setup Multi-site or partner rollout
Best fit Single flow Main package Advanced rollout
Add-ons

Useful expansions without turning pricing into a seat model.

Languages, review, and export depth can expand the same flow when the caller journey needs more than the base package.

Extra language

Extend an existing flow to a second caller-facing language without rebuilding the whole setup.

Human review

Add an editorial or operational pass before the bundle moves into deployment.

Export packs

Prepare multiple delivery variants for PBX, partner, or multi-environment handoff.

Buying guidance

Short answers for teams validating scope and rollout fit.

The goal is to keep the commercial story as product-shaped as the setup itself: focused, operational, and easy to scan.

What is a flow in phon.ist terms?
A flow is one structured inbound caller path: greeting, routing logic, optional queue or fallback audio, and the export bundle required to hand it off cleanly.
Why is pricing per flow instead of per seat?
The product value sits in a deployable caller flow and its output bundle. Flow-based framing keeps the commercial story aligned with the product itself.
When is Starter enough?
Starter fits one focused caller moment: for example a business greeting, a short after-hours asset, or a first low-complexity rollout.
When does Pro become the right package?
Pro is the main plan when the flow includes greeting, route selection, and a fuller operational path across queueing, fallback, or multiple spoken outputs.
When would a team move to Business?
Business fits multi-location operations, reseller delivery contexts, or flows that need broader export and implementation depth.
Are add-ons still flow-based?
Yes. Extra language, review, and export options expand the same flow rather than introducing seats, agent counts, or platform licensing logic.
Can teams start in the studio before pricing is finalized?
Yes. The studio path and preload logic are already stable enough for product review, while commercial packaging can keep tightening behind the scenes.