--- title: Backstage - Tools description: AI skill that drafts the morning-after recap email to ticketholders and the list. Opens with a real moment from the show, hooks to what's next. --- [Skip to content](https://backstage.hive.co/tools/agent-skills/post-show-recap-email#main-content) [![Backstage with Hive.co](https://backstage.hive.co/hs-fs/hubfs/bckwhive.png?width=170&height=47&name=bckwhive.png "Backstage with Hive.co")](https://backstage.hive.co/?hsLang=en-us) - [Tools](https://backstage.hive.co/tools?hsLang=en-us) - [Articles](https://backstage.hive.co/articles?hsLang=en-us) - [Community](https://backstage.hive.co/community?hsLang=en-us) - [Video](https://www.youtube.com/playlist?list=PLOTOWwzYFQr088c8WVspPzbPm4xX8RN2q) - [Dispatch](https://backstage.hive.co/dispatch?hsLang=en-us) # Post-show recap email by Hive Backstage The morning-after recap email to attendees and the venue's full list, opening with a real moment from the show and hooking to what is next on the calendar. ## What this skill does Writes the morning-after email to ticketholders and the full list. Two jobs: reward the people who were in the room by capturing the night honestly, and pull the people who were not into the next show on the calendar without making the email feel like a sales pivot. Recap is the most voice-sensitive email in the cycle, so it leans heavily on the venue voice profile when one exists. ## 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 recap 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, the kind of moments your room cares about, 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](https://backstage.hive.co/tools/agent-skills/venue-voice-profile-builder?hsLang=en-us) 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 post-show recap email skill" and pasting at least one real moment from the night plus the next show on your calendar. Do not use it for social captions, longer recap blog content, or logistics emails. Those have their own skills. SKILL.md Copy ``` --- name: post-show-recap-email description: Draft the morning-after recap email to attendees and the venue's full list, opening with a real moment from the show and hooking to what is next on the calendar. Trigger whenever an operator says "write the recap", "draft the post-show email", "the [artist] show was last night, can you write the email", or pastes setlist notes, crowd notes, or post-show observations and asks for a list email. Also trigger when they share a Granola or notes doc from the night and want it turned into a recap. This skill is the back half of the show cycle. Use it the morning after a show closes, before the next announce email runs. Do not use it for social captions (use `post-show-social-pack`) or longer-form blog content (use `recap-blog-opener`). --- # Post-show recap email ## What this skill does This skill writes the email that goes out the morning after a show, to ticketholders and the full list. The job is twofold. Reward the people who were in the room by capturing the night honestly, and pull the people who were not into the next show on the calendar without making the email feel like a sales pivot. The recap email is the most voice-sensitive email in the cycle. Get it right and the list trusts every announce email that follows. Get it wrong and the list reads marketing copy and tunes out. The skill leans heavily on the venue voice profile. ## When to trigger Trigger when an operator says a show happened last night and they need the recap email out. Trigger on phrasings like "write the recap", "post-show email", "the [artist] show was great, can you do the email", or when they paste notes from the night, a setlist, or quick crowd observations and ask for copy. Do not trigger this skill if the operator is asking for a social caption (use post-show-social-pack), a longer recap blog (use recap-blog-opener), or a logistics email (use before-you-go-logistics-email). This skill is the email only. ## Required inputs The recap email needs real, specific inputs from the night. Without them the email will read generic and the skill will produce a worse version than the operator could write in five minutes. If the inputs are missing, ask once. Artist name and show date. Confirm spelling. One or two real moments from the night. Examples of what counts: the song that got the loudest reaction, a moment the artist talked to the crowd, a guest appearance, a stretch where the room felt locked in, a quiet song that landed, weather that made it memorable for an outdoor show, a story from the support act, anything the operator actually noticed. Setlist context is welcome. Specifics are non-negotiable. Next show on the calendar. Artist, date, and ticket link. This is the soft CTA at the end. If there is no next show booked, ask the operator what they want the close to do instead (signup for the list, follow on socials, etc). Optional: a real quote from the artist or a fan if the operator captured one. Pull-quote style works well in recap emails. Hard rule: if the operator cannot offer at least one real moment, do not draft. Reply asking for one. Recap emails written from nothing read like every other recap email, which is what kills them. Do not invent a moment to add color. ## Voice Read the venue voice profile if one exists. Recap emails are where voice matters most because the email is reflective and observational, not transactional. Default Backstage operator voice if no profile exists: warm, observational, in-the-room. The writer was there, or close enough to it that they know what landed. Avoid sounding like a press release. Avoid sounding like a friend who is trying too hard. The bar is "warm host who saw the show". Hard voice rules: No em-dashes. Use commas, semicolons, or periods. No fragment chains. Use complete sentences with rhythm. No fabricated specifics. If the operator did not give you the moment, do not invent the moment. This rule matters more here than in any other email in the cycle. No "thank you for an unforgettable night" sign-offs. They are filler. If the night was special, the body of the email is doing that work. No selling. The next-show mention at the end is informational, not a sales pitch. The reader has just been thanked. Do not flip into close-mode. ## Structure Always draft in this order. Subject line. One option. Default patterns: a line from the night ("Goldlink closed with The Parable"), a feeling about the room ("Last night was a long one"), or a simple anchor ("[Artist] at [Venue], last night"). Under 55 characters. No all caps unless the venue voice profile uses them. No "thanks" subject lines. Preheader. One sentence. Use it to set the scene or quote a moment. Twelve to eighteen words. Scene-opener. The first two to three sentences put the reader in the room. Lead with the specific moment the operator gave you. Not "what a night". Not "we had a blast". The specific. Reflection. One short paragraph, two or three sentences. What the night felt like, why this artist mattered, what the room did. If the operator gave you a quote from the night, this is where it goes, set on its own line. Nod to next. One short paragraph, two to three sentences. Name the next show. Tie it loosely to the recap if you can (same kind of room, same kind of crowd, returning artist) but do not force it. If the link is weak, just name the next show cleanly. Soft CTA. Single primary link to the next show, or whatever the operator chose if there is no next show booked. CTA copy should match the venue voice. Default fallback: "See what's next" or "Next on the calendar". Close. One line. Optional sign-off if the venue voice profile uses one. ## Length cap Body copy sits at about 150 words. Recap emails earn a little more room than announce emails because the job is reflective, but anything past 180 starts to drag. ## Common failure modes to avoid Opening with "what a night". This is the most predictable recap opener possible. Cut it. Open with the specific moment. Listing every song the artist played. The recap is not a setlist. Pick one or two moments. The setlist is a social caption job. Pivoting hard to the next show. The transition from recap to next-show should feel like a host pointing at the calendar, not a salesperson closing. If it reads like a CTA, rewrite it. Generic gratitude language. "Thank you to everyone who came out" tells the reader nothing. If you are going to thank the room, thank them for something specific. Treating the support act as an afterthought. If the support act delivered, name them and what they did. The list will remember. ## What to deliver Return: Subject line (one). Preheader (one). Email body, ready to paste, with quotes set on their own line if used. CTA copy and the destination URL for the next show, or the alternate close the operator requested. If you had to ask for missing inputs to draft, name what you used and what is still thin in two or three sentences at the end. Do not walk through every word choice. ``` New to running Claude as part of your event marketing stack? Read [how to use Claude as an event marketer](https://backstage.hive.co/backstage-articles/introducing-agent-skills-for-event-marketers?hsLang=en-us) first. --- name: post-show-recap-email description: Draft the morning-after recap email to attendees and the venue's full list, opening with a real moment from the show and hooking to what is next on the calendar. Trigger whenever an operator says "write the recap", "draft the post-show email", "the \[artist\] show was last night, can you write the email", or pastes setlist notes, crowd notes, or post-show observations and asks for a list email. Also trigger when they share a Granola or notes doc from the night and want it turned into a recap. This skill is the back half of the show cycle. Use it the morning after a show closes, before the next announce email runs. Do not use it for social captions (use \`post-show-social-pack\`) or longer-form blog content (use \`recap-blog-opener\`). --- # Post-show recap email ## What this skill does This skill writes the email that goes out the morning after a show, to ticketholders and the full list. The job is twofold. Reward the people who were in the room by capturing the night honestly, and pull the people who were not into the next show on the calendar without making the email feel like a sales pivot. The recap email is the most voice-sensitive email in the cycle. Get it right and the list trusts every announce email that follows. Get it wrong and the list reads marketing copy and tunes out. The skill leans heavily on the venue voice profile. ## When to trigger Trigger when an operator says a show happened last night and they need the recap email out. Trigger on phrasings like "write the recap", "post-show email", "the \[artist\] show was great, can you do the email", or when they paste notes from the night, a setlist, or quick crowd observations and ask for copy. Do not trigger this skill if the operator is asking for a social caption (use \`post-show-social-pack\`), a longer recap blog (use \`recap-blog-opener\`), or a logistics email (use \`before-you-go-logistics-email\`). This skill is the email only. ## Required inputs The recap email needs real, specific inputs from the night. Without them the email will read generic and the skill will produce a worse version than the operator could write in five minutes. If the inputs are missing, ask once. Artist name and show date. Confirm spelling. One or two real moments from the night. Examples of what counts: the song that got the loudest reaction, a moment the artist talked to the crowd, a guest appearance, a stretch where the room felt locked in, a quiet song that landed, weather that made it memorable for an outdoor show, a story from the support act, anything the operator actually noticed. Setlist context is welcome. Specifics are non-negotiable. Next show on the calendar. Artist, date, and ticket link. This is the soft CTA at the end. If there is no next show booked, ask the operator what they want the close to do instead (signup for the list, follow on socials, etc). Optional: a real quote from the artist or a fan if the operator captured one. Pull-quote style works well in recap emails. Hard rule: if the operator cannot offer at least one real moment, do not draft. Reply asking for one. Recap emails written from nothing read like every other recap email, which is what kills them. Do not invent a moment to add color. ## Voice Read the venue voice profile if one exists. Recap emails are where voice matters most because the email is reflective and observational, not transactional. Default Backstage operator voice if no profile exists: warm, observational, in-the-room. The writer was there, or close enough to it that they know what landed. Avoid sounding like a press release. Avoid sounding like a friend who is trying too hard. The bar is "warm host who saw the show". Hard voice rules: No em-dashes. Use commas, semicolons, or periods. No fragment chains. Use complete sentences with rhythm. No fabricated specifics. If the operator did not give you the moment, do not invent the moment. This rule matters more here than in any other email in the cycle. No "thank you for an unforgettable night" sign-offs. They are filler. If the night was special, the body of the email is doing that work. No selling. The next-show mention at the end is informational, not a sales pitch. The reader has just been thanked. Do not flip into close-mode. ## Structure Always draft in this order. Subject line. One option. Default patterns: a line from the night ("Goldlink closed with The Parable"), a feeling about the room ("Last night was a long one"), or a simple anchor ("\[Artist\] at \[Venue\], last night"). Under 55 characters. No all caps unless the venue voice profile uses them. No "thanks" subject lines. Preheader. One sentence. Use it to set the scene or quote a moment. Twelve to eighteen words. Scene-opener. The first two to three sentences put the reader in the room. Lead with the specific moment the operator gave you. Not "what a night". Not "we had a blast". The specific. Reflection. One short paragraph, two or three sentences. What the night felt like, why this artist mattered, what the room did. If the operator gave you a quote from the night, this is where it goes, set on its own line. Nod to next. One short paragraph, two to three sentences. Name the next show. Tie it loosely to the recap if you can (same kind of room, same kind of crowd, returning artist) but do not force it. If the link is weak, just name the next show cleanly. Soft CTA. Single primary link to the next show, or whatever the operator chose if there is no next show booked. CTA copy should match the venue voice. Default fallback: "See what's next" or "Next on the calendar". Close. One line. Optional sign-off if the venue voice profile uses one. ## Length cap Body copy sits at about 150 words. Recap emails earn a little more room than announce emails because the job is reflective, but anything past 180 starts to drag. ## Common failure modes to avoid Opening with "what a night". This is the most predictable recap opener possible. Cut it. Open with the specific moment. Listing every song the artist played. The recap is not a setlist. Pick one or two moments. The setlist is a social caption job. Pivoting hard to the next show. The transition from recap to next-show should feel like a host pointing at the calendar, not a salesperson closing. If it reads like a CTA, rewrite it. Generic gratitude language. "Thank you to everyone who came out" tells the reader nothing. If you are going to thank the room, thank them for something specific. Treating the support act as an afterthought. If the support act delivered, name them and what they did. The list will remember. ## What to deliver Return: Subject line (one). Preheader (one). Email body, ready to paste, with quotes set on their own line if used. CTA copy and the destination URL for the next show, or the alternate close the operator requested. If you had to ask for missing inputs to draft, name what you used and what is still thin in two or three sentences at the end. Do not walk through every word choice. ### More Backstage skills [Pre-show Announcement Email by Hive Backstage Drafts the first email to the list when a show goes on-sale. Voice rules, required elements (artist, date, doors, presale code), length cap, structure.](https://backstage.hive.co/tools/agent-skills/pre-show-announcement-email?hsLang=en-us) [Before You Go: Logistics Email by Hive Backstage Logistics email in the week leading up to the show. Doors, set time, parking, age policy, what to bring.](https://backstage.hive.co/tools/agent-skills/before-you-go-logistics-email?hsLang=en-us) [Audience Segmentation Brief by Hive Backstage Given a show and artist, returns ranked segment criteria for a dedicated email send. First-party plus behavioral plus recency plus exclusions. Hand-off doc for the CRM operator.](https://backstage.hive.co/tools/agent-skills/audience-segmentation-brief?hsLang=en-us) [Venue Voice Profile Builder by Hive Backstage Reads 5 to 10 examples of a venue's strongest past content (announcements, recaps, social) and writes a venue-specific voice profile. Foundation skill.](https://backstage.hive.co/tools/agent-skills/venue-voice-profile-builder?hsLang=en-us) [Last Call Email by Hive Backstage Final reminder 24 to 48 hours before doors. Scarcity-driven, short, includes any remaining ticket info.](https://backstage.hive.co/tools/agent-skills/last-call-email?hsLang=en-us) [Tools](https://backstage.hive.co/tools?hsLang=en-us) [Articles](https://backstage.hive.co/articles?hsLang=en-us) [Community](https://backstage.hive.co/community?hsLang=en-us) [Video](https://www.youtube.com/playlist?list=PLOTOWwzYFQr088c8WVspPzbPm4xX8RN2q) [Dispatch](https://backstage.hive.co/dispatch?hsLang=en-us)   --- ##### Built by the team at [Hive.co](http://hive.co) ![backstage logo 1 (3)](https://backstage.hive.co/hubfs/backstage%20logo%201%20(3).svg "backstage logo 1 (3)") ![backstage logo 1 (3)](https://backstage.hive.co/hubfs/backstage%20logo%201%20(3).svg "backstage logo 1 (3)") ## FEATURED TOOLS ##### Jump in and start experimenting ![calculate](https://backstage.hive.co/hubfs/calculate.png) ### Project management Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso. ![calculate](https://backstage.hive.co/hubfs/calculate.png) ### Project management Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso. ![calculate](https://backstage.hive.co/hubfs/calculate.png) ### Project management Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso. © 2026 Hive. Experimental tools for live event marketers. ![mic-3-yellow-brown](https://backstage.hive.co/hubfs/mic-3-yellow-brown.gif "mic-3-yellow-brown") ## The Ultimate Claude Setup Guide for the Music Industry A comprehensive walkthrough for live event marketers who want to leverage Claude AI for campaign planning, copywriting, and data analysis. Includes prompts, workflows, and real-world examples from touring professionals. [Sign up for early access](https://backstage.hive.co/tools/agent-skills/post-show-recap-email#link) [![Hive Black Logo svg](https://backstage.hive.co/hubfs/Hive%20Black%20Logo%20svg.svg "Hive Black Logo svg")](https://www.hive.co) ```json { "@context" : "https://schema.org", "@id" : "https://www.hive.co/#organization", "@type" : "Organization", "description" : "Hive is an event marketing platform that helps promoters, venues, and festivals automate campaigns, engage fans, and sell more tickets.", "logo" : { "@type" : "ImageObject", "url" : "https://cdn.prod.website-files.com/60a44fa06f0feb314d1ad896/65aa7f0d8749d56b4f00d55a_FrameHive.svg" }, "name" : "Hive", "sameAs" : [ "https://www.linkedin.com/company/hive-co" ], "url" : "https://www.hive.co/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://backstage.hive.co/#website", "@type" : "WebSite", "description" : "Tools and resources from Hive to help event professionals streamline marketing workflows and improve event promotion.", "inLanguage" : "en", "name" : "Hive Backstage", "publisher" : { "@id" : "https://www.hive.co/#organization" }, "url" : "https://backstage.hive.co/" } ```