Jeff Bullas

Nice and practical — that benefit-led headline + two-sentence quick win is exactly the kind of routine that turns generic copy into something that converts. Here’s a compact checklist and a step-by-step you can apply right now, plus a ready-to-paste AI prompt and a worked example.

What you’ll need

• Product name and one clear customer benefit (what they get)
• One differentiator or proof point (material, rating, guarantee)
• 10–20 minutes and a 2-version testing mindset

Step-by-step (do this now)

1. Set a 15-minute timer. Focus on one product.
2. Write a benefit-led headline (customer-first: what they gain).
3. Write two short sentences: first = how it delivers the benefit; second = proof or risk-remover.
4. Ask AI for 3 angles (practical, emotional, aspirational). Pick one and ask AI to shorten to your tone.
5. Edit: swap bland words for one sensory detail and add an objection sentence if space allows.

Quick do / do-not checklist

• Do lead with benefit. Be specific. Use one proof point.
• Do keep sentences short — scannable copy converts.
• Do-not list every feature like a spec sheet.
• Do-not use vague adjectives (“great”, “best”) without proof.

Worked example

Product: Insulated Travel Mug

Headline: Keeps your coffee hot for 6 hours — so your first sip is always satisfying.

Two-sentence description: Double-wall stainless steel and vacuum insulation lock heat in while staying comfortable to hold. Backed by a 1-year guarantee and dishwasher-safe parts, it’s the mug you’ll reach for every morning.

Mistakes & fixes

• Too generic? Fix: add a concrete number or material (e.g., “6 hours”, “stainless steel”).
• Too feature-heavy? Fix: lead with the outcome customers want, then add one supporting detail.
• Sounds like a bot? Fix: add a tiny sensory word or a short objection line (“no spills”, “guaranteed”).

Copy-paste AI prompt (use as-is)

Write three short product descriptions for an insulated travel mug. Each description should be one benefit-led headline plus two short sentences. Offer three angles: practical (focus on function), emotional (focus on feeling), and aspirational (focus on lifestyle). Keep language simple, avoid generic adjectives, include one proof point in each, and limit each description to 25–30 words.

Action plan (this week)

1. Run one 15-minute sprint for 3 products this session.
2. Test headline A vs B on product page or email subject line.
3. Keep the version that raises CTR or adds most sales; repeat twice for tuning.

Small, focused routines beat occasional, perfect rewrites. Use AI to draft fast, then use your human edit to add the proof and personality that actually converts.

Fast win (under 5 minutes): change any “7-day overdue” template to a “friendly reminder” that triggers after the due date for Net 30 (e.g., Day +5). Update the subject to: “Friendly reminder — invoice #{{INV}} due {{DUE_DATE}} (pay in one click).” Send it to yourself once to confirm links. That one tweak keeps tone calm and boosts response.

You’re right: cadence must match the terms. Let’s lock in a term-aligned sequence and add two AI upgrades that quietly increase collections without denting relationships: pre-due nudges and tone adaptation.

What you’ll need

• Invoicing/accounting tool with automations or an integration platform.
• Per-invoice payment link and a clear dispute/contact route.
• Clean customer contacts, listed payment terms, and a “strategic accounts” list.
• Basic AI access (any LLM) to generate/refine templates and tone variants.

Step-by-step setup

1. Map your terms and set baselines. For each common term, define timing relative to the due date (not the invoice date):
   • Net 15: Day -2 (heads-up), Day +3 (friendly), Day +14 (firmer), Day +30 (human).
   • Net 30: Day -3 (heads-up), Day +5 (friendly), Day +20 (firmer with plan), Day +45 (human).
   • Net 45: Day -5 (heads-up), Day +7 (friendly), Day +25 (firmer), Day +50 (human).
