Skip to main content
SubZeroDev

Professional uncertainty since 2026.

Well… Why not?


Customer Service Denied

· 4 min read

I got to the bar with the Ridgeback and tried to do the considerate thing.

There is a couch away from the entrance.

Perfect.

Sit there.

Put the dog beside me.

People can enter and leave without stepping over seventy kilograms of opinion.

Reasonable architecture.

Apparently not.

The Couch Incident​

The woman working there saw what I was doing and immediately reacted.

No.

Not there.

Last time the dog had been near the couch she had to clean it.

And clean it.

And clean it.

The dog had not, as far as I could tell, eaten the couch.

She had not redesigned the upholstery.

She had been near it.

Nevertheless, this was apparently a remembered sanitation event of historic significance.

I tried to explain.

I am not trying to install the dog into the couch.

I am trying to sit here specifically so she is not in the way of every person entering the bar.

Eventually everybody calmed down.

Fine.

No couch.

The Approved Location​

So where did the Ridgeback end up?

Exactly in the fucking entrance.

Of course she did.

Not sort of near the entrance.

Not adjacent to the traffic path.

In the way.

The dog became a physical access-control layer.

Every customer entering or leaving now had to route around a large brown roadblock.

Apparently this was acceptable.

So we had established the operating priorities:

Dog near couch:

Unacceptable.

Dog blocking customers:

Approved.

Excellent.

The system has rules.

They are just not the rules I expected.

Uncle Ben Learns​

The dog learned nothing.

Important distinction.

The Ridgeback did not walk away from this experience with a revised model of restaurant seating.

She did not reflect.

She did not conclude:

I should avoid upholstered furniture because cleaning burden matters to the staff.

No.

She lay in the entrance.

Uncle Ben learned the lesson.

Do not attempt to optimize the bar's dog-placement architecture.

Furniture has priority.

Customers can route around the Ridgeback.

Fine.

System behavior documented.

Adapt accordingly.

Then Customer Service Was Disabled​

A little later I ordered something.

Normally, in the radical hospitality model, a customer sits somewhere and somebody eventually brings the thing.

Not today.

Apparently customer service had also been deprecated.

Order shit.

Wait.

Eventually discover that shit is waiting at the bar.

Go pick up shit at the bar.

Excellent.

So by this point the complete service model was:

Couch protected.

Dog in entrance.

Customers maneuver around dog.

Customer retrieves own order.

Everything important is functioning exactly as designed.

Assuming the design goal is to protect the couch.

Furniture Matters​

This is one of those situations where I do not even get angry.

I mostly become fascinated.

Because once you stop expecting the system to make sense according to your priorities, it becomes very easy to operate.

I thought:

Keep the dog out of the way.

The bar thought:

Keep the dog away from the couch.

Different requirement.

Mine lost.

Okay.

Now I know.

This is not a dispute.

This is documentation.

Next time I arrive, I do not need to reason from first principles.

I know the local API.

Do not sit there.

Dog goes wherever the dog is apparently allowed to go.

If that means every customer has to perform a small Ridgeback navigation exercise at the entrance, so be it.

The couch remains pristine.

Civilization survives.

Customer Service Denied​

I wanted coffee.

I got coffee.

Eventually.

The dog wanted to lie down.

She lay down.

The woman wanted the couch protected from the dangerous possibility of nearby dog hair.

Couch protected.

Customers wanted to enter and leave.

Customers are adaptable creatures.

No outage.

No escalation.

No root-cause analysis required.

Just another perfectly normal morning at the Grandpa Convention.

Furniture matters.

Customers can route around the Ridgeback.

Customer service:

Denied.