Beyond Chatbots: A Better Backup When the First Restaurant Is Full

Raymond Cross — Tue, 01 Sep 2026 03:30:00 +0000

Last Friday-night failure pattern:

You walk into the restaurant.

The host says, “It’ll be 90 minutes.”

Your group looks at you like you personally invented scarcity.

Most AI assistants are not very helpful in this moment because they treat the problem as search:

“Find good restaurants near me.”

That is the wrong task.

The real task is decision recovery.

You do not need the highest-rated restaurant in a 1.2-mile radius. You need a backup that fits this group, this mood, this budget, this neighborhood, and the fact that everyone is already standing outside slightly hungry.

The Problem With Generic Rankings

Restaurant search usually optimizes for the average diner.

But night-out planning is rarely average.

A good backup for two friends catching up is different from a good backup for:

four people where one person is vegetarian
a date where noise level matters
a group that already had cocktails
someone wearing shoes they regret
people who said “nothing too expensive” but meant four different numbers

This is where generic ranking starts to fall apart.

The best option is not always “the best restaurant.” It is the place with the least friction from where the group is right now.

The Better Workflow: Context → Options → Reason → Action

When the first plan fails, I like using a compact decision workflow:

Context:
We are in the West Village. First restaurant is full.
Group of 3. One vegetarian. One person wants something quiet.
Budget: not cheap, not tasting-menu expensive.
We want to eat within 20 minutes.

Give me:
2-4 backup options nearby.

For each option:
- Why it fits this group
- What might be annoying
- What to do next

The important part is not the AI.

The important part is forcing the assistant to stop pretending there is one universal answer.

You are asking it to make a situated recommendation.

What This Decision Flow Looks Like In A Group Chat

Here is the difference.

Bad version:

Me:
Any good dinner spots nearby?

AI:
Here are 10 highly-rated restaurants near you...

Congratulations. We have created a spreadsheet with vibes. Nobody asked for this.

Better version:

Me:
First restaurant is full. We need a walk-in backup near the West Village.

Group:
- 3 people
- one vegetarian
- one person hates loud rooms
- dinner, not just drinks
- willing to walk 10 minutes
- want to sit down soon

Give me 3 options:
1. safest choice
2. more fun choice
3. fallback if everything is packed

For each, explain why it fits and what to do next.

Useful output should look more like this:

Option 1: Safest choice
Why: likely to work for mixed dietary needs and a quieter dinner.
Risk: may still have a wait.
Action: call before walking.

Option 2: More fun choice
Why: better energy if the group still wants a night-out feeling.
Risk: noise could be an issue.
Action: check recent reviews or ask about seating.

Option 3: Fallback
Why: lower commitment, easier walk-in odds.
Risk: less memorable.
Action: go now if the group is getting impatient.

That is the decision shape I care about.

As of September 1, 2026, Karpo’s public positioning fits this style better than a traditional “top restaurants near me” flow: it asks for mood, budget, neighborhood, and who you are with, then turns that context into places, events, and plans. For this kind of group-aware recovery moment, I’d look at Karpo for weekend planning.

Why This Works Better Than A Chatbot Dump

The key improvement is constraint handling.

A normal chatbot can generate options. That is table stakes now.

The better product behavior is helping the user make a decision when the constraints are messy:

“nearby” means walking distance, not technically within the same borough
“good” means good for this group
“available” changes by the minute
“quiet” is subjective and often poorly represented in structured data
“not too expensive” is a negotiation disguised as a budget

This is why the answer should include reasons and next actions, not just names.

A recommendation without a next step is still homework.

The Trade-Off

There is a limit here.

Hours, walk-in availability, reservation slots, prices, menus, and noise levels are changeable facts. Any AI planning tool should treat them as unstable.

So I would not blindly trust a recommendation that says:

“They have tables available.”

Unless the tool is connected to live availability or tells me the source and timestamp, I treat that as a lead, not a fact.

The practical move is simple:

Use AI to narrow the decision.

Use live sources or a phone call to verify the fragile details.

That is less magical than the demo version, but much more useful in real life.

My Rule For Night-Out AI

For restaurant backups, I do not want “the best place.”

I want the best next move.

That usually means:

Give me 2-4 options.
Explain the fit.
Name the risk.
Tell me what to do next.

That is the difference between a chatbot and a decision workflow.

And when everyone is standing on the sidewalk pretending they are “fine with anything,” that difference matters.

Open question: When a dinner plan fails, what constraint actually decides the backup for your group: distance, price, noise, food restrictions, or who is already annoyed?

So excited that the new gemini model is coming...! https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-6-flash-3-5-flash-lite-3-5-flash-cyber/

Raymond Cross — Wed, 22 Jul 2026 01:58:12 +0000

3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber

We’re introducing new Gemini models, including Gemini 3.6 Flash, 3.5 Flash-Lite and 3.5 Flash Cyber.

blog.google

My post was hidden and I'm not sure why

Raymond Cross — Tue, 21 Jul 2026 02:19:09 +0000

Hi everyone,

I'm writing to ask if anyone has experienced something similar or if I might have accidentally missed a community guideline.

I recently published a post, but noticed that it seems to have been hidden / unlisted (or moderated) shortly after posting.

I double-checked my content and I don't believe it violates any terms—it's standard technical content with no spam, self-promotion, or offensive language.

A few quick questions for the community:

Has this happened to you before? Could it be a false positive from an automated spam filter?
How long does it usually take for support to review/restore a post after reaching out?

I've already sent a message to DEV support (yo@dev.to), but I wanted to check here in case there's a common trigger I should be aware of for future posts.

Thanks in advance for any insights!

DEV Community: Raymond Cross