ChatGPT prompts that actually get UK musicians booked12 prompts we’ve used or watched real artists use to win venue replies, write press kits and plan tours — copy, paste, edit.

Used right, ChatGPT is the fastest way to clear the writing pile that sits between a gigging musician and the inbox of a booker. Used wrong, it makes you sound like every other unsolicited email a venue ignores. Below: 12 prompts, all field-tested on real UK venues, real festival applications and real artist EPKs — with the editing rules that turn AI output into something a booker will actually read.

What ChatGPT actually does well for gigging musicians

ChatGPT helps gigging musicians by drafting venue emails, press releases, EPK bios, setlists and Spotify pitches in seconds — but only when given a structured prompt with a role, constraints, your variables, an output shape, and a list of phrases to avoid. Without those five parts, the output is generic and obvious.

It’s strongest at repeat-format writing: the 50 venue cold emails, the 12 festival applications, the EPK bio you’ll need in 50, 150 and 300-word versions. These are the tasks that swallow a working musician’s evenings. ChatGPT compresses them — provided you bring the inputs (your draw numbers, recent venues played, fee floor, EPK URL) and you edit before sending.

It’s also useful as a second pair of eyes: paste your existing pitch in, ask it to make it 30% shorter without losing specifics, ask it to flag clichés. Half the value is the rewrite, half is the audit.

What it gets wrong (and how we know)

We test every prompt below on real UK gig data — the rate floors come from the GX rate calculator, the venues come from our directory of 11,000+ live UK gigs, the email patterns come from our venue outreach tool. That gives us a clean before/after on what AI gets wrong.

The recurring failures:

• American defaults. Ask for an email to a UK venue and you’ll get “rocking the stage”, “crushing it”, “next big thing”. UK bookers read those as red flags. You have to forbid them in the prompt.
• Invented venues. Ask for a tour route through Yorkshire and ChatGPT will confidently list pubs that don’t exist or closed in 2019. Always verify against a real source — our directory or a Google Maps search.
• Hallucinated fees. ChatGPT will tell you a covers band in a Manchester pub gets £600 a night. Sometimes true, often not. Anchor every fee claim with our UK gig pay data.
• One ask becomes three. Without word-count and one-ask constraints, ChatGPT writes 280-word emails asking for a support slot, headline slot, residency, and follow-up call all at once. That email gets binned.
• Generic everything. Without a forbidden-phrases list, every output sounds the same. The forbidden-phrases line is the single biggest quality lever in any prompt.

Now the prompts. Each one assumes you’ll fill in the {curly braces} with your real details before hitting send.

Cold venue outreach email

Use when: you’re emailing a booker who’s never heard of you, asking for a slot.

