Combine booking confirmations into one trip itinerary
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and combine booking confirmations into one trip itinerary.
LLMPrompt
Prompt
Copied 0
Build one clear itinerary from the booking confirmations below, so that the traveler, {{traveler}}, has a single document for the whole trip and any problems are caught before departure.
Home time zone: {{home_time_zone}}
Booking confirmations (flights, trains, hotels, cars), pasted as received:
"""
{{confirmations}}
"""
Meetings and other commitments on the trip, with addresses if known:
"""
{{meetings}}
"""
Format:
1. Trip summary: dates, cities and hotels, in three or four lines.
2. Day by day: one table per day with the columns Time (local), What, Where, Confirmation or reference, and Notes. Give every time in the local time of the place where it happens, and state the time zone whenever it changes. Mark overnight arrivals with "(+1 day)".
3. Check these: anything that looks wrong or missing, such as a very short connection, a hotel booking that does not cover every night, a meeting that starts before the traveler arrives, no transport booked between an airport and a hotel, or a name spelled differently across bookings.
4. Key contacts and references: each booking's provider, confirmation number and phone number, where the confirmations give them.
Rules:
- Copy times, dates, addresses and confirmation numbers exactly. Do not add terminals, addresses, check-in times or phone numbers that are not in the confirmations, even if you think you know them, because travel details change and a confident wrong detail is worse than a blank.
- Leave out payment card numbers, passport numbers and loyalty account numbers.
- Do not fix a problem by guessing. Flag it under Check these.
If a confirmation is unclear, for example a time with no date, or a date like 04/05 that could be read two ways, write it as given, mark it "[check]" and add it to Check these.
Keep it as short as the trip allows: one table per day and no prose between the tables. The itinerary should be accurate enough to travel on without opening a single confirmation email.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/travel-itinerary-from-booking-confirmations - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "travel-itinerary-from-booking-confirmations",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}