Imagine a customer is actually still winnable: the switch is not yet final, the offer is relevant, and yet there is no response. No click, no callback, no completion. Not because the winback approach is poor, but because the case never reaches the customer.

That is precisely why effective customer winback does not begin with the offer, but with the operational question: does the case reach the customer in time and in a form they accept?

This Is Where Winback Is Decided in Practice: Delivery, reachability and trust are the upstream bottlenecks. In this article, we show how utilities can set up a cross-channel delivery mix and clear fallback rules so that customers enter an end-to-end workflow directly and cases do not quietly 'die'.

This Is What the Optimal Winback Journey Looks Like for the Customer: Cancellation → trigger starts the case in Paperfly → personalised self-service link by email or SMS → customer clicks, chooses an option and confirms within the same workflow → standard case runs automatically, while exception cases are managed as tasks with deadlines. The business department defines the offer and segments, the CRM provides triggers and contact data, and outbound teams handle exception cases.

Series: Winback as a Workflow for Utilities

What to Expect in This Article:

Why Delivery and Reachability Are the Bottleneck in Winback

The likelihood of success in customer winback workflows is not determined only by the offer, but one step earlier: does the message arrive at all, and is it perceived as legitimate? Many winback cases fail because the customer is never operationally guided towards a decision.

Traditional Channels and Common Pitfalls in Winback

  • Letters / Postcards: Traditional letters are often used as the first channel. This frequently creates media breaks, long lead times and a lack of feedback.
  • Email: Some customers who cancel respond reliably to email, while others rarely read emails or distrust senders. Winback therefore needs a cross-channel delivery strategy with a standard channel, reminders and defined fallbacks.
  • SMS: can be an effective reach channel, but only with trust by design, including a clear sender, a short context statement explaining why the customer is receiving the message, and a clear call to action. Otherwise, the risk of drop-off and distrust increases.

Channel Mix at Utilities: Email, SMS, Letter and the Role of Each Channel

Utility winback succeeds or fails on a deliberately managed channel mix: not 'more channels', but clear usage logic for each segment. The channel is only the transport layer; completion happens within the same digital workflow.

Usage Logic by Channel

  • Email: Standard Channel (Cost-Efficient), for the broad customer base; with Paperfly, a personalised workflow link leads directly to the choice between accepting or selecting an alternative.
  • SMS: Reminder / Accelerator for time-critical prompts, such as 'still open' or 'deadline approaching'. Effective only with clear trust signals, including an identifiable sender and brief context. For utilities operating in Germany, promotional SMS must also comply with the applicable consent and direct marketing requirements. In winback, SMS can be particularly useful where email gets lost in high message volumes, provided the contact is legally permitted.
  • Outbound: High-Value Fallback, when there is no response despite successful delivery or when the customer requests a callback. For utilities operating in Germany, outbound calls for promotional purposes should only be used where legally permitted and where the required customer consent or other applicable legal basis is in place. The call briefly clarifies the reason, after which Paperfly sends the personalised workflow as a self-service link so that completion does not remain stuck in the phone conversation.
  • Letter with QR Code: Reachability Fallback, when reliable digital contact data is unavailable or digital reachability is limited. With Paperfly, the letter is simply the transport medium, while a QR code leads into the same digital flow without media breaks, with brief instructions to scan the QR code, review the offer and confirm the decision.

Such a channel mix can only be operated reliably when delivery is modelled not as a series of campaigns, but as a case with rules, statuses and fallbacks. This is exactly where Paperfly comes in.

How Paperfly Secures Delivery as a Process Across All Channels

Paperfly turns winback into a controllable case with a personalised workflow into which all delivery routes converge. This reduces 'silent cases' because every contact attempt either leads to an interaction or transitions cleanly into a fallback or task.

Paperfly Is Not a CRM or Campaign Tool, but a Modern Web Application, that maps your entire case and delivery logic in a single solution. It controls when, how and through which channel a customer is guided into a binding decision journey.

