← All articles

citysense

Why not just ask a chatbot?

You can. Ask a general AI assistant to plan three days in a city and you will get a confident, fluent, well organized answer in seconds, for free. For some of the trip that is exactly the right tool. For the part that decides whether the trip goes well, it is the wrong one, and the reason is not that the assistant is stupid. It is that it was built to produce a plausible answer, and on the ground plausible and true are not the same thing. A citysense guide exists for that gap: checked facts underneath, a finished shape on top, and an editor in between. Here is where each tool belongs.

What a chatbot is good at

Be fair to it. A general assistant is excellent at the parts of travel that are conversation: how do I say this, what does this dish contain, is there a train on Sunday, rewrite my message to the hotel, compare these two flights. It answers follow-ups, it adapts to a change of plan at midnight, and it is already in your pocket. We use these tools too. Nothing below argues you should stop.

Where it fails you on the ground

Three failures repeat, and travelers meet them in the same order.

It invents. Asked for a hidden gem, a general model will produce one, because producing is what it does. Now and then the restaurant closed last year, the museum wing is shut for renovation, or the tram line stopped running before you booked. The model is not lying. It has no way to know, and no incentive to say so.

It forgets what it said. Ask on Monday and again on Thursday and you get two different cities. The second answer does not know about the first, the hotel you chose in between, or the neighborhood you have already decided against. You become the editor, holding the pieces together in a notes file.

It has no shape. A chatbot hands you fragments on request: a list here, a paragraph there. What a first visit needs is an order: how the city is put together, then where to sleep, then how it eats, then the codes that hold everywhere. That order is editorial work, and no amount of asking produces it.

What a citysense guide does differently

The facts are decided before you ask. Every city has a catalog, built and checked before it goes on sale: an AI drafter that must search and cite a source for every dated or named claim, then a second AI pass that shares nothing with the first and searches every claim again, then an editor who rules on the judgment calls, then a lock. When you order, the AI that writes your guide may choose from that catalog and may not add to it. If a place is not in the catalog, it is not in your guide. The model is allowed to leave things out; it is not allowed to make things up.

It recommends what stays true. A guide that names a specific bar is wrong the week the bar changes hands, so a citysense guide works by type and anchors to landmarks: the family trattoria near the old market, the covered food hall, the hillside of terraced cafés. You still find the place; you find it with your feet, and the recommendation is still right the week you travel.

It is finished. Twelve pages for the City Guide, eighteen for the Personalized Guide, in an order written to be read once before you land. You do not assemble it, prompt it, or remember what it said on Monday. It is the same document on Thursday.

It is personal where that is worth something. The Personalized Guide takes five minutes of questions, your pace, your interests, your dates, who is traveling, your budget band and diet, and chooses your three neighborhoods, eight experiences and three days from the catalog. That matching is the part of the job AI is good at, and it is the only part we hand it.

Use both

The honest answer to the question in the title is: ask the chatbot the questions that have one answer and change by the hour. Read the guide for the questions that shape the trip and do not change: where to sleep, how the city is put together, how it eats, what the locals expect of you. One is a conversation. The other is a decision you make once, well, before you land.

Questions people ask

Can I trust an AI to plan a trip?

For questions with one answer that you can verify on the spot, yes. For where to stay and how a city works, trust it only when its facts come from a source that was checked before you asked. A general assistant has no such source; a citysense guide has a locked catalog.

Is a citysense guide written by AI?

The words are, from a catalog of facts that was researched and checked by two separate passes before you ordered. The AI selects and writes; it does not decide what is true.

Why does the guide not list restaurants?

Because specific venues change hands, hours and quality faster than any guide can follow. The guide names dishes and types of place, anchored to landmarks that stay put, so it is still right the week you travel.

Does the guide replace my phone on the trip?

No. Use your map for the next three hundred meters and your assistant for the question of the moment. The guide is for the decisions you make once: where to sleep, how the city is put together, what it expects of you.

Written by citysense editorial. Product details as of October 2026.