Operations Backlog - Master

Stack Ranked and Groomed Weekly

  1. Definitive resolution in using paper plates for new used vehicles on Uber [trying 1/3/24 with David G]
  2. Comms blast to current drivers to install their own toll tags
  3. Create process for ensuring new bookings are made aware of this requirement for renting through Zevo. Maybe there is something we can do to streamline this for them, without using tech?
  4. Comms blast updating drivers of financial responsibility for normal wear and tear of tires (big contention point)
  5. Receive 2 Texas registration stickers for unusable Kizoch cars at Marlowe [PENDING]
  6. William Town charges - remove $130 tolls? charges for previous drivers tolls actually
  7. Last 2 Kizoch tolls to be paid - 7SAYGDEE2NA004960 = Model Y plate RZK7526, Jessie is likely the renter for this car and responsible for $105.22 in tolls. 5YJ3E1EA2PF560488 = M3 , Jorge responsible for $146 in tolls (refund Nathan Stang)
  8. Aliex reg sticker pickup
  9. Ryan R repair pickup (7038) from Tesla [DONE].
  10. Run through payment processing/monitoring Ashley Woodcock (Unlicensed) Diego Netto
    1. We need a Metabase dashboard with actionable insights that answers who is behind on payments.
    2. Use (a) to decide which current drivers we want to fire as a customer - we don’t have the luxury or bandwidth to deal with our problem children right now.
  11. I want to make dealing with tolls a non-goal if possible. We don’t have the bandwidth to deal with this right now.
  12. We need a Metabase dashboard that reports on utilization with beginning of time being the start of the first booking and the end of time being right now.
  13. For problematic users that are a week or more behind on paying their current balance, we need an automated system that informs them they are late and communicates the implications:
    1. One week grace period to settle balance, else vehicle needs to be returned within 48 hours
    2. If payment fails and vehicle not returned, communicate that the car will be reported stolen to local authorities (can we automate this via SMS and API?
  14. Classify users based on demographics, Zevo account standing, and explicitly tag their account with identifier for which bucket they fall within in order to programmatically switch on customized business logic:
    1. Are they renting a higher end vehicle and is their account in good standing?
    2. Are their charges constantly failing and are they being difficult in supporting (fire them).
  15. We need to clearly delineate between base fare, supercharging, and toll costs.
  16. We need to clean up and split off #stream-payments in order to reduce noise and make them more actionable. Success isn’t interesting, failures and action to take with link will make for more useful alerts.
  17. Create process for submitting and charging tolls Ashley Woodcock (Unlicensed)
  18. Managing hosts and setting expectations Diego Netto
  19. Driver qualification process https://zevo.atlassian.net/wiki/x/AQCIAg
  20. Updated TOS & signature page Ashley Woodcock (Unlicensed)
  21. Off hours support schedule Ashley Woodcock (Unlicensed) Diego Netto
  22. Define repairs and maintenance expectations Ashley Woodcock (Unlicensed)
  23. Access to all tools/subscriptions Diego Netto Ashley Woodcock (Unlicensed)

☐

☐

☐

☐

☐

☐