Travel conversation guide

Buy a transport ticket with the journey written down

Show where you want to go before discussing ticket names. Confirm which journey the ticket covers and what you must do before boarding.

Android release in preparation

Quick Translate and experimental Live Interpreter are the current foundation. This website will link to the official Google Play listing when it is public. Product previews and examples are illustrative.

See launch status →

Prepare the journey, not just a station word

Write the origin, destination, travel date and number of travellers. Use the operator’s stop or station names. Keep the return journey as its own question: a ticket that sounds like a return may still have time or route restrictions you need to understand.

This is a task checklist, not a complete translated ticket script. Transit terms and products vary by country and operator. Use the actual operator’s ticket page or staff explanation to resolve a fare, zone or validation rule.

Recognise two destination phrases

A la estación, por favor means “To the station, please”; Al aeropuerto, por favor means “To the airport, please” in the referenced travel booklet. These identify a destination in context; they do not specify a particular station, ticket type or route. Add the exact place name visually.

Ask these questions one at a time

DecisionShow or ask aboutConfirm before moving on
DestinationThe official stop name on a mapThis route reaches the intended place.
JourneyDate and one-way or return needThe ticket covers that journey.
TravellersA count and any relevant ticket categoryThe count on the ticket matches.
UseThe operator’s validation instructionsWhat to do and where before boarding.
ChangesA transfer or different serviceWhether it is included or needs another ticket.

Do not turn all five into a single spoken paragraph. If the first answer changes the route, later questions may need to change too.

Check the ticket itself

Compare the printed or displayed destination, date, quantity and any restrictions with your note. Ask staff about an unfamiliar term before boarding. Keep the official ticket accessible separately from a translation screenshot; a screenshot of a conversation is not itself a valid ticket.

EnglishSpanishUse
Can you write it down, please?¿Puede escribirlo, por favor?Formal singular request to write the preceding detail; lo refers to that detail. It does not translate a user-entered value.
More slowly, please.Más despacio, por favor.In the conversation context this asks for a slower pace, not a quieter volume.

Reference-checked by AI/editorial review; not native-speaker reviewed. No recorded audio is supplied. A phrase helps start or repair a conversation; confirm the other person’s answer separately.

Use the confirmation card for a date or place name and the directions guide for the stop’s entrance.

Sources and scope

Practical examples and checklists on this page are editorial exercises, not recordings, measured app results or claims about a currently released feature.

Help us improve Pocket’s website

Allow Google Analytics and Ahrefs Web Analytics to measure visits to Pocket’s website? Google also measures scrolling, outbound links and tool activity. You can decline and change your choice below at any time.

What is measured

With your permission, Google receives website activity and browser/device information. Ahrefs receives page visits and browser/device information, and uses IP addresses to estimate location. This measurement excludes URL query strings, fragments, form contents, email addresses and app conversations. Ahrefs does not receive referring URLs. Advertising personalization is disabled. Google Analytics cookies last up to 90 days; Ahrefs uses no analytics cookies. Your choice is saved on this device for 180 days. Provider privacy information: Google and Ahrefs. Contact Pocket support with website data questions.