MyBell Bill cover
Role Senior Product Designer (end-to-end)
Country Canada
Industry Telecommunications
Website Bell
AI-Powered UX Research User Journey Mapping AI-Enhanced Design Interactive Prototyping Data-Driven Strategy Cross-Functional Leadership Design System
OVERVIEW

Improving billing transparency and trust through clearer, task-aligned interactions

Bell is one of Canada’s largest telecommunications providers, serving millions of customers across mobile, internet, TV, and home phone services. Despite its scale, Bell’s digital self-serve experience had fallen behind modern user expectations, especially within billing, one of the most critical and frequently used touchpoints.

I led the UX direction for optimizing billing and invoice-related experiences within the MyBell Mobile ecosystem. The initiative focused on reducing confusion around charges, increasing customer confidence in bill accuracy, and improving callable self-service pathways through simpler, more predictable interactions.

This initiative required balancing regulatory requirements, complex billing models, and diverse user expectations across high-volume customer segments.

Context

A fragmented billing experience

The billing experience in MyBell Mobile serves tens of thousands of customers per month and directly affects satisfaction, churn risk, and support costs. Billing misunderstandings are one of the leading drivers of support calls within the Bell ecosystem.

Users engage with billing information across multiple contexts (monthly summary, historical invoices, charge details), often without clear mental models of what each line item represents.

The Challenge

Unifying Bell's billing experience into one bill

Customer frustrations:

Customers only had a static PDF invoice in the app and frequently reported:

  • Confusion about what certain charges meant
  • Difficulty reconciling monthly totals with itemized charges
  • Uncertainty about where to find help for unfamiliar or disputed items

  • Compounding this, billing logic and regulatory language introduced complexity that users did not inherently understand.

    The core problem was: How do we design a billing experience that reduces ambiguity and builds trust without oversimplifying legally required content?

The business problems:

  • Support centers were overwhelmed with 120k calls/month
  • $10.8M annual in support cost
My Role

Leading unified billing experience design

I owned the end-to-end experience and more specifically:

  • Problem framing and user journey mapping
  • Cross-functional alignment with Product, CS, and Legal
  • Design of UX flows and interaction models
  • Validation of language, layout, and clarity patterns across devices

I also worked closely with Analytics to identify patterns in confusion signals and prioritized areas with the highest support cost impact.

Business Goals & CONSTRAINTS

Reducing support costs and improving self-service adoption

Bell's leadership recognized that PDF-only billing created significant operational overhead and user frustration. The unified billing initiative aimed to transform billing from a support driver into a self-service success. Key business objectives included:

Goals

  • Reduce the $10.8M annual support cost by enabling self-service billing understanding
  • Decrease inbound support volume from 120k calls/month related to billing questions
  • Increase self-serve confidence and task completion
  • Improve mobile billing accessibility for all users


  • Constraints

    • Legal/regulatory copy requirements
    • Existing billing structure and data limitations
    • Multilingual support requirements
    • Tight delivery timeline for quarterly release

    • Early alignment was critical to avoid rework due to compliance constraints.

Competitive LANDSCAPE

Learning from interactive billing experiences