Paperfly connects every step of the business process and transforms it into fully digital, automated customer winback workflows.

All Channels in One Flow: Service Orchestrated Through Paperfly

  • Targeted Multi-Channel Delivery: Each customer who cancels is contacted individually through the appropriate channel, such as email, SMS or, where appropriate, letter with QR code. Paperfly controls channel-specific delivery for each recipient so that every contact attempt leads directly into the self-service workflow.
  • One Flow Instead of Channel Breaks: Whether via email, SMS, outbound confirmation or a QR code on a letter, completion happens within the same self-service case.
  • 'Silent Cases' Become Visible: Undeliverable cases, no-response cases and follow-up questions are not left unresolved, but routed as tasks with deadlines.
  • QR Letters as a Fallback: a workflow can be made accessible through a QR code on printed materials. Dispatch is handled through Paperfly and a connected print service provider. No forms to fill in, nothing to send back and no login required: simply scan, review the bonus and confirm the decision.

Example Wording for Letters:

  • 'Would you like to see what offer we can currently make you? Simply scan the QR code.'
  • 'Your cancellation case is still open. Review your personal offer now via QR code.'
  • 'Have you cancelled? See which alternative we can offer you here.'
  • 'Your personal bonus is ready. View the details via QR code.'

With Paperfly, email, SMS and letters are only transport media. The decision is always made within the same digital workflow.

Trust by Design: How to Make Messages Feel Legitimate

In utility winback, trust is not a soft branding issue but a conversion and service factor. The problem is that consumers are regularly confronted with calls, SMS messages and links in the market.

Customer Expectations: If the winback message cannot be clearly attributed to the utility, the likelihood of it being ignored, abandoned or triggering follow-up questions increases. Trust by design therefore means making legitimacy visible before the customer enters the workflow.

6 Trust Signals That Have an Immediate Impact in Winback

  1. Consistent sender identity, with no 'no-reply' addresses and clear recognition
  2. Direct, personalised customer address
  3. A context sentence in the first line: 'Why are you receiving this message?'
  4. Make alternative response channels visible, for example a callback option
  5. Clear decision framework: one call to action plus one alternative
  6. 'Do not contact' opt-out as a process rule so that no further unwanted contact attempts are triggered. For utilities operating in Germany, this should also ensure that objections to direct marketing and withdrawals of consent are reflected immediately in the workflow logic.

Routing Cases Cleanly: Standard vs. Exception Cases

In winback, the standard case is clear: the customer can be reached, clicks and digitally confirms the request within the workflow. Anything that interrupts this chain, such as missing contact data or a callback request, is not an edge case but an operationally manageable exception case.

The Mistake in Many Projects: Exception cases are not modelled as separate paths, so they remain unresolved or create unplanned back-office workload.

Exception Case Triggers

  • Missing Reachability: no mobile number or undeliverable email → 'Check Data' task
  • Conflict in the Case: → clarification task
  • Callback Request / 'Please Call Me': outbound task instead of further reminders

What Matters Is the System Logic: Exception cases are not 'notes', but tasks with deadlines and escalation rules. This keeps the case controllable and prevents it from disappearing in an inbox.

Once delivery, trust and routing work together, success or drop-off is no longer determined by the channel, but by the next system-driven action.

Further Reading (Strategy): Value-First Winback at Utilities: Offer Logic, Timing and Decision Design

3 Rules to Prevent Winback Attempts from Quietly Dying

To prevent customer winback from fizzling out within the channel, every case needs a clear next action, either automated or handled as a task. This also requires a stop rule: if a contact is undeliverable, suppressed through an opt-out or can no longer be contacted for direct marketing purposes, the process does not keep trying, but automatically switches to an appropriate fallback. For utilities operating in Germany, the workflow should therefore take the applicable consent, objection and direct marketing rules into account before triggering further email, SMS or outbound contact.