2. Create a three-message sequence per term. Keep emails short, include invoice number, amount, due date, pay link, and a dispute link. Label the first two messages as “heads-up” or “friendly reminder,” not “overdue,” until you’re beyond ~10 days past due.
3. Layer tone rules. Use “friendly” up to +10 days, “neutral/firmer” after that. For strategic accounts, stop automation after the second reminder and hand off to a human.
4. Add a payment-plan offer trigger. If unpaid at Day +20 (Net 30), auto-offer a short plan (e.g., 50% now, balance in 14 days) via a simple reply or {PLAN_LINK}.
5. Handle exceptions automatically. If an email bounces, create a task for a phone follow-up. If a reply contains dispute language (“incorrect amount”, “PO”, “credit”), pause reminders and route to a review queue.
6. Test end-to-end on 10–20 invoices. Check deliverability, links, and that payments auto-reconcile to the correct invoice.
7. Monitor and tune. Track open/click rates by step, days-to-pay after each reminder, and complaint rate. Adjust timing and subject lines accordingly.

Insider refinements that move the needle

• Pre-due heads-up works. A short Day -3 nudge reduces “oops, forgot” without sounding pushy.
• Subject line formula that converts: “Invoice #{{INV}} — {{AMOUNT}} — due {{DUE_DATE}} — pay in 10 seconds.” Clear, specific, action-oriented.
• Micro-intent link: add “Need a bit more time?” link that pauses automation and suggests a call or a plan. People appreciate the option.
• Quiet hours: schedule sends Tue–Thu mid-morning local time; it lifts response and reduces spam complaints.

Ready-to-use templates (Net 30 example)

• Day -3 (heads-up)Subject: Quick heads-up — invoice #{{INV}} due {{DUE_DATE}}Body: Hi {{NAME}}, a quick reminder that invoice #{{INV}} for {{AMOUNT}} is due on {{DUE_DATE}}. You can pay securely here: {PAY_LINK}. Questions or PO updates: {DISPUTE_LINK}.CTA: Pay now: {PAY_LINK}
• Day +5 (friendly)Subject: Friendly reminder — invoice #{{INV}}Body: Hi {{NAME}}, our records show invoice #{{INV}} for {{AMOUNT}} is now a few days past due. Here’s the one-click payment link: {PAY_LINK}. If anything looks off, tell us here: {DISPUTE_LINK}.CTA: Settle in seconds: {PAY_LINK}
• Day +20 (firmer with plan)Subject: Action needed — invoice #{{INV}} {{AMOUNT}}Body: Hi {{NAME}}, invoice #{{INV}} for {{AMOUNT}} is still open. You can pay here: {PAY_LINK}. If helpful, choose a short payment plan option: {PLAN_LINK} or reply to arrange dates.CTA: Resolve today: {PAY_LINK}

Copy-paste AI prompt (creates term-aligned sequences and tone)

You are an Accounts Receivable assistant. Given payment terms and a client profile, produce a 3-step reminder sequence with timing relative to the due date and short emails that match tone by stage. Requirements: 1) Align timing to terms (examples: Net 15, Net 30, Net 45). 2) Use “heads-up/friendly” before +10 days past due; firmer after. 3) Include placeholders {{NAME}}, {{INV}}, {{AMOUNT}}, {{DUE_DATE}}, {PAY_LINK}, {DISPUTE_LINK}, {PLAN_LINK}. 4) Output: a) a schedule list (e.g., Day -3, Day +5, Day +20) and b) three email templates with subject, 2–3 sentence body, and a one-line CTA. 5) Add a note with when to pause automation (on dispute/bounce) and when to route to human for strategic accounts.

Mistakes to avoid (and quick fixes)

• Calling it “overdue” too early. Fix: use “heads-up” and “friendly reminder” until at least +10 days.
• One-size-fits-all cadence. Fix: segment by terms and by account value; hand off strategic clients after the second reminder.
• Long emails. Fix: 2–3 sentences, then a clear CTA.
• Broken pay links or poor reconciliation. Fix: test invoice → payment → ledger matching before launch.
• Ignoring replies. Fix: route “help”, “PO”, or “dispute” keywords to a manual queue and pause the flow.

1-week action plan

