Newlin Reception Call Analysis

Reception has quietly become the firm's switchboard — and it is carrying a heavy, mixed load. Over one week it handled 1,235 inbound calls, and it handles them well: 79% were answered, only 3 rolled to voicemail. The problem is not that Reception drops calls. It is how much lands there, and why.

1,235

inbound calls in the week

79%

answered live (only 3 to voicemail)

45%

also tried another line first (overflow)

~1 in 5

are agencies & providers, not clients

1. It is the main line, not scattered numbers

Every one of the 1,235 calls came into just two reception extensions — 5114 (712 calls) and 5116 (523 calls). Callers are dialing the main number, not a specific person. So this is the "call the front desk" experience, and it is where a large share of the firm's inbound world converges.

2. Nearly half of it is overflow

558 of the 1,235 callers (45%) also tried a different, non-reception line the same week. That is the fingerprint of "I could not reach my person, so I called the main number."

This connects directly to what we found in the Hearing analysis: agents are buried in outbound work, so inbound rolls to voicemail; the client then calls the main line; Reception tries to transfer them, often back toward the very voicemail they were escaping. 203 people called Reception two or more times in the week — the sound of callers trying again and again to get through.

3. About a quarter is agencies and providers — not clients

Reception is also the first stop for the outside organizations that need to reach us. Of the answered, transcribed calls, roughly 1 in 5 was a third party (agency, provider, court, insurer), and these are the most time-sensitive:

Who is calling	Calls / week	Typical reason
SSA	133	Address verification, asking for the attorney's direct line for a hearing, Title 2 vs Title 16
Medical providers	83	Appointments, failed record faxes, where to send records
Other outside parties	75	General third-party inquiries
Courts / ODAR	10	Hearing offices calling on behalf of a judge about a claimant
Records / ROI	5	Records-request clerks
Insurers	4	Adjusters on client injury/auto cases

Real examples from the week (client identifiers removed):

SSA — A Social Security representative called to verify a client's mailing address after DDS received returned mail.

SSA — An SSA representative called to obtain the direct phone number for the attorney handling a 9:00 a.m. hearing.

Court / ODAR — A hearing-office clerk called on behalf of the judge regarding a claimant's case.

Medical provider — A medical records rep called because a fax of patient records failed, and confirmed an email address to send them instead.

Insurer — An adjuster called about a client's case and was put through a transfer.

4. What clients are calling about

On the client side, the mix is what you would expect for a front desk, and much of it is routable:

Category	Calls
General inbound client	739
Other	264
SSA	97
Medical provider	51
Client callback / status check	47
Records / ROI	12
New client intake	14

By party, 46% were agent-and-client, 21% were third parties, and the rest reached an IVR or voicemail. In practice Reception spends a large share of its day as a manual operator, relaying and transferring — for both overflow clients and urgent agency messages.

5. Why the experience is poor

Two forces converge on the front desk:

Overflow. When an agent is unreachable (on outbound, in a hearing), the client falls back to the main line. Reception then tries to hand them back — frequently to the same voicemail.
No smart routing for outside parties. Every SSA, court, provider, and insurer call hits Reception first and is relayed by hand, even when it is urgent (a judge's office, a same-day hearing).

The result is a switchboard doing a lot of manual triage, a client experience of "call, get transferred, reach voicemail, call again," and time-sensitive agency messages passing through a middleman.

6. The fix

This is exactly the problem an intelligent inbound layer solves:

An IVR tied to client records. Identify the caller by number and case stage, and route them to the right team or person directly — instead of parking everything on Reception.
A true inbound queue that hands a call to the next ready agent, so overflow stops dead-ending in voicemail and clients stop bouncing back to the main line.
Direct routing for agencies (SSA, courts, providers) so urgent messages reach the case owner without a manual relay.

Reception is not the bottleneck — it is the shock absorber for everything upstream that is not routing correctly. Fix the routing, and the front-desk load, the overflow, and the client experience all improve together.