Three Operational Decision Rules That Keep Every Winback Case Moving

  1. Undeliverable → Task Instead of Repeating
    If the email is undeliverable or contact details are missing, an automatic task is created to check or update the contact data. Alternatively, use the letter fallback.
  2. No Response → One Reminder, Then a Decision
    If the winback message has been delivered but there is no interaction within the defined time window, send one reminder. For high-value customers, for example business customers with high consumption and additional products, start an outbound task; for low-value customers, close the case.
  3. Distrust → Trust Path with a Deadline
    If the customer has doubts, such as 'Is this genuine?', or requests a callback, route the exception case as a task into a trust queue. The goal is not a discussion, but a quick return to the same workflow.

Typical Anti-Pattern in Utility Winback: Another reminder is sent through the same channel even though the contact is undeliverable or trust is lacking. Cause: no stop or fallback rules and no exception-case queues. Result: Reputation suffers and back-office workload increases.

Pilot Blueprint: Start with Two Channels and Scale from There

Start with two simple delivery paths that both lead into the same workflow: email as the standard channel plus SMS as a reminder. Scale only once the foundation is running reliably. For hard-to-reach cases, a letter with a QR code complements the delivery strategy.

Pilot (Initial Delivery Paths):

  • Email: standard for reachable customers who have cancelled → personalised link → workflow
  • SMS: reminder for no-response cases → personalised link → same workflow

Scaling (Additional Delivery Paths):

  • Outbound: high-value customer or callback request → conversation → open the customer-specific workflow link together
  • Letter: no current digital contact data or digital channels are ineffective → QR code → workflow start

6 KPIs That Make the Pilot Measurable

KPI Definition Why It Matters in One-Flow Winback Where to Measure / Where to Intervene in the Workflow
Reachability Rate Share of cases with a usable contact channel Shows how large the truly reachable customer population is Segmentation and data status; if missing → 'Check Data' task
Delivery Rate Delivered / sent (by channel) No entry into self-service without successful delivery Channel rules (see above)
Bounce / Undeliverable Rate Share of undeliverable emails (total) Early warning signal: cases quietly die / reputation suffers Undeliverable → automatic task and stop further attempts
No-Response Rate Delivered, but no interaction within the time window Dividing line between 'delivered' and 'effective' Reminder rule; then high-value fallback or close
Fallback Rate Share of cases that switch to outbound Measures exception-case load and process robustness Routing; if high → refine rules and trust design
Time-to-Contact Cancellation trigger → first successful interaction Determines whether winback happens within the relevant time window Deadlines; escalation in case of delay

These KPIs Are Leading Indicators: They explain why return rate and Time-to-Reactivation rise or fall during the pilot. Fine-tuning only becomes worthwhile once reachability is stable.

Mini How-To: Set Up the Pilot in 5 Steps

  1. Define the Population: Customers who cancelled within the last X days.
  2. Check Reachability: Record email, mobile number and opt-out status for each case as data fields within the process.
  3. Activate Channel Rules: Email standard → SMS reminder → outbound / QR code as fallback according to rules.
  4. Set Stop Rules: Opt-out or hard bounce → no repeated attempts, immediate fallback or task.
  5. Build Exception-Case Queues: Data validation, trust / service and outbound.

Time and Competitive Pressure in Winback

Speed determines success: when a customer cancels, the next provider is already in the picture. The response time of campaigns, call centres or the back office therefore becomes a critical factor.

Paperfly Addresses This Bottleneck Systematically: Delivery, reminders and fallbacks run automatically in real time, controlled by rules and statuses within the workflow. This avoids delays and enables every interaction to happen at the right time.

Why Traditional Campaigns Are Often Too Slow:

Dispatch vs. Response Time: Messages are sent in batches, and feedback can only be evaluated with a delay.
Manual Processing: Call centres or back-office teams only review responses or callback requests later. This creates significant delays.
Repeated Use of the Same Channel: Repeated calls or emails through the same contact channel create disruption and reduce acceptance.
No Prioritisation: High-value customers do not automatically receive priority treatment, while low-value contacts consume resources.

