Where 8,117 calls actually go

1. The spine: one sentence routes the whole firm

The recorded greeting on the main number offers exactly two things. Transcribed verbatim from 2,016 recordings:

"Thank you for calling Newlin Disability. If you are a first time caller and would like a free evaluation of your Social Security disability claim, please press 1. For all other inquiries, please press 0 and an operator will assist you."

Every existing client in the firm is verbally instructed to press 0. They do: 69% of everyone who calls lands in a queue staffed by two people. Keys 2 through 9 and # are unassigned, so a caller with a hearing date question hears nothing that describes them.

2. What people are actually calling about

The 2,016 operator calls that carry transcripts, classified against a fixed taxonomy on the caller's first stated reason. A reason was stated on 1,720 of them.

3. The one path that works

Client Concierge on ext 6518 is dialled directly. It skips the greeting, skips the menu and skips the operator, landing straight on a team of eight. It is the best performing entry point in the entire estate by a wide margin.

4. Entry points that answer nobody

Every row below is a live number or extension a client can reach today.

And when a message is left, it is usually the end of the road

2,970 calls ended in a mailbox, from 1,638 people. A callback was counted as any outbound call to that number afterwards, across both Vonage and the Conduit dialer on Twilio, with 110,762 Twilio calls scanned. That is a generous test.

5. What else is in the garage

Pulled from the Vonage account inventory (259 extensions, 257 users) and cross referenced against thirteen days of traffic. The provisioning API exposes account, users, extensions and locations only. Call groups, queues and receptionists are portal objects and cannot be read programmatically, which is itself a finding: the routing layer has no API and therefore no automated audit.

Two things hiding in plain sight

The account is still named "Fleschner Law", and the second busiest receptionist is still "Fleschner Main VR", carrying 506 calls across 812-232-2000 and 800-618-4878. A quarter of that traffic, 127 legs, goes to extension 9000, which has no name anywhere in the CDR or the inventory. Its neighbour 9002 is "PI After Hours - Capture Now Forward".

The hold audio is a radio stream. Transcripts of held calls contain news bulletins and speech. It is polluting the transcript corpus and may be affecting QA scores.

6. Where calls enter, and the doors nobody opens

Reconciled from the portal exports for phone numbers, extensions, users, call groups, call queues and receptionists, against thirteen days of traffic.

Every team already has a direct number. Nobody publishes them.

This is the most important row in the audit. The direct-to-team routing described in section 8 does not need to be built. It exists, it is staffed, and it is dark.

Client Concierge is not better designed. It is the only one anyone publishes. Of its 62 assigned numbers, five have ever taken a call.

The number we put on the client's phone does not lead back to us

Outbound caller ID is set per extension, and the CDR records the originating extension rather than the number presented, so this is the extension inventory joined to outbound call volume. 17,930 outbound calls with a resolvable caller ID.

76.1% of outbound calls present a shared number. A client rung by a case worker who dials the number back lands in a phone menu, not on the person who called them.

And almost nobody rings the shared numbers back

The two that point at call groups answer nothing. The one that points at a queue is fine.

Calls where the caller withheld their number are rejected by an account-wide anti-spam setting and show as Blocked. Excluding those, here is what the three numbers actually did between 1 June and 14 August:

454 identifiable calls to the two group-backed numbers and not one was answered. Both route into nested blast groups that ring for five seconds. It is the same failure described in section 5, arrived at from a different direction.

Anonymous callers are rejected account-wide

1,292 inbound legs over ten weeks, 0.7% of the total, from 123 distinct callers across 56 different numbers including the main line, were rejected because the caller withheld their number. That is a defensible anti-spam setting. It is worth being a decision rather than an inherited default, since some clients call from hospitals, shelters and switchboards that withhold by default.

54 staff have no direct number at all

All 32 Client Concierge extensions, all 14 Case Status and all 8 Decision Support share one of those three numbers and have no line of their own. For those teams a shared number is the right thing to show a client, because the client should reach the team rather than one person. It only needs to work.

Which teams this affects

Eight circular rollover pairs

Group A's only member is Group B, whose only member is Group A. A call entering either has nowhere to go. All are lead-vendor intake paths, all at zero calls, so either the vendors are gone or their calls fail silently and nobody would know.

