← All reports

🎧 Customer Support report

Mon 9/14/26 to Sun 9/20/26

Report generated: Mon 9/21/26 @ 11:43pm Central

Last sync: Mon 9/21/26 @ 6:04am Central, 8,719 tickets.

❀️ HEALTHπŸ” DIAGNOSIS🌟 PRAISE

❀️ HEALTH

Is the desk ok right now?

πŸ“Š Activity

DayMsgs in<1h1-2h2-4h4h+Waiting
Mon 9/142386210
Tue 9/1520150010
Wed 9/1633156110
Thu 9/1729108220
Fri 9/181980105
Sat 9/19000000
Sun 9/20000000

Business hours only. Rows do not sum to messages in: 32 more were closed without a reply, nearly all of them a client saying thank you. The ones that were not are under Bad closes.

🚨 Needs attention now

12 messages are waiting on a reply. Longest first.

WaitingCompanySubject

πŸ”‡ Bad closes

72 of 72 closed threads judged: 62 answered, 3 bad closes, 7 not a support request.

❌ We never replied (2)

22970gmail.com

An applicant could not open the verification link and asked for another way to submit; we never replied.

I have been unable to access the verification link provided in the email, including when copying and pasting the alternate link into my browser.
22732srascreening.com

Client reported that several applicants cannot upload documents from our link and asked us to look into it; an agent asked internally whether to answer and nobody ever did.

We have had several applicants call us stating that they are unable to upload documents when they click on the link that is sent requesting the documents. If you could please look into it

❌ We replied and it missed (1)

22873essentialscreens.com

Client asked a follow-up question after the cancellation reply and it was never answered before the ticket closed.

Are you not concurrently calling on these?

πŸ“ˆ Against your own baseline

This week4w baseline
Tickets in8379flat
Messages in124122flat
Closed7276flat
Still open11–
Median response44m41mflat
p90 response5.0h4.6hflat
Still waiting5–

Response times are per inbound message, not per ticket, and include messages still waiting at their elapsed-so-far duration. Dropping unanswered ones would mean ignoring a customer improved the percentile.
p90 is the number to watch: a fast median with a slow p90 is a desk that looks healthy and has a tail of people who were left.
Rows with – for a baseline are cohort-aged: this week's tickets are days old and earlier weeks' have had a month to close, so comparing them would read as worse every week no matter what.

⏱️ Response distribution

Wait
p5041mhalf were faster
p751.8h
p903.9h10% waited longer than this
p956.4h
p993.7d1% waited longer
max13.2d
AnsweredMessagesShare
< 1 business hour31159%
< 4 hours47590%
< 1 business day50596%
< 3 business days51999%
> 7 business days30.6%

525 inbound messages over the trailing 4 weeks. A single week is too few messages for a p99 to mean anything.

⚑ What changed

πŸ” DIAGNOSIS

Why, and who it is coming from.

⏳ Where the time goes

56.2d of business time across 83 tickets, 43% of it waiting on us.

Owed byHoursShare
Us24.3d43%
The client31.9d57%
Our time per ticket
p5059mhalf held us less
p909.0hthe tail that sets the week
max15.7h
Our timeTheirsCompanySubject

Derived from message timestamps, not from Freshdesk status. A span that starts with a customer message is ours until we reply; one that starts with our reply is theirs until they write back. Private notes move nothing. Business hours only, and the clock stops when a ticket closes. Tickets still open are counted to now, so their share can only grow.

🏒 Who

Ranked by change against each company's own 4-week baseline, so a client going from one ticket to six outranks a steady heavy user.

CompanyWeekBaselineChange
firstchoicebackground.com2714.8+83%
kennia@15
samanthad@6
courtney@6
veritablescreening.com30.8+300%
support@3
pinnacleprof.com20.0new
aking@1
sschilke@1
inquirehire.com20.0new
tanya@2
fisd.us20.0new
dbrowder@1
korth@1
datascreening.com20.0new
jgarcia@2
bc.edu20.0new
bcdining@1
hrsc@1
truviewbsi.com31.5+100%
jmorales@2
jtincher@1

🏷️ Tags applied

Computed from the store, not inferred.

πŸ’¬ Themes

Inferred: read from the ticket bodies, not computed.

The document upload link stopped working

Applicants could not open the link that asks them for documents. It surfaced Monday, went unanswered, and came back Thursday morning through three clients and one applicant before the fix went out.

The TWN detection closes document-collection orders on arrival

One SLA β€” Employment Signature 3-Day No-Email No-Calls w/ Equifax TWN β€” closes the order the second it detects The Work Number, with zero calls, zero emails and zero attempts to collect documents. Four tickets on Thursday alone, across two clients.

Verification data that turned out to be wrong

Dates we furnished were disputed or impossible, which is the category that becomes an FCRA reinvestigation rather than a support ticket.

Orders aged past SLA because a bad contact triggered nothing

An invalid email or a missing phone number neither closed the order nor raised it for research, so files sat. Eight tickets, six of them First Choice's Monday and Wednesday sweeps.

Work we finished that the client could not see

The most common reason to write in: the order is complete on our side and the client's platform shows nothing. Every one of these was answered by pasting the result into the ticket by hand.

Documents and reports missing from the finished file

Distinct from the sync gap: the work is visible, the artefact is not attached.

Applicant outreach that was supposed to be switched off

Clients who had configured us not to contact applicants, or had told us a verification was done, still saw emails go out.

Orders worked against the wrong target

Three separate ways an order went to the wrong place, all three ending in a billing credit.

The inbound AI agent ends calls with questions unasked

The verifier answers, the order completes, and two questions were never put to them β€” and the verifier is unreachable afterwards because the order is already closed.

Did the reference ever respond?

Ten tickets asking us to check for or forward a response the client was told had been given. Routine, and each one is a manual lookup.

Our own outbound verification mail landing in the support queue

Replies from schools and employers to verifications we sent, routed into Customer Support rather than to the order. A Freshdesk routing rule, not a support workload.

Contact information handed to us

Thirteen tickets that are one message in, one message out: a client sending a better address or number for an open order. All answered the same day.

Cancel this, we already have it
Questions about what we offer

Two inquiries that are business development rather than support, both handed to Erica.

🌟 PRAISE

Client praise, in their words.

No noteworthy praise this week.

Written by a Claude Code routine. Not for distribution outside Argus.