iMessage for wedding planners

A wedding planner is running a long project with a fixed end date, a dozen suppliers, and clients whose emotional investment is total. The messaging job is not coordination — a spreadsheet does coordination. It is making a large, expensive, unrepeatable thing feel under control.

Separate the couple's thread from the vendor threads

The single most common mistake is running everything through one channel. Couples should not see the florist's delivery problem or the caterer chasing final numbers — that is exactly what they are paying you to absorb.

The countdown is the product

export const planning = {
  // Monthly, calm, and specific about what is needed from them.
  monthly: (c: Ctx) =>
    `${c.planner}: ${c.monthsOut} months out. Done this month: ` +
    `${c.completed}. Next up: ${c.upcoming}. ` +
    `From you I need ${c.clientAction} by ${c.clientDeadline}.`,
 
  // The week-of message people remember for years.
  weekOf: (c: Ctx) =>
    `${c.planner}: it's this week. Everything is confirmed — ` +
    `${c.vendorCount} suppliers, all briefed, timeline attached. ` +
    `Your only job now is to enjoy it. I'll handle the rest.`,
 
  dayOf: (c: Ctx) =>
    `Morning. Everything's on schedule. ${c.firstMilestone} at ` +
    `${c.time}. I'm on ${c.phone} all day — but you shouldn't need me.`,
};

That week-of message is doing something no spreadsheet can. The couple has spent a year worrying; being told plainly that it is handled is the thing they will remember about working with you.

Day-of coordination

On the day itself, a vendor group thread beats a dozen phone calls — everyone sees a delay at once and adjusts without you repeating yourself. Open it a week before, use it for timings only, and close it afterwards.

And keep the couple out of it. On the day especially, their thread should contain nothing but reassurance.