How the workbooks work

Six workbooks cover every piece of your phone system. You supply the intent; we supply the numbering, validation, and build tracking. They are built to catch problems during discovery, not during cutover — everything you fill in feeds straight into the build and the acceptance testing.

Discovery is a joint effort

We gather. You validate. Neither works alone.

We pull what we can from your legacy system — extensions, DIDs, device MACs, hunt groups, IVR trees, calling privileges. But exports show configuration, not intent. Only you know who actually answers the phone, what's still in use, and what should change.

Your system might have years of drift in it: orphaned extensions, phantom queues, phones on desks nobody sits at. This migration is your chance to clean that up — not to carry it forward.

Conventions

You columns are yours to complete. RX3 columns we complete.

In the workbook itself these are amber and navy column headers. On this site they appear as the pills above.

• An asterisk marks anything required.
• Most fields are dropdowns, so there's no guessing at the right wording. Each workbook page here lists the allowed values for every field.
• Every workbook opens with a Read Me explaining what it covers and what to watch for.
• Every tab has one example row in gray — delete it before you send the workbook back.
• The workbooks reference each other, so names and emails need to match exactly, character for character.

Names are join keys

A queue named as an overflow destination must also exist as its own row. A member email must match a user in the Users & Devices workbook. Mismatched names are the most common cause of a stalled build.

Where to start

Start with Users & Devices — most other workbooks reference the people in it. Then work through the rest in any order.

See Call Queues for a fully documented example of what each workbook page looks like.