The Appointment That Wasn’t Really an Appointment

Some conversations are not really conversations.

They are collisions between two completely different understandings of reality.

In August 2010, I wrote down one of those collisions.

It involved a car service appointment.

The sequence was simple.

On Tuesday, I went to the service center.

They gave me an appointment for Friday.

So on Friday, I took the car there.

So far, everything followed the normal logic of the word “appointment.”

You agree on a time.

Then you show up at that time.

That is usually the point.

I arrived.

They welcomed me.

I reminded them why I was there.

Then came the answer:

“Sir, today is Friday. Tomorrow is Saturday. We can’t finish it today. Best come on Monday. There’s no point leaving the car here for nothing.”

There are moments when language briefly stops functioning.

This was one.

The problem was not that they could not finish the car that day.

That happens.

Schedules slip.

Work takes longer than expected.

Parts do not arrive.

Someone gets sick.

A previous job turns out to be more difficult.

Life interferes with planning.

All understandable.

The problem was the way the situation was presented as though Friday had arrived unexpectedly.

Today is Friday.

Yes.

That was the date of the appointment.

Tomorrow is Saturday.

Also true.

This information had been available on Tuesday.

The calendar had not suffered a surprise update.

I said what any mildly functioning customer would say:

“But you gave me an appointment for today. You could have called and told me not to come.”

The answer was:

“Hayırlısı.”

Roughly:

“Let’s hope for the best.”

That is a very powerful phrase in Turkish.

It can express faith.

Resignation.

Politeness.

Avoidance.

A desire to end the conversation.

Or the verbal equivalent of closing a ticket without resolving it.

In this case, it was not a scheduling solution.

It was more like a curtain descending over reality.

I had an appointment.

The appointment had no operational meaning.

I had driven there.

They had apparently known, or could easily have known, that the car would not be handled.

Nobody had called.

And the final response was essentially:

Well.

Fate.

This is why I filed the story under “dialogues that end with a slap.”

Not because I actually slapped anyone.

I did not.

The joke was that the conversation had reached the point where language had no obvious next move.

The line after “hayırlısı” was simply silence.

Sometimes silence is the only available response to a system that refuses to recognize its own contradiction.

Looking back, the story is funny because it is so small.

Nothing catastrophic happened.

No money vanished.

The car did not explode.

Nobody was stranded in another country.

I lost time.

I was annoyed.

That was all.

But everyday frustration is usually made of exactly these small failures.

A person gives you a commitment.

You organize around it.

Then the commitment turns out to be informal in a way nobody told you.

This creates a specific kind of irritation.

It is not only inconvenience.

It is asymmetry.

One side treats the agreement as real.

The other side treats it as approximate.

That difference makes planning impossible.

A functioning appointment system is a promise about coordination.

Not necessarily a promise that the entire job will be completed by a certain hour.

But at minimum:

We expect you at this time.

We have allocated some capacity.

If that changes materially, we will tell you.

Without that, “appointment” becomes decoration.

A word printed over a queue.

This distinction applies far beyond car service.

Medical appointments.

Meetings.

Deliveries.

Repairs.

Interviews.

Installations.

Technical support visits.

A schedule is useful only if it reduces uncertainty.

If I still need to ask on the day whether the agreement is real, then the scheduling system has failed.

This is one of those areas where people often blame “communication.”

Communication is indeed part of it.

But that word can be too soft.

Sometimes the problem is not merely that people failed to communicate.

The problem is that nobody took ownership of the commitment.

Ownership is stronger than communication.

If you own the appointment, you notice when capacity disappears.

You call.

You reschedule.

You explain.

You do not wait for the customer to physically arrive and then discover the calendar.

Organizations often suffer from this gap.

There is a system for creating commitments.

There is no system for maintaining them.

The front desk can make the appointment.

The workshop changes.

The change is not propagated back.

Now two versions of reality exist.

In one:

Friday means Friday.

In the other:

Friday means maybe, depending on what happens.

The customer is living in the first version.

The service center is operating in the second.

The conflict appears at the counter.

This is a classic systems problem.

Information exists somewhere.

It fails to reach the place where it is needed.

The surprising thing is how often human frustration comes from stale state.

