Field research · Customer Operations · 2026
Searvis is independent research into a specific enterprise problem: the same customer operations failures repeat for years, everyone can see them, and nobody fixes them. I'm trying to understand why — by talking to the people who live it.
No product. No pitch. Research in progress.
The premise
Working hypothesis, not a finding. Discovery will confirm it or kill it.
Enterprises have spent a decade instrumenting customer operations. There are dashboards for containment, handle time, CSAT, transfer rates, deflection. The measurement problem is largely solved.
The explanation problem is not. A repeat-contact rate tells you the number went up. It doesn't tell you which broken policy, failed handoff, or misrouted bot caused it — what it costs, or who owns fixing it.
So recurring failures get discussed quarterly, assigned to nobody in particular, and survive. Not because people are careless, but because the failure has no owner and no price tag. Anything without those two things loses to whatever does.
If that's right, it's a real and expensive problem. If it's wrong, I want to find out now — before building anything.
Systems already tell you
Repeat contact rate rose 18% this quarter
Nobody can tell you
Which three issues drove it, and what they cost
Systems already tell you
Bot containment dropped in the billing intent
Nobody can tell you
Whether it's the bot, the policy, or the data behind it
Systems already tell you
Escalations cluster on Tuesdays in one queue
Nobody can tell you
Who owns the fix, or why last quarter's fix didn't hold
The left column is a solved problem. The right column is the research.
Open questions
The questions driving every conversation. They change as evidence comes in — that's the point.
01
Which recurring failures are painful enough to actually fund?
Plenty of things hurt. Very few get budget. The gap between those is the whole question.
02
Who actually owns a failure that spans four teams?
No owner, no buyer. And most real failures cross org lines by definition.
03
How do you find root cause today — honestly?
Not the process on the slide. The one that happens at 9pm during an incident.
04
What do your dashboards refuse to explain?
Everyone has the tools. I want to know where they stop being useful.
05
Where do AI agents create new operational failures?
Automation moves work. Sometimes it moves the breakage somewhere less visible.
06
What would you want to see in your own data tomorrow?
The honest test of whether any of this matters enough to pull for.
Who's asking
I've spent fifteen years selling into contact centers and customer operations — cloud communications at Twilio, CX testing and conversational AI assurance at Cyara, AI voice infrastructure at Telnyx, and automation at Kognitos.
Which means I've seen this from the wrong side of the table. I've sat in hundreds of enterprise evaluations watching teams buy tools to measure problems they already knew they had. The tooling kept improving. The same failures kept recurring.
I don't know yet whether that's a product. That's what the research is for.
Based in Atlanta.
Background at alrazibashir.com
Who I'm talking to
If a recurring failure lands on your desk and stays there, you're who I'm looking for. High-volume consumer service operations — where the same issue costs you a thousand times a month.
Insurance & payers
Claims, policy service, member services, appeals & grievances
Consumer banking
Servicing, disputes, fraud ops, digital support
Health systems
Patient access, revenue cycle, patient experience
Telecom & utilities
Billing, provisioning, field service coordination
Titles I'm reaching out to
What you get
What this isn't
The ask
I'm interviewing customer operations leaders through 2026. No product exists, so there's nothing to sell you. I'm trying to find out whether the problem I think is real actually is — and you'd know better than I would.
al@searvis.io · Atlanta, GA