1. Day 1: Export invoices by terms; pick one term (Net 30) to pilot. Draft the three messages above.
2. Day 2: Configure triggers relative to due date (Day -3, +5, +20). Add exception list for strategic accounts.
3. Day 3: Set up bounce/dispute rules to pause and create tasks. Enable payment-plan link.
4. Day 4: Send an internal test (10–20 invoices). Confirm deliverability, links, and auto-reconciliation.
5. Day 5: Go live to a small cohort. Monitor opens, clicks, and payments.
6. Day 6: Review tone complaints (aim for zero), adjust subjects and send times.
7. Day 7: Compare days-to-pay vs. baseline and expand to the next term group.

Bottom line: match cadence to terms, keep messages short, and let AI handle tone and timing while you step in for exceptions. Do this well and you’ll speed up cash without sacrificing goodwill.

Yes — and we can make it feel almost automatic. Give the AI a tight brief once, then run a short weekly review loop. That’s how you turn big goals into doable weeks without overwhelm.

Here’s the system I use with clients over 40 who want progress without the grind: capacity-capped planning plus a 15-minute weekly reset. It’s simple, repeatable, and forgiving when life happens.

• What you’ll prepare (5 minutes)
  • Your one-sentence goal and deadline.
  • Your weekly time budget (be honest — we’ll add a safety buffer).
  • Constraints: people, tools, dependencies, known blockers.
  • Definition of done: what “finished” looks like in one sentence.
  • Where tasks will live: calendar or to-do app.

1. Do this first
   1. Pick a realistic weekly capacity. Then plan only 80% of it. That 20% buffer is the difference between momentum and burnout.
   2. Decide your work windows (e.g., Tue/Thu 9–11am). Tasks expand to fill space; we’ll give them a container.
   3. Run the planning prompt below to generate a 4-week plan with A/B/C priorities and hour estimates.
   4. Keep only A tasks if the week is tight. B and C are stretch tasks, not promises.
   5. Import A tasks into your calendar as blocks. Treat them like appointments.

Copy-paste AI prompt (planning)

You are my capacity-capped planning assistant. Goal: [insert]. Deadline: [date]. Weekly capacity: [hours/week]. Preferred work windows: [e.g., Tue/Thu 9–11am]. Constraints: [tools, people, dependencies]. Definition of done: [one sentence]. Create a 4-week plan. For each week provide 3–5 tasks, estimated hours per task, A/B/C priority, and one measurable weekly outcome. Enforce total hours per week ≤ 80% of capacity. Front-load decisions and setup in Week 1. Flag dependencies. End with a one-paragraph milestone summary and a plain checklist I can paste into my calendar.

Insider trick: Ask the AI to start with 3 clarifying questions if anything is vague. You’ll get a sharper plan and fewer rewrites.

Example (two capacities to show realism)

• Goal: “Launch a simple newsletter with a landing page by March 31.”
• Capacity 3 hrs/week (buffered plan at 2.4 hrs):
  • Week 1 (2.4h): Choose topic + name (0.5h, A); pick tool (0.5h, A); draft landing page copy (1.4h, A). Outcome: draft copy ready.
  • Week 2 (2.4h): Build landing page (1.5h, A); set up sign-up form (0.5h, A); write welcome email (0.4h, B). Outcome: page in staging.
  • Week 3 (2.4h): Test + fix (0.8h, A); design simple header (0.6h, B); write first issue outline (1.0h, A). Outcome: page ready to go live.
  • Week 4 (2.4h): Launch (0.5h, A); share to 1 channel (0.7h, A); schedule issue #1 (1.2h, A). Outcome: first 10 sign-ups.
• Capacity 6 hrs/week (buffered plan at 4.8 hrs):
  • Weeks mirror above, but with one extra B task each week (e.g., add a basic lead magnet draft). Outcome target: 25 sign-ups by Week 4.

Your weekly rhythm (the “automatic” part)

1. Monday: glance at the plan, confirm calendar blocks (2 minutes).
2. Midweek: if a block slips, keep the same total hours — move, don’t delete (1 minute).
3. Friday: 15-minute review using the prompt below. That’s your reset for next week.

