1. 1The challenge
  2. 2Discovery
  3. 3Journey map
  4. 4The big call
  5. 5The redesign
  6. 6Change management
  7. 7Impact
  8. 8Reflection
Service Design · Journey Mapping

Support that shows up first.

How I used data and journey mapping to move a 25-year-old software company from reactive to proactive support.

RoleLead UX Researcher · Service Designer
Duration2017 – 2018
ToolsPivot tables · Surveys · Office · Miro
85%
faster resolution: from 8 days to 1.2 days
100%
at-risk revenue protected
$180K
saved in the first 6 months
6.1→8.2
support satisfaction out of 10
01
The challenge

Twenty-five years of the same support model.

To a 25-year-old West African financial software company whose revenue depended on service contracts, stability looked like reliability. To customers, it looked like a company that would rather manage a complaint than prevent it.

Problem 1

Reactive by design

Built to respond after problems surfaced. Every customer interaction began with a failure.

Problem 2

No resolution standard

No SLAs or escalation paths, so resolution time varied wildly and customers couldn’t set expectations.

Problem 3

Invisible churn risk

Unhappy customers didn’t complain loudly. They quietly deprioritised renewals.

The real problem
The support model had scaled with the business in volume, but not in design. Nobody had gone back to ask whether it still fit.
02
Discovery

Not a sample. Every signal we had.

I started with data that already existed, then turned it into a business case leadership couldn’t ignore.

250+

Customers surveyed

A structured survey sent to the active customer base.

Years

Of support tickets

Pivot analysis across resolution time, issue type, segment and outcome.

$

Risk & impact

Sized the at-risk revenue pool in annual contract value. Not hypothetical.

⚠︎

System failure map

Pinpointed where the system broke, giving the redesign clear targets.

64%
The insight

Support decided renewals, not the product.

64% of customers said support responsiveness directly affected whether they’d renew.

23%
had already started looking at alternatives, because of support, not product quality
#1
driver of dissatisfaction was resolution time, above issue complexity or outcome
Step 1A resolvable issue…
Step 2…becomes a repeat contact…
Step 3…becomes a dissatisfied customer…
Step 4…becomes a churn risk.
03
Customer journey map

A lose-lose made visible.

Customers waited days for help while consultants spent 75% of their time on travel and low-value diagnostics instead of billable work. Flip between the two maps.

Reactive, travel-dependent, expensive

Problem → Contact → Schedule → Resolution → Follow up (often none)

~8 days to resolve

Remote-first and proactive

Triage and ownership at first contact, a defined resolution path with SLAs, and a post-resolution loop that catches repeats.

Self-serve → Remote → Prevent
04
The big call · your turn

Customers trusted in-person visits. How do you move them online?

The new model was remote-first, but this relationship was built on consultants showing up. Tap a card.

05
Service design recommendations

Redefining customer support.

Every stage of the journey shifted from waiting for a failure to getting ahead of one.

01
DetectIssue logged or flagged early
02
Self-serveGuided fixes in the knowledge base
03
RemoteChat or video, real-time help
04
ResolveClear owner and SLA
05
Follow upAutomated check-ins
06
PreventMonitor for repeats
↺ Learnings from every resolved case feed back into the knowledge base and monitoring
Layer 01

Self-service & knowledge base

Built around the most common issue types from the ticket analysis, so support capacity went to the issues that needed a person.

Layer 02 · Biggest change

Streamlined resolution

A defined escalation path, clear ownership at each stage, and SLAs customers could see and hold us to. This fixed repeat contact at the source.

Layer 03

Proactive prevention

Monitoring for the early signals most linked to churn, so we stepped in before a customer escalated or went quiet.

06
Change management

Six months. 250+ customers onboarded.

New processes weren’t enough. The relationship between consultants and customers had to change too.

  1. 1
    Piloted with 10 key accounts

    Weekly feedback sessions to refine the process and systems.

  2. 2
    Ran live onboarding webinars

    Walked customers through the portal and benefits, and answered concerns.

  3. 3
    Trained interns on the front line

    They took customer calls and logged issues for consultants to turn into FAQs.

  4. 4
    Made a visual “how to submit a ticket” guide

    So the new way was the easy way.

  5. 5
    Freed consultants for strategic work

    Upskilled interns handled phone and ticket intake, escalating only when needed.

45%
faster resolution in the pilot vs on-site, which earned the full launch
62%
of initial inquiries resolved without a site visit
20+
software training videos
100+
FAQs written in the first 3 months
07
Key outcomes

From firefighting to foresight.

Flip the switch to compare.

Average time to resolve
8 days
1.2 days
Support satisfaction
6.1/10
8.2/10
At-risk revenue
Invisible
100% kept
How issues got fixed
On-site
62% remote
Consultants felt
Stretched
Empowered
Grow
Complaints
Champions

Pilot customers became champions whose word of mouth brought more customers on board, and consultants finally had time for strategic projects and certification renewals.

08
Reflection

Processes change fast. Relationships take care.

The shift needed more than new processes. In an environment rooted in in-person trust, I trained consultants to act as change agents, helping customers see the long-term value of the new model. Empathy and data together turned a slow, costly system into a proactive one, and proved that customer experience insight drives organisational alignment.

John LarteySAP Project Manager · managed Veronica at Persol Systems
Recommendation

I managed Veronica on a number of projects at Persol Systems. She gets things done. She exhibits a high sense of empathy for her team members and stakeholders.

She is hardworking and very receptive to new ideas. Suggest a project, and she will come up with ideas to make it work.

You can trust her. You can literally take her word to the bank.

How did this land?

🤔Tell me more (opens LinkedIn in a new tab)

That’s a wrap. Let’s talk.

© 2025 Veronica Dogbegah · Product & Service Design Leader LinkedIn · Medium · YouTube · AI Pattern Library