mere.dev / csm consulting

Your support pipeline is built to ignore people.

Most customer service systems are engineered to deflect — to close tickets, not solve problems. To make complaints disappear, not customers feel heard. I help companies rebuild their CSM pipeline from the ground up — turning a cost center into a genuine competitive advantage.

Let's Talk

Tickets designed to disappear, not to resolve.

Here's what a typical enterprise support queue looks like. Notice what's missing: the customer.

Support Queue — All Open
5 open live
#10280

Onboarding question — new enterprise client

Opened 6 weeks ago · Bounced between 3 teams · No owner

Abandoned
Last reply
42 days ago
#10341

Account migration failed

Opened 31 days ago · Auto-closed after 30 days · Customer furious

Re-opened
Last reply
31 days ago
#10388

Feature request: export to CSV

Opened 3 weeks ago · Marked "Under Review" · Customer not updated

Waiting
Last reply
21 days ago
#10401

Wrong charge on invoice

Opened 12 days ago · Escalated · Awaiting finance review

Waiting
Last reply
12 days ago
#10432

Login not working — urgent

Opened 6 days ago · Assigned to Tier 1 · No response

Open
Last reply
6 days ago
A ticket is a promise. Most pipelines are built to break it as quietly as possible.

What most pipelines do

  • Route to the wrong team, twice
  • Auto-close unresolved issues after N days
  • Measure success by tickets closed, not customers satisfied
  • Use AI to deflect, not to help
  • Leave customers in status limbo for weeks
  • Treat escalation as failure, not signal

What a good pipeline does

  • Route on intent, not keywords
  • Acknowledge every customer, every time
  • Measure happiness, not closure rate
  • Use AI to surface answers, not to stall
  • Proactively update customers before they ask
  • Treat escalation as the most valuable data you have

I didn't read about these tools. I built them.

At ServiceNow I built the Conversation Builder and NLU Engine — the AI chat and natural language infrastructure that enterprise CS pipelines actually run on. I've seen from the inside how these systems get designed, where they break down, and why most of them are built to serve the company, not the customer.

I've also secured AT&T as a customer by dispatching 50,000 field agents across 200,000 locations — which required a pipeline that couldn't afford to fail anyone. That kind of accountability changes how you think about support.

This work was featured in a national ServiceNow TV campaign with Idris Elba. Not because it was flashy — because it worked.

From audit to transformation.

Pipeline Audit

I map your current CSM workflow end-to-end — where tickets enter, where they stall, where customers fall through. You get a clear picture of what's broken and why, without jargon.

Customer Self-Direction

The best support interaction is one the customer resolves themselves — on their terms, at their pace. I design self-service tooling that gives customers real controls: account actions, status visibility, the ability to act without waiting. Customers are happier when they're steering, even when things go wrong. And your agents are freed up for the problems that actually need a human.

Routing & Triage Redesign

Most misdirected tickets aren't a people problem — they're a design problem. I rebuild routing around customer intent, not internal org charts.

AI Integration — Done Right

AI in CSM is almost always bolted on as a deflection layer. I integrate NLU and conversational AI to surface real answers, resolve common issues, and escalate intelligently — not to wear customers down until they give up.

Metrics That Matter

Tickets closed is a vanity metric. I help you define and instrument what actually matters: resolution time, customer sentiment, escalation signal, and repeat contact rate.

Team & Culture Alignment

The best pipeline redesign fails if the team still thinks their job is to close tickets. I work with your people — not just your tools — to shift the posture from deflection to engagement.

The same queue. A different intent.

Four principles that separate a CSM pipeline built to engage from one built to deflect. Annotated for the people in the back.

#10432 · Login not working

Account access — customer self-resolved

Resolved
↺ Reset password ⊕ Add MFA device ⊘ Revoke session ↗ Escalate to agent

One-time passwords — never touch a password reset again

Customers get a magic link or OTP sent directly to their email or phone. No password to forget, no reset flow to support, no ticket. They're in within seconds — on their own.

Last reply
18 min ago

#10401 · Billing dispute

Wrong charge on March invoice

Open
Customer This charge doesn't match my plan — I'm on the $49 tier.
Maya (Agent) Thanks — pulling your billing history now. Can see the discrepancy. Escalating to finance.
Finance Confirmed — credit of $22 issued. Visible on next statement.
Last reply
6 hrs ago

#10388 · Product question

How do I configure the stone mill cutting pattern?

Resolved
Open Visual Pattern Designer →

stones.mere.cloud · Interactive laser cut stone mill configurator

Last reply
2 days ago
real search — not 3 canned filters customer self direction every conversation, inline. no lost email chains real tools beat AI every time (click and try!)
Every ticket is a customer trying to stay. Treat it that way.

I'm just a mere dev. Hungry and humble.

If your CSM pipeline is built to ignore people — any size, any industry, anywhere — let's talk.

Get in Touch