(812) 232-9599 is explained. It is call group 6526 Decision Support Specialists, which contains 6528 Team Leads, which contains 6529 Supervisors. Three levels of nested blast groups, which is why 82 calls produced only zero-second Missed and Blocked legs. Separately, the Operator Queue is itself a member of 5041 PreHearing and 5042 Hearing CMs, so calls to those teams also ring the operator.

Thirty-two accounts can change the phone system

27 hold full ACCOUNT_ADMINISTRATOR and one holds ACCOUNT_SUPER_USER. Five are external to both firms. This is a list to prune at the Twilio cut rather than port.

7. Two businesses, one tenant

Vonage account 336580 is still named Fleschner Law and carries two separate businesses. Any move to Twilio is a split, not a lift and shift. The good news is that the roster already carries a Firm column, so the separation is mostly recorded. The bad news is what the two firms share.

The twelve people flagged "Both" carry 41% of every answered call

What each side takes, and what has to be decided

Two signals inside Vonage itself, both cleaner than email

Outbound caller ID. Thirteen extensions dial clients as (812) 232-2000, the Fleschner main number, while the rest of the firm shows 812-232-9595. That is the Fleschner identity as the client experiences it.

Vonage's own group tags. The user records already carry FSTN on 10 users and PI on 6. Two of the FSTN entries have no extension at all: Adam Waters, and Max Winchell at an outside firm's address, max@williamsinjurylaw.com.

The single decision that unblocks the split

Who answers Fleschner's 39 calls a day? At that volume the question is smaller than it sounds, and there are three real answers.

8. Reassembly

Every finding above points the same direction. The menu already has eight free slots, direct extension dialling is already enabled, and the destination dropdown already lists every queue and group in the account. The redesign is a configuration change. The order it is done in is what determines whether it works.

The order matters more than the design

1. Check ext 400000's General Settings, then stop the dead end. The three other receptionists we inspected (40000, 65181 and 400002) are each set to wait 2 seconds for input and then "play a message and disconnect". 400000 itself has not been inspected on that screen, so confirm it first. If it matches, change the action to "forward to extension 5000" and widen the input window to 5 seconds. 476 business-hours callers a fortnight reach that greeting and go no further, it is one dropdown, and it is safe no matter what else you decide.
2. Fix the destinations before pointing anything at them. Ring durations to 20 seconds on 6529 and 15 on 6524, untick "delete voicemail after sending email" everywhere, and resolve 5011 by deciding whether intake answers Vonage at all. Adding menu keys to five second groups just gives callers a faster route to the same mailbox.
3. Give every group a visible queue. This is the piece that does not exist today. A queue nobody can see cannot be managed, which is why 670 people gave up waiting last fortnight with no record that it happened.
4. Then rewrite the greeting and open keys 2 through 6. Only at this point does the operator step stop being load bearing, and only then should it be retired.
5. Change the outbound voicemail script. The 135 "returning our call" cases cannot be fixed by any menu, because the caller does not know who rang them. The message the firm leaves has to name the team and the key to press.

9. Still open

1. Call group and queue configuration. Not exposed on the API. Needs a portal export in the same way the receptionist list was exported, covering membership, ring duration and no-answer destination for every group.
2. Extension 9000. 127 legs off the Fleschner line, no owner recorded anywhere.
3. 812-232-9599. 82 calls producing zero-second Missed and Blocked results against groups 6526, 6528 and 6529. The failure mode is not understood.
4. Whether 812-231-1886 and 812-231-1881 are fax lines. Inferred from single leg, no user, long duration and the caller ID "MED RECORDS ONL". Not confirmed in the portal.
5. A scam impersonating the firm. One caller reported a number impersonating Newlin and harvesting personal information from people who ring it. That is in the transcripts as a real call and needs someone to own it today.

Method. Window 1 to 13 August 2026, thirteen consecutive complete days. Source is the Vonage CDR on the analytics droplet, joined per call using the shared id across legs rather than counted per leg. Inbound runs 2.89 legs per call, so any leg-level count of this system overstates it by roughly that factor. "Reached a person" means at least one leg answered by a named user; queues, groups and receptionists record no name and never count. Dialer bridge traffic and two device lines were excluded before any rate was computed. Transcript classification used a fixed taxonomy over 2,016 recordings with no classification failures; the "a menu could route it" column is a model judgment and the only soft figure on this page. Everything else is counted.