Customer Flags

Concept

Customer flags are an extension of the Customer entity, storing additional information about a Customer. This information can be about a Customer’s permissions, preferences, or other relevant information. Flags are binary, meaning they are either set or not set.

Information stored in Customer flags is not mandatory for the operation of a Ridepooling Service but can be used to fulfill specific legal requirements, business rules, or to extend the Ridepooling Service.

These Customer flags are not part of the Customer entity itself because they are specific to an individual Integrator, a Service Area or use case. Most Integrators will only need access to a subset of the available Customer flags.

Note

Customer flags are predefined and are not standardized globally. To find out which Customer flags are available to you, please reach out to your Service Configuration Manager.

Example Use Cases: Closed-User Group Service

Note

This use case is exemplary only.

In case an Integrator offers both human-driven and Autonomous Vehicles, and the usage of Autonomous Vehicles is restricted to specific Customers, a Customer flag may be added to a Customer to indicate that the Customer is allowed to order an Autonomous Trip.