The final reminder email that goes out 24 to 48 hours before doors for a show that still has tickets and is worth one last push to the list. Real inventory, one clean ticket link, no manufactured urgency.
How to use it
Copy the SKILL.md below, paste it into a Claude chat, and tell Claude to remember it as a skill. Claude will save it and pull it in the next time you ask for a last-call email.
To make it match your venue, tell Claude the details it doesn't know yet: your venue name, your typical CTA wording, your sign-off, your at-the-door policy, anything your team does differently. Then ask Claude to update the skill with that information. The file will be tuned to how you actually write, without you ever opening a code editor.
Works best with: install the venue-voice-profile-builder first. This skill checks for the profile it produces and writes in your venue's voice when it finds one. Without it, Claude falls back to a generic event-marketing voice.
Once it's saved, trigger it by telling Claude "use the last call email skill" and pasting the show details with a real remaining-ticket count. Do not use it for sold-out comms, the mid-cycle reminder, the logistics email, or the morning-after recap. Those have their own skills.
---
name: last-call-email
description: Draft the final reminder email that goes out 24 to 48 hours before doors for a show that still has tickets and is worth a last push to the list. Cover real remaining inventory, a clean ticket link, and a clear close. Trigger whenever an operator says "write the last-call", "draft the final push", "the [artist] show is tomorrow, can you write the email", "we have [N] tickets left", or pastes a remaining-ticket count and asks for an urgency email. Also trigger when they say "we're not sold out, can we send one more". This skill is the closer in the announce cycle. Use it the day before or the day of the show, after the logistics email has gone out. Do not use it for sold-out comms (use `sold-out-waitlist-email`), the mid-cycle reminder (use `pre-sale-reminder-email`), or any send earlier than 48 hours before doors.
---
# Last call email
## What this skill does
This skill writes the final reminder email that goes to the venue's list 24 to 48 hours before doors. It runs only when the show still has tickets and the venue wants one more push. The job is to give the small slice of the list that is still on the fence a real reason to act now, with honest inventory, a clean ticket link, and no manufactured urgency.
This is the shortest email in the cycle. It is not a re-announce. It is not a thank-you to people who already bought. It is a closer.
## When to trigger
Trigger when an operator says the show is in the next day or two and they want one more send to move tickets. Trigger on phrasings like "write the last-call", "final push email", "we still have [N] tickets, can we send one more", or when the operator pastes a remaining-ticket count and asks for copy.
Do not trigger for sold-out comms (use sold-out-waitlist-email), the mid-cycle reminder (use pre-sale-reminder-email), the logistics email (use before-you-go-logistics-email), or the morning-after recap (use post-show-recap-email).
## Required inputs
Last-call emails live or die on whether the scarcity is real. Ask for these before drafting if anything is missing.
Artist name and show date. Day of week is helpful so the email can say "tomorrow" or "Friday".
Real remaining inventory. A number or a tight range. "About 40 tickets left" is fine. "A few left" is fine if it is actually true. Do not draft a last-call without the operator confirming the count.
Final online on-sale cutoff. The time and day the website stops selling. This matters because the email's CTA is asking people to act before that cutoff.
Ticket link. Single primary CTA.
At-the-door policy. If tickets will still be available at the door after online sales close, the email should say "last chance to lock in your ticket online", not "last chance to get tickets". The distinction protects the list's trust.
Anything the operator wants flagged: a guest support act announced late, a tour-finale framing if true, a return to the city after a long gap. Real anchors only.
## Voice
Read the venue voice profile if one exists. Last-call emails are urgency-leaning but the urgency has to feel like a host pointing at the clock, not a marketing department running a sale.
Default Backstage operator voice if no profile exists: direct, honest about the inventory, warm without being chummy. The reader should feel like the venue is doing them a favor by reminding them, not pressuring them into a purchase.
Hard voice rules:
No em-dashes. Use commas, semicolons, or periods.
No fragment chains. The temptation to write "Tomorrow. Doors at 8. Last tickets." is real. Resist it. Use complete sentences with rhythm.
No fabricated scarcity. If the operator did not give you a number, do not write "only a few left". If the show is not actually close to selling out, do not write "tickets going fast". The list will catch it once and stop trusting last-call emails forever.
No hype superlatives. "Don't miss out", "the show of the year", "you'll regret missing this" are out. The job is information, delivered with warmth.
No countdown theatrics. Subject lines with rocket emojis, all-caps urgency, or "FINAL HOURS" framing are out unless the venue voice profile explicitly uses that register.
## Structure
Always draft in this order.
Subject line. One option. Default pattern: a clean line that names the show and the urgency in plain language, e.g. "[Artist] tomorrow at [Venue]" or "Last tickets for [Artist], [Day]". Under 55 characters. No all caps unless the venue voice profile uses them. No emoji unless the venue voice profile uses them.
Preheader. One sentence, twelve to eighteen words. Use it to add the single most useful detail the subject line did not have, often the inventory count or the support act.
Opener. One sentence. Name the show and when it is. If the inventory is genuinely tight, name it in the same sentence or the next one. Do not bury it.
The fact. One short paragraph, two sentences at most. The remaining-ticket count or the honest framing the operator gave you. The online cutoff time if it matters. The reader needs to know exactly what is true and exactly what they need to do.
CTA. A single primary button or link with the ticket URL. CTA copy is short. Default fallbacks if no profile: "Grab a ticket" or "Get yours". Do not stack multiple CTAs.
Close. One line. Optional sign-off if the venue voice profile uses one.
## Length cap
Body copy, opener through close, sits at about 60 words. This is the shortest email in the cycle. Anything past 90 words is too long for a last-call and should be cut.
## Common failure modes to avoid
Faking scarcity. The most damaging failure mode. If the operator did not give you a real count, do not write a scarcity line. Ask for the count before drafting.
Writing "last chance" when there will be tickets at the door. The list will be at the door tomorrow. If they see tickets available, the next last-call email will get ignored.
Treating the email like a second announce. The reader already knows the show is happening. Do not re-introduce the artist with two paragraphs of context. The email opens on the urgency, not the announcement.
Stacking CTAs. One ticket link. Not "buy now" plus "see the lineup" plus "view directions". The reader is one click away from converting. Do not give them somewhere else to go.
Manufactured countdown language. "Only 6 hours left" is fine if it is true and useful. "Time is running out, act now" is filler that signals the venue does not have anything real to say.
Forgetting the support act. If a support act was announced late or if the lineup matters, naming the support in the preheader or the fact is often the single most useful inventory-moving detail. Use it if the operator gave it to you.
## What to deliver
Return:
Subject line (one).
Preheader (one).
Email body, ready to paste into the send tool.
CTA copy and the destination URL.
If the operator could not give a real ticket count, do not draft. Reply asking for one. If anything else in the inputs was missing or ambiguous, name what is missing in two or three sentences at the end. Do not list every word swap or stylistic choice.
.svg "backstage logo 1 (3)")