Copy-paste AI prompt (weekly review)

You are my planning editor. This week I planned: [paste tasks with A/B/C and hours]. I completed: [list]. Blockers: [list]. Keep next week within ≤ 80% of my capacity: [hours/week]. Roll over only what matters, re-estimate hours, keep 3–5 tasks total, and propose one task to drop. Output: revised weekly list (A/B/C, hours), one measurable outcome, and a 1-sentence rationale.

Optional daily focus prompt (when time is tight)

I have [X] minutes now. My Week [N] A tasks are: [list]. Create a mini plan with: (1) 5-minute setup, (2) focused blocks, (3) 5-minute wrap with next step. Keep me within this time.

Common mistakes and fast fixes

• Planning to 100% capacity → Fix: cap at 80% and protect the buffer.
• Vague tasks → Fix: start each with a verb and an output (e.g., “Draft 300-word landing copy”).
• Ignoring dependencies → Fix: ask the AI to flag blockers and front-load decisions in Week 1.
• Not calendaring → Fix: every A task gets a time block the moment it’s accepted.
• Over-collecting ideas → Fix: keep a separate backlog; only 3–5 tasks enter a week.

7-day starter plan

1. Day 1: Pick your goal, deadline, and weekly hours.
2. Day 2: Run the planning prompt. Answer clarifiers. Get the 4-week plan.
3. Day 3: Keep only A tasks for Week 1. Block time.
4. Days 4–6: Work the blocks. Move, don’t delete.
5. Day 7: Run the weekly review prompt. Adjust Week 2.

What to expect

• Week 1: decisions and setup; you’ll feel clearer immediately.
• Weeks 2–3: steady execution, small course corrections.
• Week 4: a testable milestone and a measurable result.

Reply with your goal, deadline, and how many hours per week you can commit. I’ll tailor the first 4-week plan and your Week 1 A-list so you can start today.

Quick win (under 5 minutes): open your invoicing tool, create a 7-day overdue email template with a clear pay link and invoice number, then save it as a draft. Send it to one internal test account to confirm links — done.

Why this matters: automated reminders remove the grunt work, keep your tone consistent, and free hours each week — without annoying good customers when done politely.

What you’ll need

• Invoicing/accounting tool that supports templates or automations (or Zapier/Make if not).
• Standard invoice template, one-click payment link and dispute link.
• Customer contact list with email (optional SMS) and payment terms.
• Simple rules: cadence (e.g., 0, 7, 21 days), escalation, and exceptions for high-value accounts.

Step-by-step setup

1. Pick one invoice type to start with (monthly recurring or standard services).
2. Create three short templates: invoice sent, 7-day polite reminder, 21-day firmer notice.
3. Map fields: customer name, invoice number, amount, due date, {PAY_LINK}, {DISPUTE_LINK}.
4. Define triggers: send invoice immediately; send reminder at 7 days overdue; send escalation at 21 days with phone contact.
5. Set exception rules for strategic/high-value clients to go to a manual queue.
6. Run an internal test batch (10–20), check deliverability and payment links, then enable for a small customer cohort.

Example templates (short)

• Invoice sent: Subject: Your invoice #{{INV}} — Due {{DATE}}. Body: Hi {{NAME}}, attached is invoice #{{INV}} for {{AMOUNT}} due {{DATE}}. Pay here: {PAY_LINK}. Questions? {DISPUTE_LINK}.
• 7-day reminder: Subject: Friendly reminder — invoice #{{INV}} is 7 days overdue. Body: Hi {{NAME}}, our records show invoice #{{INV}} for {{AMOUNT}} is overdue. Pay now: {PAY_LINK}. Need help? {DISPUTE_LINK}.
• 21-day notice: Subject: Action needed — invoice #{{INV}} overdue 21 days. Body: Hi {{NAME}}, invoice #{{INV}} ({{AMOUNT}}) is 21 days overdue. Call us at [phone] or pay here: {PAY_LINK}. To request a payment plan: reply to this email.