Competitor telecom billing experiences generally fall into two camps:

  • Feature-rich but highly complex
  • Minimal detail and high abandonment
  • This is when I saw an opportunity to position MyBell Mobile as the most transparent and trustworthy billing experience among Canadian carriers by marrying clarity with accountability.

    User research

    Billing confusion drives support calls

    Research and support data revealed:

    • Users couldn't understand why bill amounts changed between months
    • PDF invoices were difficult to read and navigate on mobile devices
    • High support volume was concentrated around three patterns of confusion: ambiguous fees, promotional adjustments, prorated charges.
    • Accessibility barriers prevented users with disabilities from understanding their bills

    These insights shaped our approach: creating an interactive, accessible, and transparent unified billing experience that enables self-service understanding.

    The solution

    A startegic, interactive billing experience that empowers customers to self-serve

    Rather than redesign the billing engine, I focused on:

    Structured language patterns: Standardizing how charge categories are described

    Progressive detail disclosure: High-level summaries with optional deep dives

    Predictable navigation anchors: For recurring invoice elements across screens.

    Interactive Charge Breakdown
    Interactive Charge Breakdown

    Replace static PDFs with expandable, drill-down charge details. Users can tap any charge to see explanations, dates, and context, making it easy to understand what each line item represents and why it appeared on their bill.

    Period Comparison
    Period Comparison

    Enable users to compare current and previous bills side-by-side. Highlight changes in charges, services, and usage, helping users understand why their bill amount changed and identify trends over time.

    Mobile-First Design
    Dynamic Billing Summary

    Provide users with a real-time view of their total charges as they make plan, feature, or usage changes during the billing cycle. The dynamic summary updates automatically, showing how modifications impact the next invoice, increasing transparency and reducing billing confusion.

    Accessibility & Integration
    Service-Level Breakdown

    Offer a detailed view of charges per service; mobility, internet, TV, and home phone, including subtotals, discounts, and promotional adjustments. This granular breakdown helps users understand exactly what they’re paying for, compare across services, and identify changes over time.

    Design of the services details breakdowns for each service offering.
    Design of the summary of changes, in real time.
    Design of the bill history and comparisons.
    Unified Bill Architecture

    To extend the value of unified billing beyond static viewing, we designed a comprehensive bill management system that consolidates multiple services (mobile, internet, TV, home phone) into a single, interactive bill view. The unified architecture allows users to see all charges across services in one place, compare usage patterns, and understand their complete billing relationship with Bell.

    The unified bill introduced intelligent charge categorization, usage insights, and predictive billing estimates—helping users anticipate future charges and identify opportunities to save. By combining transparency, interactivity, and accessibility, the unified billing experience transformed billing from a source of confusion into a tool for financial understanding and control.

    Design decisions & tradeoffs

    Balancing clarity, control, and transparency

    What we intentionally deprioritized

    We did not introduce a fully interactive billing explainer or embedded chatbot in the first release. While these could support contextual help, they required significant backend data normalization, which was outside scope for the quarter.

    Trade-off: Immediate contextual assistance vs predictable roadmap delivery
    Outcome: Preserved release velocity and prevented dependency risk on backend changes.

    Where I pushed back

    Some stakeholder groups requested inline promotional detail expansion on the main invoice view. I resisted this because it increased cognitive load and diluted the primary charge hierarchy.

    Trade-off: Comprehensive detail exposure vs clarity and scanability
    Outcome: Cleaner core summary reached wider adoption in testing.



    How we reduced delivery risk

    We aligned UX language patterns with Legal and Regulatory frameworks upfront, so copy did not require rework during QA. This protected delivery timelines and reduced last-minute iterations.

    Trade-off: Generic language vs maximally detailed descriptions
    Outcome: Compliance confidence with minimal overhead



    The decision with the largest downstream impact

    We standardized charge category labels and progression patterns across screens. This decision reduced ambiguity, created reusable UX patterns, and supported future expansion of dynamic billing insights.

    Trade-off: Limited customization vs operational consistency
    Impact: Higher predictability in customer interpretation across invoice types

    Business Outcomes

    Clearer billing, lower support cost

    The unified billing initiative shifted billing from a high-volume support driver to a scalable self-serve experience grounded in clarity and structured transparency.

    Measured impact (first 6–9 months post-launch):

    • Reduced billing-related support calls by 28–35%, lowering monthly call volume from 120k to 85k.
    • Contributed to an estimated $7M annual support cost reduction, driven by decreased call handling and improved self-serve adoption.
    • 92% of users reported understanding their bill without calling support.
    • 48pt improvement in user-reported billing clarity and satisfaction scores.
    • Achieved 100% WCAG accessibility compliance, expanding usability for customers with assistive needs.
    Learnings

    Key takeaways

    1. Transparency Reduces Support Volume

    Most billing calls were driven by confusion, not errors. By making charges scannable, comparable, and drillable, we reduced the need for support intervention. Clarity, not correction, was the lever.


    2. Mobile-First Means Native Interaction, Not Responsive PDFs

    PDF invoices failed on mobile because they weren’t built for touch or progressive disclosure. Replacing static layouts with native mobile patterns increased engagement and improved comprehension. Mobile-first is structural, not cosmetic.


    3. Accessibility Drives Business Impact

    Accessibility was not just compliance. Designing for screen readers, semantic structure, and keyboard navigation enabled independent self-serve for users who previously had no alternative. Accessibility directly reduced support reliance and expanded adoption.












    Scroll