How shortlists work

Can someone actually pick this — without the assistant guessing?

Commercial and booking asks need more than a name on the list. If the offer, the limits, tonight’s facts, or the next step stay fuzzy, the assistant fills the gaps — and you can lose the selection even when you are already visible.

Northloop is a fictional example brand on this site, not a logged chat test.

Full article: You can be recommended and still not get chosen →

Shop

Offer
Northloop Trail Watch S, black, SKU NL-TRAIL-S-BLK, sold by the brand — not a vague category name or a bundle title that does not match the feed.
Limits
Ships to SK and CZ, 30-day returns, each size or edition as its own SKU — not “from €249” without saying which model that price belongs to.
Now
€279 EUR on the buy button, in stock today — the webpage, JSON-LD, and feed row all say the same thing.
Next
Buy on the shop’s canonical product URL — not an invented “available at Shop X” pulled from a marketplace listing in another country.

Travel and local stays

Offer
This hotel, restaurant, or walk — named operator, what the booking includes — not only a city nickname or a famous landmark.
Limits
Who fulfils the booking (operator vs marketplace), service area, dates the experience runs — not a third-party page with different rules than the operator’s site.
Now
Hours tonight, rooms or dates this week, seasonal access — your Maps listing and your own site agree.
Next
Official booking or enquiry URL, fees, and cancellation in plain language — not a link the assistant guessed because nothing official was findable.

Make those facts explicit, current, and easy to check.