Common mistakes & fixes

• Too aggressive cadence — fix: add a longer grace period and A/B test tone.
• Automating strategic clients — fix: add value-based exceptions and manual review.
• Broken payment links or reconciliation issues — fix: test end-to-end and enable auto-match of payments.

Action plan (next 7 days)

1. Day 1: Create 3 templates and map fields.
2. Day 2: Configure automation rules and exception list.
3. Day 3: Run internal test and fix links.
4. Day 4–6: Pilot with 10–20 customers and track opens/clicks/payments.
5. Day 7: Review metrics (DSO, % paid on time) and iterate.

Copy-paste AI prompt (use to generate polished templates)

Act as a professional B2B collections writer. Produce three concise email templates: (1) invoice delivery, (2) polite 7-day overdue reminder, (3) firmer 21-day overdue notice offering a payment plan. Include subject line, 2–3 sentence body, and one-line CTA. Use placeholders: {{NAME}}, {{INV}}, {{AMOUNT}}, {{DUE_DATE}}, {PAY_LINK}, {DISPUTE_LINK}. Tone: calm, professional, relationship-first.

Start small, measure, and protect customer relationships with staged escalation. Get the basics working this week and you’ll buy back hours and improve cash flow fast.

Best,

Jeff

Quick win: In under 5 minutes, paste the sample prompt below into an AI chat with your goal filled in and you’ll get a tangible 4-week task plan to edit and use.

Why this works

AI is great at drafting structure — milestones, weekly tasks, estimated hours. But it needs clear inputs (goal, deadline, time you actually have) and one short human review to make the plan realistic.

What you’ll need

• A concise goal (one sentence) and a deadline
• Your real weekly capacity in hours
• Key constraints (people, tools, blockers)
• A place to store tasks (calendar, Todo app, spreadsheet)

Step-by-step (do this now)

1. Write your one-line goal and deadline. Example: “Launch a lead magnet and landing page by Dec 1.”
2. Open an AI chat and paste the prompt below, replacing the bracketed parts.
3. Ask for 4 weekly lists with 3–5 tasks each, hours per task, priority (A/B/C) and one measurable outcome per week.
4. Quick review: remove anything you can’t do, re-balance hours, keep only A tasks for the week if overloaded.
5. Import top-priority tasks into your calendar and block time to do them.
6. Do a 15-minute review at the end of each week and adjust the next week’s tasks.

Copy-paste AI prompt (use as-is)

You are a productivity assistant. Convert the following goal into a 4-week execution plan. Inputs: Goal: [insert goal]. Deadline: [insert date]. Weekly capacity: [hours/week]. Constraints: [people, tools, blockers]. For each week produce 3–5 tasks, estimated hours, priority (A/B/C), and one measurable outcome. Also list the milestone at the end of 4 weeks. Keep tasks actionable and limited to my weekly capacity.

Example (short)

• Week 1: Decide lead magnet topic, draft outline, set up landing page skeleton — 6 hours total — Outcome: outline complete
• Week 2: Write lead magnet content, create CTA copy, build form — 6 hours — Outcome: lead magnet draft ready
• Week 3: Design and proof, set up email sequence, test form — 6 hours — Outcome: landing page live in staging
• Week 4: Launch, promote to 1 channel, capture first 10 leads — 6 hours — Outcome: 10 leads

Common mistakes & fixes

• Overloading weeks — enforce weekly capacity and make A tasks only mandatory.
• Vague tasks — add estimated hours and a measurable outcome.
• Skipping review — commit to 15 minutes weekly to adapt.

7-day action plan

1. Day 1: Fill the prompt with your goal and run the AI.
2. Day 2: Review and pick Week 1’s A tasks. Block time in the calendar.
3. Day 3–6: Execute the blocks. Aim for 80% completion of planned tasks.
4. Day 7: 15-minute review and adjust Week 2.

Try the prompt now with a real goal. The faster you try it, the sooner you’ll have a practical weekly plan you can actually follow.

