Define your menu tree, DTMF options, open / closed / holiday rules — get a ready-to-build call-handler hierarchy with every handler, schedule, and routing rule you'll need to create in Unity Connection.
Unity Connection auto-attendants are built from Call Handlers — each menu is one handler, each option is a key-mapping to another handler or to a user/extension. Get the hierarchy wrong and you'll discover at 9am Monday that pressing 2 sends callers to nobody. This tool takes your menu tree, your business hours, and your holiday schedule, and emits the complete list of handlers, schedules, and transfer rules you need to create. Copy the list, build it in Unity Connection Admin, test with one call.
Fill in the menu, click Generate handler tree.
Named entry points. Each has a greeting, menu, and optional caller input actions.
Business / After-Hours / Holiday. Each handler references one schedule.
Ties the pilot DN to the top handler — the entry point.
A new auto-attendant fails in a specific, predictable way: the main greeting is perfect, and option 1 works, but option 3 silently transfers to an unassigned extension or dead-ends. The fix is a three-pass review before go-live. First pass: walk every branch yourself from an outside line. Press every digit at every menu level, including digits you didn't define (unassigned digit should replay the menu). Second pass: verify every after-hours branch by advancing the Unity system clock to 7pm with utils date (on a test system) or by temporarily setting After-Hours to "always active." Third pass: load the holiday schedule and verify the holiday handler's greeting and transfer destinations.
Where most engineers waste time is recording 12 greetings when 3 would do. Record the main greeting once, the after-hours greeting once, the closed/holiday greeting once, and let the sub-handlers for Sales/Support/etc. inherit silence (the caller just hears ringing of the next destination). Pre-recording every sub-menu greeting is optional polish; skip it for initial launch and add later based on user feedback.
Holiday schedules are the stalest part of Unity in most deployments — set once in 2018, never updated. Use our Holiday Schedule Generator to produce a fresh year each December. Unity accepts a CSV import of holiday dates, so the annual refresh is a 10-minute job, not a day.
Call Handler = one greeting + one menu. Directory Handler = spell-by-name caller input. Use Directory Handler when you have ≥ 50 users; skip it for small businesses.
Yes — Caller Input on a handler can transfer to any other handler by name.
Create a "Snow Day" handler with a different greeting and a direct transfer-to-voicemail. Create a routing rule keyed to a toggle DN (e.g., \*99) that reception dials to enable.
No. The Directory Handler is the only built-in name-search. Caller types last-name digits and Unity matches against user directory.
Pilot → main menu with 1=Sales, 2=Support, 0=Reception, 9=Dial-by-ext
Main → Departments (1=Pediatrics, 2=Cardiology, 3=Billing). Each department → sub-menu (schedule, nurse, billing).
Main → 1=Sales (goes to UCCX queue), 2=Support (UCCX queue), 3=Billing (direct DN), 0=Receptionist
Our UC Modernization Sprint redesigns your Unity auto-attendants, greetings, and routing for a professional caller experience — and migrates you off older Unity versions in the same window.