A person believes something that was true yesterday.

The system changed.

Nobody updated them.

Software engineers see this in distributed systems.

People see it everywhere else.

Your hotel reservation changes.

Your flight gate changes.

A meeting moves.

A delivery window disappears.

A price changes.

A document requirement changes.

The worst version is not change itself.

Change is normal.

The worst version is discovering the change only after acting on the old information.

Then the cost transfers to the person least able to prevent it.

In my case, the service center knew its own workload better than I did.

Only they could have known that Friday no longer worked.

So only they could have prevented the unnecessary trip.

That makes the missing phone call important.

A phone call would not have fixed the schedule.

It would have fixed the relationship.

“Sorry, we won’t be able to take the car Friday. Can we move you to Monday?”

Annoying?

Yes.

But understandable.

Now the customer has agency again.

They can reorganize.

The problem becomes shared.

Without the call, the customer absorbs all the waste.

This is one of the reasons people forgive bad outcomes more easily than bad treatment.

A delay explained honestly can be acceptable.

A delay discovered after unnecessary effort feels disrespectful.

Respect often appears operationally as early information.

Tell me before I travel.

Tell me before I wait.

Tell me before I build plans around something that is no longer true.

This is not sophisticated customer service.

It is basic coordination.

The old exchange also captures something very Turkish in tone.

“Hayırlısı.”

That phrase can end entire categories of conflict.

You can present a completely rational objection.

The other person can respond with a phrase large enough to contain destiny.

Now what?

You cannot argue with destiny.

At least not efficiently.

The phrase moves the problem out of process and into fate.

Scheduling failure?

Hayırlısı.

Bureaucratic confusion?

Hayırlısı.

Missing document?

Hayırlısı.

Perhaps Monday?

Hayırlısı.

There is humor in this because fatalism can be incredibly convenient for the person who caused the problem.

The universe becomes responsible at exactly the moment accountability would be uncomfortable.

Of course, this is not unique to Turkey.

Every culture has phrases that perform similar work.

“That’s just how it is.”

“These things happen.”

“It is what it is.”

“We’ll see.”

“Hopefully.”

Language can soften uncertainty.

It can also hide responsibility.

The phrase itself is not the problem.

Context is.

Sometimes “hayırlısı” is the only honest thing to say.

Nobody knows what will happen.

Fine.

But if the issue is that you scheduled a customer for Friday while knowing Friday was unusable, fate has limited involvement.

There is another lesson in the story about process design.

A bad process often survives because each individual step seems reasonable locally.

The receptionist schedules Friday.

Reasonable.

The workshop becomes overloaded.

Reasonable.

Someone decides the car should not sit there over the weekend.

Reasonable.

Nobody calls the customer.

Maybe everyone assumes someone else will.

Then the customer arrives.

The final outcome is absurd even though no single person had to make an obviously absurd decision.

Systems can fail without villains.

This matters because anger naturally searches for one person to blame.

The person at the counter becomes the face of the whole failure.

But they may not have created the appointment.

They may not control workshop capacity.

They may simply be the unlucky interface.

Front-line staff often absorb the emotional output of broken systems they did not design.

That does not make the customer’s frustration illegitimate.

It means the real solution is structural.

Who owns schedule updates?

Who sees capacity?

Who contacts customers?

What happens when today’s commitments cannot be met?

These questions sound bureaucratic until you have driven across town for nothing.

Then process design becomes deeply personal.

This is why good systems feel almost invisible.

You make an appointment.

You receive confirmation.

If something changes, you are notified.

You arrive.

The system knows why you are there.

No drama.

Nobody writes an essay about it.

Failure creates stories.

Reliability creates ordinary days.

The old entry exists because the system failed memorably.

If everything had worked, I would probably remember nothing.

That is unfair to competent organizations.

The best service often leaves no story.

The car is fixed.

You leave.

Done.

Human memory rewards exceptions.

Mostly bad ones.

This can distort our judgment.

One terrible encounter can become the entire identity of a company in our minds.

One great encounter can do the opposite.

We build narratives from small samples.

Sometimes that is unfair.

But from the customer’s perspective, the sample is the relationship.

