Examples

Examples built around actual caller situations.

Each example stays narrow: one operating problem, one structured answer, one direct path into the wizard.

Project management illustration used in the examples hero.

Use cases

A product library, not a gallery of generic use-case cards.

Every example below is tied to a caller situation, an audio preview, and the kind of bundle a team would actually hand off into deployment.

Hotel

Calm front desk routing

Premium first contact for reservations, arrival questions, and late check-in.

Problem The desk gets repetitive calls with different urgency and language expectations.

Solution A greeting-led flow that sorts front desk, reservation, and after-hours questions without sounding like a phone maze.

01 Greeting

Brand tone and language cue in the first sentence.

02 Menu

Reservation and front-desk paths split early.

03 After-hours

Late arrivals get clear fallback instructions.

Start hotel flow

Greeting Hotel example

Preview

Voice preview 0:00 0:00

Marketing sample Scrub preview

Greeting-led example for hospitality setups.

hotel-greeting.wav Greeting asset 184 kB
reservation-menu.wav Route selection 212 kB
arrival-notes.txt Front desk handoff 4 kB

IT support

Ticketing without caller confusion

Menu-based sorting before the team spends time on the wrong queue.

Problem Support numbers receive mixed requests, wrong extensions, and repeated status calls.

Solution A tighter IVR entry with a clear greeting, support menu, and wait handling that reduces manual triage.

01 Greeting

State service scope and expected action clearly.

02 Menu

Sort support, billing, and urgent issues fast.

03 Queue

Use wait messaging instead of dead air.

Start IVR flow

IVR IVR example

Preview

Voice preview 0:00 0:00

Marketing sample Scrub preview

Support-focused menu sample.

support-menu.wav IVR asset 228 kB
queue-message.wav Queue layer 176 kB
support-flow.txt Routing notes 5 kB

Multi-location

One inbound layer across sites

Central routing that stays readable even when schedules differ.

Problem Different sites, schedules, and fallback rules make phone routing drift fast.

Solution A guided flow that makes the entry greeting, branch logic, and location-aware routing explicit from the start.

01 Entry

One central greeting sets the structure.

02 Routing

Locations and teams branch cleanly.

03 Schedules

Fallback logic stays attached to opening hours.

Start multi-location flow

Fallback After-hours example

Preview

Voice preview 0:00 0:00

Marketing sample Scrub preview

Fallback sample for location-aware openings.

main-greeting.wav Entry asset 181 kB
site-routing.wav Location split 236 kB
hours-map.txt Schedule notes 6 kB

Service business

Professional first contact for everyday inbound calls

A lighter setup for greetings, wait messaging, and after-hours clarity.

Problem Teams answer similar questions all day and callers get inconsistent guidance after hours.

Solution A service-led preset with a friendly greeting, queue messaging, and a dependable fallback layer.

01 Welcome

Set expectation and tone immediately.

02 Wait

Use audio instead of uncertainty during delay.

03 Fallback

After-hours handling stays clear and short.

Start service flow

Queue Service example

Preview

Voice preview 0:00 0:00

Marketing sample Scrub preview

Queue-style example for service teams.

service-greeting.wav Greeting asset 164 kB
queue-loop.wav Wait layer 194 kB
fallback-flow.txt After-hours notes 4 kB