Personalized customer service for ridehail vehicle passengers

1. A method of resolving service instances to riders participating in a ride-hail service provided by a fleet of autonomous vehicles (AVs), comprising:

navigating an AV to provide a trip to a passenger;

associating the passenger with a unique passenger identifier (UPID);

receiving passenger metadata for the passenger according to the UPID;

monitoring, by the AV while navigating, for a passenger service instance;

triggering, by one or more sensors on the AV, a data-driven event, wherein information relating to the data-driven event includes AV sensor data and a state of a user interface being displayed to the passenger within the AV;

triggering, by an AV controller, a passenger-initiated event based on a passenger-initiated button press within the AV;

determining, by the AV while navigating, an occurrence of the passenger service instance based on the triggering of the data-driven event and the passenger-initiated event;

establishing a connection between the AV and a service center;

identifying event data associated with other passenger service instances of the ride-hail service;

displaying, by the service center, contextual information regarding the passenger service instance to a service representative, the contextual information including the AV sensor data, a copy of the user interface being displayed to the passenger, and the event data associated with other passenger service instances; and

responding to the passenger service instance, comprising customizing the response to the passenger service instance according to the UPID, the passenger metadata, and the event data associated with other passenger service instances.

2. The method of claim 1 , wherein customizing the response comprises assigning the service representative to the passenger according to the UPID.

3. The method of claim 1 , wherein the passenger metadata comprises traceability data sufficient to trace the passenger to one or more AVs that the passenger has ridden in.

4. The method of claim 1 , further comprising:

aggregating and storing data associated with passenger service instances triggered by passenger-initiated button presses and data associated with passenger service instances triggered by sensor and state logs of AVs as the event data.

5. The method of claim 1 , further comprising:

storing data associating with passenger trips as the event data.

6. The method of claim 1 , wherein responding to the passenger service instance comprises:

determining the trip has been interrupted;

identifying, from passenger metadata, a further AV to complete the trip, wherein identifying comprises determining that the further AV belongs to a type of AV to which the passenger had responded positively based on the UPID, the passenger metadata, and the event data; and

routing the further AV to complete the trip.

7. The method of claim 1 , wherein:

the passenger service instance is initiated due to a lost item; and

customizing the response comprises identifying an AV the passenger was riding in and a seat in which the passenger occupied based on the UPID, the passenger metadata, and the event data.

8. A system for resolving service instances to riders participating in a ride-hail service provided by a fleet of autonomous vehicles (AVs), comprising:

an AV of the fleet of AVs, the AV comprising an onboard computer configured to:

navigate to provide a trip to a passenger,

monitor for a passenger service instance,

trigger a data-driven event, wherein information relating to the data-driven event includes AV sensor data and a state of a user interface being displayed to the passenger within the AV,

trigger a passenger-initiated event based on a passenger-initiated button press within the AV, and

determining an occurrence of the passenger service instance based on the triggering of the data-driven event and the passenger-initiated event; and

a central computer in communication with the fleet of AVs comprising:

at least one processor circuit;

a memory; and

instructions encoded within the memory to instruct the at least one processor circuit to:

associate the passenger with a unique passenger identifier (UPID),

receive passenger metadata for the passenger according to the UPID,

identify event data associated with other passenger service instances of the ride-hail service,

display contextual information regarding the passenger service instance to a service representative, the contextual information including the AV sensor data, a copy of the user interface being displayed to the passenger, and the event data associated with other passenger service instances, and

respond to the passenger service instance, comprising customizing the response to the passenger service instance according to the UPID, the passenger metadata, and the event data associated with other passenger service instances.

9. The computing system of claim 8 , wherein the instructions are further to instruct the at least one processor circuit to:

assign the service representative to the passenger according to the UPID.

10. The computing system of claim 8 , wherein the passenger metadata comprises traceability data sufficient to trace the passenger to one or more AVs that the passenger has ridden in.

11. The computing system of claim 8 , wherein the instructions are further to instruct the at least one processor circuit to:

aggregate and store data associated with passenger service instances triggered by passenger-initiated button presses and data associated with passenger service instances triggered by sensor and state logs of AVs as the event data.

12. The computing system of claim 8 , wherein the instructions are further to instruct the at least one processor circuit to:

store data associating with passenger trips as the event data.

13. The computing system of claim 8 , wherein responding to the passenger service instance comprises:

determining the trip has been interrupted;

identifying, from passenger metadata, a further AV to complete the trip, wherein identifying comprises determining that the further AV belongs to a type of AV to which the passenger had responded positively based on the UPID, the passenger metadata, and the event data; and

routing the further AV to complete the trip.

14. The computing system of claim 8 , wherein:

the passenger service instance is initiated due to a lost item; and

customizing the response comprises identifying an AV the passenger was riding in and a seat in which the passenger occupied based on the UPID, the passenger metadata, and the event data.

15. One or more tangible, non-transitory computer-readable storage media having stored thereon executable instructions to instruct a processor to:

navigate an autonomous vehicle (AV) to provide a trip to a passenger;

associate the passenger with a unique passenger identifier (UPID);

receive passenger metadata for the passenger according to the UPID;

monitor, by the AV while navigating, for a passenger service instance;

trigger, by one or more sensors on the AV, a data-driven event, wherein information relating to the data-driven event includes AV sensor data and a state of a user interface being displayed to the passenger within the AV;

trigger, by an AV controller, a passenger-initiated event based on a passenger-initiated button press within the AV;

determine, by the AV while navigating, an occurrence of the passenger service instance based on the triggering of the data-driven event and the passenger-initiated event;

establish a connection between the AV and a service center;

identify event data associated with other passenger service instances of the ride-hail service;

display, by the service center, contextual information regarding the passenger service instance to a service representative, the contextual information including the AV sensor data, a copy of the user interface being displayed to the passenger, and the event data associated with other passenger service instances;

respond to the passenger service instance, comprising customizing the response to the passenger service instance according to the UPID, the passenger metadata, and the event data associated with other passenger service instances.

16. The one or more tangible, non-transitory computer-readable storage media of claim 15 , wherein the executable instructions are to further instruct a processor to:

assign the service representative to the passenger according to the UPID.

17. The one or more tangible, non-transitory computer-readable storage media of claim 15 , wherein the executable instructions are to further instruct a processor to:

aggregate and store data associated with passenger service instances triggered by passenger-initiated button presses and data associated with passenger service instances triggered by sensor and state logs of AVs as the event data.

18. The one or more tangible, non-transitory computer-readable storage media of claim 15 , wherein the executable instructions are to further instruct a processor to:

store data associating with passenger trips as the event data.

19. The one or more tangible, non-transitory computer-readable storage media of claim 15 , wherein responding to the passenger service instance comprises:

determining the trip has been interrupted;

identifying, from passenger metadata, a further AV to complete the trip, wherein identifying comprises determining that the further AV belongs to a type of AV to which the passenger had responded positively based on the UPID, the passenger metadata, and the event data; and

routing the further AV to complete the trip.

20. The one or more tangible, non-transitory computer-readable storage media of claim 15 , wherein:

the passenger service instance is initiated due to a lost item; and

customizing the response comprises identifying an AV the passenger was riding in and a seat in which the passenger occupied based on the UPID, the passenger metadata, and the event data.