alt Hacker NewsI initially didn’t read this post, fixated on “company event”, and thought it could be used for a single-day, one-off “thing to do tonight given (location) and (preferred activities/venue type) after (work end time)” It presented hotels and then some potential activities, but didn’t look up the time. When I asked about what is open after the time, the agent seemed to realize my request was not in your typical use case flow and gave me a refusal.
It’d be cool to offer one-off event suggestions, but I understand that’s probably not as easily monetizable.
Replies
Since there has been more than one case of this misunderstanding in the thread, I've changed the title to say "retreats" instead of "events". That (to me at least) that implies overnight stays.
That is interesting feedback, and you are right.
Right now the AI flow is optimized for multi-day events where people stay at least one night, like offsites, retreats, and conferences. When you shifted it to a same-day “what should we do tonight after work” use case, you basically stepped outside its current planning model, so the refusal you saw is on us.
We do support day events and activities on the supply side, but they are not yet fully integrated into the AI agent flow. Over the next few weeks, we are plugging that inventory into the system so it can handle more one-off and shorter formats.
Monetization is part of the equation, but it is also a product focus decision. We started with the higher-friction, higher-stakes planning problem. Expanding into lighter-weight, single-day coordination is definitely interesting and your comment is a good nudge in that direction.