What if I have a complaint or feedback?

Complaints and feedback both go to the same team. Tell us what happened, how it affected you, and what outcome you're looking for; we'll investigate and respond. For service-quality issues (rude agent, slow response, billing error), we'll resolve the specific problem and review what went wrong. For feature requests or content feedback (unclear lesson, broken link, suggested improvement), we route those to the relevant team and update you when changes are made. We track feedback in aggregate so common pain points get fixed faster.

The escalation path for complaints not resolved at the first level: ask to speak to a supervisor or to have your case reviewed by a manager. Some complaints are best handled by a supervisor who has authority to make exceptions; some are best handled by a manager who can authorize policy departures; some are best handled at our compliance level when they involve regulatory questions. The structural escalation exists for genuine reasons rather than as a delaying tactic. Drivers who feel their complaint was dismissed at the first level should specifically request escalation, which usually produces a different outcome.

The aggregate-feedback tracking is also part of how the platform improves over time. Individual complaints rarely lead to platform changes by themselves, but patterns across many complaints frequently do. A single confusing chapter mentioned by twenty drivers gets revised; a payment flow issue mentioned by fifty drivers gets refactored; a state-specific reporting issue mentioned by a hundred drivers gets a dedicated workflow. Drivers who provide feedback should know that their input is contributing to the longer-term quality of the platform even when their specific complaint can't be retroactively addressed. The feedback loop is part of what makes the service better year over year rather than static.