If I visit once and the process fails, I experienced a 100 percent failure rate.

Statistics may disagree.

Emotion does not.

There is also something interesting about appointments themselves.

They are social technology.

A calendar entry seems trivial.

But it represents trust between strangers.

I promise to be there.

You promise to expect me.

This allows both sides to allocate time.

Without appointments, life becomes queues and guesses.

The appointment is a coordination contract.

Usually informal.

Still real.

That is why breaking it without notice feels bigger than the lost minutes.

It says:

Your time was not part of our calculation.

People notice that immediately.

Time is one of the few resources everyone experiences as personal.

You can refund money.

You cannot return an hour exactly as it was.

This makes unnecessary waiting disproportionately irritating.

The customer is not only asking:

Why wasn’t the car serviced?

They are asking:

Why did my time become free to waste?

That is a fairness question.

Organizations that understand this design around it.

Clear windows.

Accurate estimates.

Notifications.

Honest uncertainty.

If you cannot promise 10:00, do not promise 10:00.

Say morning.

If you cannot guarantee Friday, say tentative Friday.

Precision should match confidence.

False precision creates stronger disappointment than honest uncertainty.

This is a lesson that applies to engineering schedules too.

“We’ll finish Friday.”

Really?

Or:

“We currently expect Friday, but there is risk around X.”

The second sounds less satisfying.

It is more useful.

People can plan around uncertainty when uncertainty is visible.

Hidden uncertainty is what causes surprise.

Project management is full of Friday appointments.

A delivery date is agreed.

Everyone behaves as if it is real.

Internally, the team knows the probability is collapsing.

Nobody wants to say it yet.

Maybe we can still make it.

Maybe one more day.

Maybe the problem will disappear.

Then Friday arrives.

The stakeholder arrives metaphorically at the counter.

And someone says:

Today is Friday. Tomorrow is Saturday. Best come Monday.

At scale, this becomes very expensive.

The lesson is the same.

Bad news becomes more expensive as it ages.

Communicate early.

Not when certainty is perfect.

When the change becomes material.

The younger me did not turn the event into a project-management principle.

He wrote a dialogue.

That is better.

The dialogue preserves the absurdity.

Tuesday:

Appointment for Friday.

Friday:

It’s Friday, so we can’t do it.

Customer:

But you gave me the appointment.

Service:

Hayırlısı.

End scene.

There is almost nothing to improve.

It has the structure of a joke because real life occasionally writes better comedy than comedians do.

One premise.

One contradiction.

One impossible response.

What I appreciate now is that my younger self understood the core issue immediately.

Not:

You must fix my car today no matter what.

But:

You could have called.

That is the reasonable center of the story.

Plans fail.

Tell people.

This principle is so simple that organizations continuously fail to implement it.

Maybe because the call feels like admitting failure.

Maybe because nobody owns it.

Maybe because there are too many customers.

Maybe because bad news is uncomfortable.

Maybe because the organization values internal convenience more than external time.

Whatever the reason, silence rarely improves the situation.

It converts a scheduling problem into a trust problem.

Once trust is damaged, the next appointment is different.

You call to confirm.

You do not fully believe the date.

You build buffer into your own plan.

The system’s unreliability creates work for the customer.

This is another hidden cost of bad service.

Customers develop defensive procedures.

Call twice.

Bring extra documents.

Take screenshots.

Ask for the name of the person.

Confirm the address.

Arrive early.

Keep the receipt.

These behaviors are often signs of low institutional trust.

When systems are reliable, people can remain relaxed.

When systems are unreliable, people become amateur auditors.

That is exhausting.

The appointment story is tiny, but it belongs to that larger category.

You begin with trust.

Friday means Friday.

One absurd interaction later, Friday means:

Call first.

This is how institutions train people.

Not through official rules.

Through repeated consequences.

A reliable system trains users to trust.

An unreliable one trains users to verify everything.

Years later, I would rather live in systems where verification is optional.

Where a promise can remain small and still mean something.

An appointment does not need to be sacred.

It just needs to be real enough that both sides can plan.

And when reality changes, somebody needs to pick up the phone.

That is all.

The car can wait until Monday.

My time did not have to drive there first.