Yes — speed wins. Your 10-minute rule and the 48% reminder are spot on. Here’s how to make your follow-ups even clearer and more “doable” by humans and tools.

The upgrade: write actions in a tiny, repeatable grammar so AI drafts are crisp, team-friendly, and easy to track without rework.

The simple grammar (use this in your notes and prompts)

• Action: start with a strong verb + what + success criteria (if any).
• Owner: name a person. Add (A) for accountable, optional (C) for consulted.
• Due: a specific date (avoid “next week”).
• Status: New, In progress, Blocked.
• Note: optional 5–8 word hint or a single link.

Subject line formula (threads neatly): Project — Next Steps #[YYWW]-[MMDD] (3–6 actions)

What you’ll need

• Your 3–8 bullets rewritten in the “Action — Owner (A/C) — Due — Status — Note” format.
• Attendee list and one working doc link (if needed).
• An AI chat window and the copy-paste prompt below.
• A task tracker (spreadsheet or app) for logging owners and dates.

1. Capture (0–3 min): Right after the meeting, write atomic lines like “Draft launch banner (3 concepts approved) — Sarah (A) — Aug 1 — New — uses brand v2”.
2. Draft with AI (1–2 min): Paste your atomic bullets into the prompt below. Ask for subject, 3–6 action bullets with owner+deadline, one check-in, and one-sentence closing.
3. Review (1–2 min): Trim to ≤6 bullets, confirm names, clarify outcomes (what “done” means), remove jargon.
4. Add a tiny decision log (30 sec): 1–3 bullets: Decision — By — Date — Rationale (5 words).
5. Schedule (30 sec): Add the check-in to the calendar in the email body: “Check-in: Tue Aug 6, 10:00 AM — invite sent.”
6. Send & track (1 min): Email to attendees + stakeholders. Log each action (owner, due, status) in your tracker.
7. Smart reminders: Set two nudges: at 48% of time-to-deadline and on due date +1 day if no “done”.

Copy-paste AI prompt (refined)

“You are an assistant that turns atomic meeting bullets into a concise follow-up email. Use this format for actions: Action — Owner (A or C) — Due (MMM D) — Status — Note. Output: 1) a short subject using ‘Project — Next Steps #[YYWW]-[MMDD]’, 2) 3–6 action bullets exactly in that format (one owner per item, clear due date), 3) a tiny ‘Decisions’ section (1–3 bullets: Decision — By — Date — Rationale), 4) one check-in suggestion with date/time, 5) a one-sentence closing asking for corrections. Keep it professional, plain English, and under 8 short sentences overall. Meeting notes (atomic bullets): [PASTE HERE]”

Worked example

Raw notes:

• Approve Q3 marketing budget — finance to decide
• Homepage banner — Sarah to design 3 concepts
• Set launch date — target Sept 15

Atomic bullets:

• Confirm Q3 marketing budget — Finance Lead (A) — Aug 5 — New — aligns to plan
• Design homepage banner (3 concepts) — Sarah (A) — Aug 1 — New — uses brand v2
• Decide launch date (target Sept 15) — Product Manager (A) — Aug 3 — New — consider ops

AI-generated follow-up (example):

• Subject: Product Launch — Next Steps #2447-0801
• Actions:
• Confirm Q3 marketing budget — Finance Lead (A) — Aug 5 — New — aligns to plan
• Design homepage banner (3 concepts) — Sarah (A) — Aug 1 — In progress — uses brand v2
• Decide launch date (target Sept 15) — Product Manager (A) — Aug 3 — New — consider ops
• Decisions:
• Proceed with homepage refresh — By: Team — Date: Jul 25 — Rationale: improves CTR
• Check-in: Tue Aug 6, 10:00 AM (invite sent). Please update the doc by Aug 4.
• Closing: Reply with any corrections today so we can lock dates.

Bonus prompts you can keep

