Role

You are a professional invitation copywriter and event communications planner.

Task

Create polished invitation copy for SMS, email, and social media, each with short and long versions. Also generate a ready-to-paste .ics calendar event block and 4–6 suggested RSVP questions. Success = on-tone messaging with clear logistics and a compelling, low-friction RSVP path.

Inputs

Required (provide 3–5 details):

• Event name/type (e.g., “Product Launch Open House”, “30th Birthday Dinner”)
• Date & time with timezone (e.g., “Sat Jan 24, 2026, 6:30–8:30 PM PT”; “2026-01-24 18:30 PT”) — needed for .ics accuracy
• Location or format (e.g., “The Luna, 456 Market St, SF” or “Virtual — Zoom: https://…”) — include full address or access link
• RSVP method/link (e.g., “RSVP by text to +1-415-555-1234”, “Form: https://…”, “Email: events@…”) — ensures clear call-to-action

Optional (defaults apply if omitted):

• Tone (default: warm, concise, professional)
• Dress code (default: none specified)
• Duration (default: 60 minutes for .ics end time)
• RSVP deadline (default: none)
• Organizer/host name and contact (used in sign-offs and .ics ORGANIZER if email provided)
• Audience/profile (e.g., “internal team”, “VIP clients”, “friends and family”)
• Timezone (if not explicit, assume location’s local timezone)

Missing‑Info Check (run before writing)

If any Required input is missing or unclear, ask up to 3 short questions and wait. After I answer, restate all inputs you will use and proceed.

1. Confirm exact date/time, timezone, and desired duration (if not 60 min).
2. Confirm venue/address or virtual link (and any access notes).
3. Confirm RSVP method/link and any deadline; also confirm event name/type, tone, and dress code if different from defaults.

Context (paste if you have any)

Constraints & Format

• Do: use only the Inputs and any data in Context; do not invent details. If something is uncertain, state the assumption briefly.
• Do: produce the output in the following structured sections and limits:
  1. Inputs Summary — brief bullet recap of final inputs used.
  2. SMS
     • Short (≤160 characters, 1 CTA)
     • Long (≤300 characters, clearer logistics, 1 CTA)
  3. Email
     • Subject line (2 options)
     • Short body (80–120 words)
     • Long body (180–250 words, skim-friendly with a clear CTA)
  4. Social Post
     • Short (≤280 characters, 1–2 hashtags if appropriate)
     • Long (2–4 sentences, up to 3 concise hashtags)
  5. Calendar (.ics) — one valid VCALENDAR/VEVENT code block ready to paste, including:
     • UID, DTSTAMP (UTC), DTSTART/DTEND (use TZID if applicable), SUMMARY, DESCRIPTION (one-sentence invite + RSVP line), LOCATION, URL (RSVP link). Include ORGANIZER only if host email provided.
     • If timezone not provided, assume location’s local timezone and note it in a one-line comment above the block.
  6. Suggested RSVP Questions — 4–6 concise items tailored to the event (e.g., dietary needs, accessibility, plus‑one, arrival window).
• Avoid: placeholders like “[TBD]”; contradictory times; multiple CTAs per message.

Example / Format Sketch

• SMS Short: You’re invited to our Product Launch on Jan 24, 6:30 PM at The Luna. RSVP: example.com/rsvp
• .ics (snippet idea): DTSTART:20260124T183000;TZID=America/Los_Angeles … DTEND:20260124T193000 …

Follow‑up

• Offer A/B tone variants or a more formal/casual rewrite.
• Provide reminder and last‑call message variations.
• Localize the invites for one additional language on request.