nbn Troubleshooter

Helping customers fix nbn issues themselves

Product Designer

Timeline 8 Weeks

nbn Troubleshooter

Helping customers fix nbn issues themselves

Product Designer

Timeline 8 Weeks

Context

Context

  • No self-serve troubleshooting option

  • Customers unable to self-diagnose nbn issues

  • 18,700 average support calls per month

  • Customers could resolve themselves

Constraints

Constraints

  • Prioritised by most common connection type

  • Self-serve without degrading support quality

  • Designed for low technical confidence

  • Cover the most common nbn fault types

  • Existing Belong app architecture

  • 8-week build timeline

Mapping fault types and diagnostic flows across connection issues

Mapping fault types and diagnostic flows across connection issues

Step-by-step troubleshooter designed for low technical confidence

Step-by-step troubleshooter designed for low technical confidence

Mobile experience customers resolving issues without calling support

Mobile experience customers resolving issues without calling support

Outcomes

Outcomes

  • 704 customers in the first 24 hours

  • 64 resolved issues without calling

  • Agents can see every step a customer took

  • Tool adopted without any marketing

  • 10% call drop within weeks - ongoing

Iterations

Iterations

  • Push notifications

  • Predictive fault detection

  • Expanded fault types

  • Agent dashboard integration

  • Mobile data widgets

Copyright Rodney Blackney All Rights Reserved

Copyright Rodney Blackney
All Rights Reserved