Skip to main content
Logan Leiter
All work
PlatformsDigital TransformationCX Ops

Responsiveness after the system went live

Worked the post-go-live responsiveness problem — quotes, email, and order confirmations — and gave those intervals a target the operation can manage.

Organization
In-house, at a global industrial manufacturer
Role
Customer Experience Program Manager
Timeframe
2025 – Present
Tools
CRM / service cloud, Microsoft 365, Power BI

The situation

Quotes, first replies, and order confirmations have a visible target the team can manage.

What I found

Quotes, first replies, and order confirmations were slow enough that customers said so before the queue was visible.

What was in the way

A new system does not repair a fuzzy process. Requests still arrived in several inboxes. Aging was not in one place. The old path and the new path were both half-true.

What I did

Named the three intervals that matter, set a visible reply target, consolidated orphaned inboxes, and put backlog and quoting rate in front of the people who own the work.

Why it mattered

A platform decision is an operating decision. After go-live, quote turnaround, email replies, and order confirmations tell you whether the new system is actually how work moves.

Summary

Customer-facing work had grown up across tools and workarounds. After a core system went live, the practical test was responsiveness. The work was to name the intervals, set a visible reply target, and put aging where the people who own the queue can see it.

Context

Customer-related work had evolved across multiple tools. That showed up as inconsistent handling, inconsistent capture, and reporting that was difficult to standardize.

The platform work was treated as an operating-model decision: the system should support the business, not digitize the old workaround.

The problem

  • CX workflows were spread across systems and manual steps.
  • Process variation made both the experience and the report unreliable.
  • Teams needed one foundation for intake, follow-up, and visibility.
  • After go-live, quote turnaround, email replies, and order confirmations were the customer-facing proof.

The approach

  1. 01Brought CX and intake requirements into the platform conversation.
  2. 02Pushed workflow standardization and less unnecessary variation.
  3. 03Set a first-reply target, so “faster” had a definition.
  4. 04Put aging and quoting rate in an operating view, not a side spreadsheet.

What changed

Quote turnaround

Qualitative

Quote turnaround got a visible target and a view of aging.

First email reply

Qualitative

First replies moved to a managed interval instead of whenever someone noticed.

Reply target

Qualitative

I set a first-reply target with the team so "faster" had a definition.

What exists

Reply targets

Goal-setting for responsiveness, including a first-reply target.

Aging and quoting view

Backlog age, quoting rate, and request status in one place.

Inbox consolidation notes

Where requests entered, and the path they should use instead.

Where this sits

This work sits with CX audit and Go-live is when the customer starts measuring you.

Takeaways

  • Go-live is the start of the responsiveness problem, not the end of the project.
  • A reply target is useful because it's specific. It doesn't count as a result until I can show the interval.
  • When quoting improves, the next complaint will surface. That is a sign the system is working.
NextA front door, instead of a pile of inboxes

Bring a problem

Tell me where customers are waiting.

A short note is enough: what is breaking, what you have already tried, and what a good month would look like. If I am the wrong person, I will say so.