A maps app has never heard of your hotel. That's the gap, and it's why "which train do I take?" still costs you two lookups and a paste.
Two days in Chicago with an agent that already knows where you are, where you're staying and what's on your calendar. The right train, the right stop, the brief before the meeting, the tours for the kids.
Fasrad · September 16, 2026 · 4 min read
A maps app has never heard of your hotel. That's the gap, and it's why "which train do I take?" still costs you two lookups and a paste.
An agent holding your position and your reservation answers in one line. A Fasrad agent works out where you are from your phone and your calendar, plus whatever it remembers about you, then comes back with the line name, the departure time and the walk at the other end. Here's how that runs over two days in Chicago for Nora, a product manager flying in Thursday for a Friday meeting, with her kids joining on Saturday.
Your position reaches the agent three ways and you control each one. The web app asks your browser for a fix when you open a chat, governed by the Track Location switch in Account Settings. On Telegram, sharing a location once records it. The third source is inference: a hotel booking on the calendar and a note saying home is Austin tell the agent where you're expected to be, and it says which of the two it's leaning on.
Every position carries its age. A fix from six hours ago is labelled six hours old. A fix that would have required faster-than-airplane travel since the last one gets held until a second reading confirms it.
It uses the best evidence it has and tells you how current that evidence is. That's what you want from anyone giving you directions.
Nora lands, opens the agent on her phone and types "What train do I take to the Loop?" She didn't type an origin. She didn't give it the hotel address.
It has the airport from the phone fix and the hotel from the reservation it filed on her calendar last week. The answer names the Blue Line toward Forest Park, 45 minutes to Clark/Lake, $5 with a Ventra ticket from the machine on the platform, next train at 4:52 PM, and a six-minute walk to her hotel on West Lake Street. A taxi, it adds, runs about 50 minutes at this hour.

On the train she asks "Should I get off at Clark/Lake or Washington?" and gets one sentence back. Clark/Lake, because the hotel entrance is on that side of the street.
That's a question a maps app can't take, for the reason at the top of this article.
The hotel emails a confirmation with a different room block and a breakfast voucher on it. Nora screenshots the mail and sends "Add this to my calendar". It reads the image, updates the stay with the new confirmation number and the breakfast hours, and leaves the address in place. That address is what makes every later directions question work. A personal assistant agent that reads screenshots cuts out most of what travel admin actually consists of.
Then: "Somewhere for dinner within ten minutes of here, not a chain, table for one." Here means the hotel. She's standing in it. Three places come back with walking minutes and a map she can zoom, and "Show me the second one on a map" does exactly that.
The morning briefing opens with weather. 58°F and clear at 7:00, 71°F by 2:00 PM, rain moving in after 8:00. Under that sits the day: a 2:00 PM meeting at the Merchandise Mart with two people from the client's design team, and a 6:30 dinner reservation the agent found in her inbox.
Departure timing arrives closer to the event, worked out from where she actually is by then, so it holds even when she changes her plans over breakfast.

Forty-five minutes ahead, the pre-meeting brief lands. It names the two attendees from her contacts, pulls the agenda off the email thread they traded on Tuesday, and lists the one question still open from last month's call. The logistics line reads: leave the hotel by 1:35, fourteen minutes on foot along the river, 71°F, no service alerts on the Brown Line if she'd rather ride.
Briefs get built when they fire rather than the night before. A meeting moved to 3:00 PM produces a brief for 3:00 PM.

Afterwards she types "Walking directions to the Art Institute" and gets the route from the Mart, 22 minutes, with the Michigan Avenue entrance, because that's where she is now. A calendar-connected agent also adds the dinner walk to the reservation without being asked.
Friday night she sends "The kids land at 10 tomorrow. Give me some sightseeing tours for the weekend, ages 8 and 11." Back come bookable cards carrying price, duration and rating, with free cancellation noted where it's offered. An architecture river cruise came back first. Under it sat a Chicago-style pizza tour and a Saturday afternoon slot at the Field Museum with skip-the-line entry. Each card opens its booking page. The reply leads with Saturday's weather, 74°F and sunny, and puts the cruise on Saturday and the museum on Sunday when the forecast turns.

Her kids' ages stick. She typed 8 and 11 once on Friday night, and every later suggestion that weekend was filtered by them without her saying so again. Telling it "they're 9 now" in March would replace that, and the older number goes to the archive rather than being argued with.
Saturday morning the family is standing on Navy Pier when she asks "What is around here worth seeing with kids?" The phone fix does the work. It lists the Children's Museum and the Centennial Wheel with walking minutes, then offers a route back to the hotel that passes a good ice cream place. The conversation keeps going on the walk through a Telegram assistant, same agent and same memory.
No. Without a device fix the agent works from your calendar and what it remembers, such as a hotel booking or your home city, and it tells you it is using an expected position rather than a live one. Sharing a location from your phone or on Telegram makes answers precise to the block.
It looks up live transit routes between your position and the destination, including line names, departure times and walking connections, and can anchor the search to a departure or arrival time you give it. It reports the route as text and, if you ask for it, as an interactive map.
No. The day-before message only carries information that helps you prepare, such as the weather at the destination or a known disruption. Departure times and connections come from a check that runs shortly before the event, from wherever you are at that moment.
A fix that would require impossible travel since the last one is held until a second reading agrees, and every position the agent uses carries its age. You can also tell the agent where you are in plain words, which overrides the device.
Yes. Track Location in Account Settings stops the web app from asking your browser for a position. The agent then relies on your calendar, your notes and anything you tell it directly.
Yes. Transit routing, place search, weather and tours cover the same cities the underlying map and booking services do, and the agent answers in the language you write in.