{VM}
Vikas Mayya
initializing...
0%

Building a Scalable Support Ticketing System

Gro Club's unique subscription model promised free service throughout the tenure—but growing customer base and unscalable processes caused friction. Customers repeatedly contacted support, had to re-explain issues, and eventually vented through negative reviews online. We needed a robust support system that brought together app, CRM, and real-time technician tracking.


Problem Statement

gro.club was a subscription-based bicycle service offering free servicing till subscription end — a strong USP. But the after-sales experience was broken:

  • Ops team couldn’t track thousands of service requests.

  • Customers repeated themselves to different agents.

  • No service history or ticket traceability.

  • The app was underutilized; awareness was low.

  • Frustrated users left negative reviews across platforms.


Discovery & Research

I sat with the ops & support teams, studied user complaints, CRM flow, and app analytics. Key observations:


Solution (3-Phase Rollout)

Phase 1 – Ticketing System MVP:

Result: Structured ticketing → Faster resolutions


Phase 2 – Communication touch points + Call Integration

Result: 50% fewer calls to support and Higher app engagement for ticketing




Phase 3 – Technician App (PWA)

Result: 3x faster service closure and Real-time updates improved customer trust


Business Impact


Metric Before After
Negative reviews/month 6–10 0–1
Support call volume High Reduced by 50%
Service completion speed Slow 3× faster
Customer app usage Low Significantly improved


Product Thinking Behind it

“Solving basic CX frictions with tech infra drives word of mouth, reduces churn, and sets a foundation for scalable ops.”

This system aligned tech with business goals:


What's Next?


Tools and Stack


Want to discuss how I can solve similar problems? Let’s connect!


Contact Me