Known Once a Ticket Exists

The line between wanting and having

Everything in the first moment is true of a person. Everything here is true of a booking somebody else made.

That is the difference that decides whether an operator's answer means anything. Asked about a preferred Tuesday, an operator gives a reply it is entitled to withdraw. Asked about a fixed date, it can look at what it has committed and answer properly, including by declining.

Two hours, not one

The most common muddle in this moment is time. A ticket carries an hour, and a traveler has an hour in mind for the car, and those are different numbers arrived at differently.

The desk records both, separately, and lets the operator do the arithmetic between them. A single time field is how a car arrives an hour late while every piece of paper agrees with itself.

The entry that says no

One of the four exists mainly to refuse something. The flight number is collected and passed on, and nothing at this desk watches a flight. That refusal sits in the intake rather than in the small print because it is the thing a traveler is most likely to assume without asking.

The four

1. Known once a ticket existsThe calendar date, once something is bookedUntil a ticket exists the date is a preference. Once it exists the date is a fact, and only then can an operator say what it has open.
2. Known once a ticket existsWhether the run goes toward the field or awayThe same two addresses on the same day are two different jobs depending on which way the car is pointed, and they fail in different ways.
3. Known once a ticket existsThe hour the schedule saysThe hour printed on a ticket is a fact. The hour a car should arrive is a decision made from it, and the two are not the same number.
4. Known once a ticket existsThe flight number, and what it is not forThe number is written down and handed to the operator. Nothing on this desk watches it, and a delay does not move a booking by itself.