What can a travel manager see about employees' rides, and how?
A company account can have a ride feed: a read-only list of rides with the rider's first name and last initial, the area of pickup and drop-off, the status, the captain's first name, the vehicle and plate once assigned, and the car's location only while it is on its way. It is kept deliberately light on detail.
A travel manager answers for every employee on a trip, and wants to know three things without calling anyone: who is in a car now, where it is, and whether anything is wrong. The ride feed is Quo's answer to those, and this page says exactly what it shows and what it holds back.
What it shows: for each ride on the account, the booking code, the rider as first name and last initial, the status, the scheduled time, the area of the pickup and drop-off, the captain's first name, the vehicle and its plate, the expense code and cost center, and an alert state. The captain, plate and car location appear only once a captain is assigned, and the location only while the ride is on its way, rounded to about 100 metres.
What it holds back: street addresses and numbers are removed unless the account has asked in writing for full addresses, which staff turn on only for that reason. The feed covers rides from the last 12 hours that have not closed and all upcoming rides, up to 200. It is for rides billed to the account, not for an employee's personal ride.
How it is read: with a key issued once in the studio and sent as a bearer token. A new key revokes the old one. Requests are rate-limited, responses are not cached, and the feed works only while the account is active. A security team can also be sent events as they happen: a status change on a ride, and an alert raised by a rider or a captain, to a web address the account sets, signed so that the receiver can check it came from Quo.
What to rely on: treat the feed as the source of truth and the events as a prompt to look. Failed deliveries are retried and recorded, but a security process should not depend on one message arriving.
What the rider has: a private tracking link to share, and a one-tap alert to the concierge desk. When the ride is on your account the alert can also reach your named security contact by email. The business duty-of-care page covers the controls on the captain and the vehicle; this page covers the feed.
What it is not: it is not a replacement for a travel risk program, for the traveller's own judgement, or for a conversation. It will not show rides that other vendors are carrying. Pair it with a rule on who the first call goes to: the traveller, the desk, or the security contact.