You are a UK gig-booking copywriter. Use only supplied facts; mark any
missing fact as [NEEDS FACT]. Write a 120-word email from {artist_name},
a {genre} act based in {city}, to {venue_name}'s booker. We're available
on {date_range} and want a {support | headline | residency} slot. Local
draw: {mailing_list_size} subscribers / {avg_door} average door.
EPK: {epk_url}. Venue-fit fact (specific recent line-up or reason this
venue fits): {venue_fit_fact}. If blank, write [NEEDS FACT: venue-fit
reason] and do not invent one. Tone: friendly, specific, one ask only.
Subject line first, then body. UK formatting (£, DD Month YYYY, 24h
times, British spelling). No clichés ("rocking the stage", "next big
thing", "absolute pleasure", "hope this finds you well").

Why this works: the role + word cap + one-ask rule + forbidden-phrases list together force ChatGPT off its default behaviour (long, generic, multi-ask, American). The local-draw line is the credibility lever — bookers care about whether you’ll bring people, not how passionate you are.

Where it still fails: it doesn’t know the venue’s programming. If they’re a folk-only listening room and you’re a metal trio, no prompt saves you. Read the venue’s recent line-ups before sending. Faster route: skip the prompt and use our free venue outreach templates — they ship pre-written for six different ask types.

Festival application pitch

Use when: you’re submitting via a festival’s online form or to their bookings email.

You are a UK festival-application copywriter. Use only supplied facts;
mark missing facts as [NEEDS FACT]. Do not invent awards, press, audience
size or past festival slots. Write a 250-word festival application for
{festival_name} from {artist_name}, a {genre} act. Festival theme/criteria:
{festival_criteria}. Recent venues: {recent_venues_3}. Streaming:
{monthly_listeners} monthly. Band size: {band_size}. Set length:
{set_length_minutes} minutes. Tech needs summary: {tech_needs_summary}.
Availability dates: {availability_dates}. Rider summary (2 lines max):
{rider_summary}. Stage preference: {stage_name}. Slot:
{opener | mid | headline}. Structure: 1-line hook, fit with festival,
strongest supplied credibility signal (or [NEEDS FACT: credible proof
point] if none supplied), live setup (band size, set length, tech
needs), availability + rider summary in 2 lines. Target outlet/recipient
type: {festival_team_or_curator}. UK formatting (£, DD Month YYYY,
"licence"). British English. No hype clichés ("rising stars",
"explosive", "next big thing").

Why this works: festivals get hundreds of applications. “Lead with the strongest credibility signal” forces ChatGPT to put your best line first — the recent venue, the streaming figure, the press hit — rather than burying it after a paragraph of self-introduction.

Spotify playlist curator outreach

Use when: you’re pitching a track to an editorial or independent curator.

You are a UK independent-artist outreach writer. Use only supplied facts;
mark missing required facts as [NEEDS FACT]. Write outreach to a Spotify
curator at {playlist_name}. Pitch "{track_name}" by {artist_name}, a
{genre} act. Mood/sound: {3 adjectives}. For-fans-of: {3 reference acts}.
Release date: {date}. Pre-save: {url}. Direct listen / private stream
link for the curator: {private_listen_url}.
Recent track they added that genuinely fits us: {recent_playlist_add}.
If {recent_playlist_add} is blank, omit the personalised line rather
than inventing one. One ask: "would you consider it for {playlist_name}?".
Output: subject line, 90-word email, 40-word DM variant. British English,
UK formatting. No "perfect fit", "vibe", "would mean the world".

Why this works: curators get spammed daily. The 90-word cap and the “one specific line about a track they recently added” clause force genuine research. If you can’t name a track they recently added, you’re not ready to pitch them.

Press release for a single, EP or tour

Use when: you’re sending to UK music press, podcasts, or playlisting blogs.

You are a UK music-publicist copywriter. Use only the facts below; mark
missing facts as [NEEDS FACT]. Do not invent press hits, dates or quote
wording. Write a UK music press release for {single | EP | tour} by
{artist_name}. Hook: {one_line_news}. Release/tour date(s): {dates}.
Location(s): {locations}. Confirmed quote (exact wording, 1-2 sentences):
{exact_quote}. Press kit: {press_kit_url}. Target outlet/recipient type:
{specific_publication_or_blog_or_radio_show}. Adapt the register to that
outlet without copying its wording. Word count 280-320. Register:
factual UK music-publicist style, not advertorial. Output: headline,
subheading, release body, quote, notes to editors, contact line. UK
formatting (£, DD Month YYYY, "licence"). No exclamation marks, no
"frontman/frontwoman", no "rising star", no "explosive".

Why this works: naming the target style (BBC / DIY / Clash) gives ChatGPT a register to imitate. The exclamation-mark ban kills the press-release-as-marketing-flier energy that gets these binned by music journalists in three seconds.

Where it still fails: ChatGPT will sometimes invent press hits or tour dates. Always proof every factual claim before sending.

EPK bio (3 lengths)

Use when: you’re building or refreshing your musician profile, EPK, or website.

You are a UK independent-artist bio writer. Use only supplied facts; mark
missing facts as [NEEDS FACT] and inferences as [INFERRED]. Write three
bios for {artist_name}, a {genre} act from {city}: 50, 150, 300 words.
Sharp identity line (one sentence on what makes you distinctive):
{distinctive_line}. Highlights: {achievements_3_to_5}. Sound:
{3 adjectives}. For-fans-of: {3 reference acts}. End each bio with one
specific upcoming {date_or_release} OR omit the upcoming line if blank.
Do not turn reference acts into
claims about influence unless explicitly supplied. Keep every claim
traceable to the supplied highlights, sound adjectives or distinctive
line. UK formatting (£, DD Month YYYY). British English. No "rising
star", "explosive sound", "carving out a unique sound", "next big
thing".

Why this works: you need three lengths because Spotify, your website, your EPK and your festival-application form all want different word counts. Generating them in one pass keeps them consistent. Pin the output and reuse for a year.

Setlist planner

Use when: you’re building a set for a specific room, length and audience.

You are a UK gigging-musician setlist editor. Use only songs in the
supplied list — do not add covers, originals or songs not listed. Build
a {45 | 60 | 90}-minute setlist for {artist_name}, a {genre} act playing
{pub | theatre | festival | wedding} on {date}. Songs available with
runtime, key, BPM, energy (low/mid/high), type (up-tempo/ballad/cover/
original): {paste_song_list}. Banter/changeover buffer to subtract from
total set length: {buffer_minutes} minutes. Crowd: {description}. Strongest
closer candidates: {song_titles_or_blank}. If blank, mark [NEEDS FACT:
strongest closer] and choose the best runtime/tempo fit only. Open with
{up | mid}-tempo, peak at 40-60% in, ballad at 70% if a low-energy song
is supplied (otherwise drop to the lowest-energy supplied song at the
70% mark and note [NO BALLAD SUPPLIED]), close strongest of the
supplied options.
Output: ordered table with song, key, BPM, runtime, transition note.
Calculate total runtime and show remaining / over time. If the requested
set length is impossible with the supplied songs, propose the closest
viable set and explain the gap in one line.

Why this works: ChatGPT can’t pick your strongest song — you have to tell it — but it’s good at sequencing once you give it the rules. The “ordered table” output forces structure. Pair it with our piece on building a setlist that gets you rebooked for the framework behind these rules.

Instagram caption + hashtag set

Use when: you’re posting a gig announcement, a release, or a tour reveal.

You are a UK independent-artist social-media writer. Use only supplied
facts; mark missing facts as [NEEDS FACT]. No emojis. Write 3 Instagram
caption variants for {artist_name} announcing
{gig | release | tour | merch}. Announcement facts: {date},
{venue_or_link}, {ticket_or_stream_url}, {one_real_reason_to_care}.
City/locality for hashtags: {city_or_locality}. Caption length 80-120
words. Use plain first-person or venue-neutral
language; no hype clichés, no fake urgency. Output: 3 captions, each
with one clear CTA + 8 hashtags split into 3 local / 3 genre /
2 event-specific. UK formatting. British English. No #livemusic, no
#musicians, no #musiclife, no "drop everything", no "the place to be".

Why this works: generic music hashtags are dead. The genre + city specificity keeps you in pools of 10k posts, not 10m, where actual reach happens. Three variants gives you A/B options. Pair these captions with AI-generated graphics from our visual identity playbook for a consistent social grid.

Follow-up email after no reply

Use when: a venue, festival or curator hasn’t replied to your initial pitch.

You are a UK gig-booking copywriter. Use only supplied facts. Write a
90-word follow-up email to {booker_name} at {venue_name}. Original pitch
sent {days_ago} days ago for {date}. Do not re-paste the original pitch
in full. New news to add: {confirmed_support_act | sold_out_recent_gig |
press_mention | new_release | blank}. If new news is blank, omit the
new-news sentence and mark [NEEDS FACT: fresh reason to follow up].
Polite, zero pushy energy, single ask: "any update?". Output: subject
line (referencing the original), body.
UK formatting (DD Month YYYY). British English. No "hope this finds you
well", no "circling back".

Why this works: the “new news” line is the trick — you’re not just nudging, you’re adding value. Bookers reply to follow-ups with a reason to look again. Wait 7 working days, send once, then let it go.

Rider negotiation

Use when: a venue has confirmed and asked for your rider.

You are a UK gigging-musician rider writer. Use only supplied facts; do
not add technical requirements not supplied. Draft a concise rider
negotiation email plus rider attachment outline for {artist_name}, a
{band_size}-piece {genre} act. Tour level: {pub | mid | theatre}.
Backline supplied / required: {list}. Input list: {input_list_or_unknown}.
Stage footprint: {stage_dims_or_unknown}. Power needs: {power_or_unknown}.
Hospitality: {meals_y/n, dressing_room_y/n, drinks_spec}. Advance
contact (name + email + phone): {advance_contact}. Fee floor:
£{amount} (do not negotiate below in this draft). Output: subject line, short
email body (~120 words), then rider attachment outline. Separate must-have
/ nice-to-have / negotiable. Mark unknowns as [CONFIRM]. UK formatting,
British English.

Why this works: “Do not negotiate below this” is a constraint ChatGPT actually respects. Pair the output with our UK gig pay data so your fee floor is anchored to market reality, not what feels right at midnight.

Tour route planner

Use when: you’re sketching a UK run and need a sensible date order.

You are a UK touring-musician routing assistant. Output is provisional
brainstorm only — not for booking decisions. Provide rough routing
logic only; mark every travel time and distance as [VERIFY IN MAPS] and
every venue tier as [INFERRED — verify capacity]. Do not invent venue
names. Do not produce a list of specific venues. Plan a {n}-date UK tour for {artist_name} in
{month}. Cities to include: {city_list}. Constraints: max {drive_hours}h
drive, day off every {n} dates, avoid {dates_unavailable}. Output:
proposed city order, travel-risk notes (M25 traffic, M6 north of
Birmingham, A1(M) south of Newcastle), rest-day placement, suggested
venue tier to research per city. Expected draw / capacity target:
{expected_draw_or_capacity_range}. If blank, label venue-tier suggestions
[INFERRED] and keep them broad. End with a checklist of what I need to
verify in Google Maps / National Rail before booking. UK formatting (DD
Month YYYY).

Why this works: spelling out UK road realities stops ChatGPT routing you Bristol → Newcastle → Plymouth in a week. The “suggested venue tier” column is the cue to follow up with our live UK gig directory and find venues that match the tier in each city.

Where it still fails: ChatGPT does not know which venues are open this month. Verify every venue you cite.

Post-gig thank-you

Use when: you’ve just played a gig and want to be remembered.

You are a UK gigging-musician follow-up writer. Use only supplied facts;
mark missing facts as [NEEDS FACT]. Write a 70-word thank-you email to
{booker_name} at {venue_name} after a gig on {date}. Specific moment:
{moment}. Door / turnout: {numbers}.
Ask mode: {return date | sister venue slot | referral | no ask}. If
"no ask", do not include any booking request. Output: subject line, body. UK
formatting, British English. No "smashing time", "absolute pleasure",
"see you again soon", "until next time".

Why this works: 90% of artists never send a post-gig email. Doing so puts you in a tiny minority and is the single fastest way to a rebook. The specific-moment line proves you were paying attention.

Year-end self-review

Use when: you’re heading into a new year and need to update your pitch deck, EPK and goals.

You are a UK gigging-musician strategy assistant. Use only supplied
numbers. Label opinions as [INTERPRETATION]. Do not infer causes for
wins or losses unless the user has supplied evidence. Generate a 1-page
year-end review for {artist_name}'s {year}: gigs played ({count}),
highest-paid gig (£{amount}), biggest crowd ({number}, {venue}), press
hits ({list}), streaming change YoY ({pct}%). Output as markdown:
factual year summary, up to 5 evidenced wins (reusable as pitch-deck
bullets — write [MISSING] rather than padding if fewer than 5 are
supported), up to 3 evidenced risks to fix, next-year priorities, 5
booking actions for Q1. Label every risk, priority and action as
[EVIDENCED] (linked to a supplied number) or [INTERPRETATION] (your
opinion). UK formatting
(£, DD Month YYYY).

Why this works: the prompt forces honest self-audit. The 5 wins become EPK bullet points; the 3 losses become next year’s plan; the 3 changes become specific, actionable. Run this on 31 December every year and your pitch deck refreshes itself.

How to make any prompt better — the 5-part formula

Every prompt above shares the same five parts. Skip any one of them and the output reverts to generic AI-listicle slop.

1. Role. “You are a UK gig-booking copywriter.” Anchors voice and register before any task is given.
2. Constraints. Word count, tone, British English, language register. Without limits, ChatGPT writes long.
3. Variables. The {curly_braces} your real details slot into. The more specific the variables, the less generic the output.
4. Output shape. “Subject line first, then body.” “Ordered table.” “Bullet list, signable PDF-ready.” Defines the artefact you actually want.
5. Forbidden phrases. The single biggest quality lever. List the clichés you never want to see — “rocking the stage”, “next big thing”, “absolute pleasure”, “explosive sound”. Without this, every output sounds the same.

If a prompt isn’t working, the missing piece is almost always part 5.

How we know these prompts work — the 5 tests every prompt passes

Every prompt above passes the same 5 quality tests before it ships. They’re worth knowing because once you’ve used the prompts here, you can apply the same tests to any prompt you write yourself.

1. It can’t make stuff up. Every prompt forces ChatGPT to use only the details you give it — leave a field blank and it writes [NEEDS FACT] rather than inventing press hits, venues, fees or stream counts that don’t exist.
2. It can’t make you sound like a chancer. No fake urgency, no invented credibility, no “tickets selling fast” when they aren’t, no “next big thing”. The prompts that touch sensitive ground (rider, follow-up, year-end review) carry explicit guardrails against over-claim.
3. It produces a finished thing, not a fragment. Every email prompt outputs a subject line plus body. Every list outputs the right number of items in the right shape. Every report fills in the template — it never gives you a blank one.
4. It sounds British, not American. No “rocking the stage”, no “the place to be”. £ and DD Month YYYY. 24-hour times. “Licence” not “license”. The forbidden-phrase list is task-specific so the output reads like a working UK musician wrote it.
5. It handles blanks gracefully. If you don’t fill in a field, the prompt tells ChatGPT exactly what to do — omit the line, mark it, or ask for it — rather than letting it improvise.

The test in plain English: would you be safe pasting this output and sending it without rewriting? If the answer was no, the prompt got reworked. The same 5 tests run again at every annual refresh.

Where ChatGPT stops and GigXchange starts

ChatGPT writes the email. It doesn’t find the venue, doesn’t know the booker’s programming, doesn’t see what other gigs are happening that week, and doesn’t connect you with anyone.

The natural complement: use ChatGPT for the writing, then use a real UK live-music marketplace for everything else.

• Find venues to pitch: our live UK gig directory shows what’s on right now in 40+ cities — useful for spotting venues actively booking your genre.
• Skip the prompt entirely: our free venue outreach templates ship six pre-written email types — cold outreach, festival submission, support slot, follow-up, thank-you, residency — with one-click copy-to-Gmail formatting.
• Anchor your fees: the GX rate calculator gives you a defendable fee floor based on real UK rates by city, gig type and band size. Use the output as the {fee_floor} variable in Prompts 1, 9.
• Build a profile bookers actually read: our guide on creating a killer musician profile online covers the EPK, photo and audio assets that turn the prompt-written bio into something that converts.

Treat ChatGPT as a fast first-drafter for the writing pile. Then use the real-world tools to do the parts AI can’t.

If you find a prompt above that works particularly well for your act — or one you’d add — we’d genuinely like to know. Working musicians sharing what works is how everyone’s pitch deck gets stronger. The prompts here will be updated whenever a better version emerges. Last refreshed at the date stamped above.