How Paperfly Optimises Timing:

Real-Time Delivery: The 'cancellation' trigger starts the workflow immediately, at the desired time, including weekends or public holidays. The process runs automatically without manual intervention.
Staggered Channels: Email, SMS, QR-code letters and outbound contacts follow clear rules, avoiding unnecessary repetition.
Automatic Prioritisation: High-value customers immediately receive relevant fallbacks, while low-value contacts are handled efficiently.
Deadline-Driven Tasks: Nothing is left unresolved because exception cases are immediately created as tasks with escalation rules.

Campaign vs. Paperfly: Delivery as a Workflow Instead of a One-Off Action

Many utilities still treat winback like a traditional campaign: send a message, hope the customer responds, perhaps send one more reminder. In practice, this approach is too rigid.

Paperfly Takes a Different Approach: winback is implemented as a continuous, controllable workflow. Every contact attempt, whether by email, SMS, QR-code letter or outbound call, leads directly into the same process: started automatically in real time, end-to-end digital and managed within one flow.

Before: launch a campaign and hope. Today: Paperfly controls every step in real time, from delivery to completion.

Conclusion: Reachability Before Conversion

Winback is not decided by the offer, but by delivery and trust. If the customer never receives the workflow or does not trust it, nothing happens, regardless of how good the offer is. That is why you need a rule-based channel mix. The goal: one flow, clear next steps and measurable reachability.

Paperfly Implements This as a Workflow: a case rather than a campaign, with statuses, rules, tasks and deadlines, so that standard cases run through automatically while exception cases remain controllable.

Practical Questions (FAQ): How to Keep Winback Deliverable

Why Do Winback Journeys Fail More Often Because of Reachability Than Because of the Offer?

The workflow can be perfect, but if the offer is not delivered, the customer overlooks the message or does not perceive it as legitimate, the offer is never even reviewed.

How Does a Utility Choose Between Email, SMS, Outbound and Letter/QR?

Use a simple decision tree based on reachability, such as a valid email address or mobile number, timing since cancellation and trust risk. Email can be the standard channel; SMS and outbound can serve as additional or fallback channels; letter or QR code can be used when digital contact data is unavailable. For utilities operating in Germany, the selected contact channel must also comply with the applicable consent and direct marketing requirements, so the workflow should verify whether the respective contact is legally permitted before delivery is triggered.

How Can Winback Messages Appear Legitimate in the Energy Sector?

Use clear authenticity signals: an identifiable sender, a short context sentence explaining why the customer is receiving the message, one or two clear calls to action and an alternative response channel such as a callback. Opt-out or 'do not contact' must be implemented as a technical process rule. For utilities operating in Germany, the workflow should also ensure that customer objections and withdrawals of consent are applied before any further direct marketing contact is initiated.

Back to the Series: Customer Winback at Utilities: Winback as an Executable Workflow (Overview)

Mini Glossary (Terms from Winback Projects)

Reachability
Whether a customer can actually be reached: valid contact data, an authorised channel with no opt-out, and technical deliverability. Reachability is the fundamental metric before any conversion.

Delivery Rate
Share of messages that are technically delivered by channel. Without delivery, there is no entry into self-service.

Emails: Hard Bounce / Soft Bounce
Hard bounce = permanently undeliverable, for example because the address does not exist. Soft bounce = temporarily undeliverable, for example because the mailbox is full or there is a server issue. Each requires different fallback rules.

No-Response
Delivered, but with no response within the defined time window, for example no click or selection in the flow. No-response triggers a reminder or fallback.

Value Segment (High-Value / Low)
Segmentation by economic relevance, for example customer lifetime value, margin, consumption or product mix. This determines whether a case receives an outbound fallback or is closed after a reminder.

Outbound
Telephone fallback contact in winback used to clarify reasons and guide the customer back into the digital self-service flow in a controlled manner.