• Nudge prompt (48% to deadline): “Draft a polite 2‑sentence reminder to [Owner Name] about the action ‘[Action]’ due [Date]. Ask for a quick yes/no on being on track and request any blockers in one line. Keep it friendly and direct.”
• Slack/Teams summary: “Turn this follow-up email into a 4‑bullet Slack post with emojis removed, one owner per line, and the check-in date at the end. Keep each bullet under 14 words. Text: [PASTE EMAIL]”

Common mistakes & quick fixes

• Mixing decisions and actions: Split them. Actions drive work; decisions record context.
• Vague ‘done’: Add success criteria in brackets (e.g., “3 concepts approved”).
• Unclear dates/time zones: Use a calendar date (MMM D) and your local time.
• Group owners: Replace with a named person (A). Add (C) for key advisors.
• Too many bullets: Cap at 6; move the rest to the working doc.

30-minute setup plan

1. Create a one-page template with the atomic action format and subject formula.
2. Save the main AI prompt as a snippet in your AI tool.
3. Run it on your last meeting and send the follow-up within 10 minutes.
4. Add the two reminder prompts to your task/calendar system.
5. Track three metrics this week: time-to-send, 48‑hour acknowledgements, on-time completion.

Bottom line: Make your actions atomic, owners named, dates real, and AI becomes a speed boost you can trust. Try the prompt on your next meeting and hit send in under 10 minutes.

Good, practical question — you’re focused on outcomes, which is exactly the right place to start.

Quick win (under 5 minutes): pick one recent booking confirmation email, copy its text, paste this AI prompt (below) into a chat and ask for a one-line calendar event. You’ll have a usable event in seconds.

What you’ll need

• Your booking confirmation email (flight, hotel or train).
• An AI chat tool (e.g., ChatGPT) or AI assistant that can read/parse text.
• A calendar (Google, Outlook, Apple) and a method to add events quickly (copy/paste CSV or manual).
• Optional: simple automation like Zapier/Make to forward emails and parse attachments.

Step-by-step: a simple, reliable workflow

1. Collect: Create an email folder “Travel Confirmations” and move all booking emails there.
2. Extract: Open one confirmation, copy the important text (dates, times, confirmation numbers, hotel address, check-in/out times).
3. Parse with AI: Paste the text into the AI chat with the prompt below to get a clean, structured summary and a calendar-friendly line.
4. Create events: Copy the calendar line into your calendar or export as CSV for bulk import.
5. Build itinerary PDF: Ask the AI to assemble all parsed items into a single day-by-day itinerary with transport times and reservation numbers; save or print to PDF.
6. Automate (optional): Use an automation tool to forward new confirmations into the AI parser and auto-create calendar events and a shared itinerary link.

Example (what to expect)

After pasting an airline confirmation into the AI and using the prompt, you’ll get output like:

• Flight: JFK → LAX, 12 May 2025, Depart 10:00 ET, Arrive 13:30 PT, Confirmation: ABC123
• Calendar line: 2025-05-12, 10:00-13:30, Flight JFK→LAX, ABC123

Copy-paste AI prompt (use this)

Here is the booking confirmation email: [paste email text]. Extract these fields: type (flight/hotel/train), date(s), start time, end time (if known), timezone, confirmation number, address, check-in and check-out times. Provide:

1) A short one-line calendar event for each booking (date, start-end, title, short note). 2) A day-by-day itinerary summary (bullet list). 3) Any follow-up actions I should take (e.g., check-in, visa, seat selection). Keep it concise.

Mistakes people make — and how to fix them

• Relying fully on automatic parsing: always scan the AI output for timezone and date errors.
• Missing refunds/cancellation windows: have the AI list cancellation deadlines as a follow-up action.
• Not syncing companions’ plans: keep a shared calendar or itinerary file for everyone traveling.

Action plan — do this now

1. Move recent booking email into a “Travel Confirmations” folder.
2. Use the prompt above on one email and create a calendar event.
3. Repeat for all bookings this week and save the AI-generated itinerary PDF to your phone.

Reminder: AI speeds the work, but you’re the final check. Confirm times, time zones and required documents before you travel.