ChatGPT for DJs: A Month of Social Posts, Reviews and Venue Outreach

Write a one-page voice card from three of your own messages, then give ChatGPT three jobs: a four-week post calendar built from your real gigs, a review request that goes out the morning after every event, and a three-email venue pitch spread over three weeks. You edit every draft, so it still sounds like you.

None of this touches playlists or set planning. It is the admin that decides whether next month has gigs in it: posts that show you're active, reviews that show you turn up, and venues that know you exist. ChatGPT drafts; you supply the facts it can't know and strike the claims it invents, such as events you never played or a preferred-supplier status you don't have.

Follow me on Instagram@sagnikteaches

For the on-the-night side, ChatGPT prompts for DJs: MC scripts, toasts and announcements covers the microphone. The daytime half of the business is different work, and the examples here assume about eight bookings a month across weddings, birthdays, corporate parties and school events. All prices and times below are placeholders to replace with your own.

Connect on LinkedInSagnik Bhattacharya

Your voice on one page, from three real messages

Left alone, ChatGPT writes like every other party advert: "unforgettable night", "get the party started". A voice card fixes that. You give it three messages you really sent to clients, it describes how you write, and you keep that description in a ChatGPT Project's instructions so every chat starts with it. OpenAI's help page says those instructions work only inside the Project and take priority over your general custom instructions, so your other chats stay as they were.

Subscribe on YouTube@sagnikteaches

Read the three messages below. They are how I really write to clients. Write a voice card of no more than 120 words that another writer could follow: how I open, sentence length, words I use, words I would never use, how I handle price and dates, and how I sign off. Quote at most two short phrases from the messages. Do not add traits that are not in them.

Message 1: [paste]
Message 2: [paste]
Message 3: [paste]

Sample output (illustrative):

VOICE CARD
- Opens with the date or the question, not "hope you're well".
- Short sentences. Dry humour, one joke at most per message.
- Says "a night" or "the party", never "an event experience".
- Gives the price in the first reply, plainly: "[package] is [price]".
- Never uses: "unforgettable", "epic", "curate", strings of exclamation marks.
- Signs off with a first name and the next step: "Tell me the venue and I'll check the date."

Edit the card until you'd sign it, then add two rules underneath: never invent a price, date, venue or past gig, and mark anything that needs someone's permission with [CONSENT]. Those two lines do more work than the voice description, because they stop the two worst habits of an eager writer: inventing credentials and naming people who haven't agreed.

Test the card before trusting it. Take a real enquiry you answered last month, ask ChatGPT for a reply with the card and one without, and put both beside what you actually sent. Whichever draft sounds more like you shows what the card is still missing; often it's a habit you didn't know you had, such as always giving the price before the pleasantries.

A four-week post calendar from your real gigs

A month of posts needs facts, and ChatGPT has none of yours. Spend half an hour building a post bank, which is just a list in your Project: last month's gigs (type of event, one thing that happened, whether the client agreed to a post), what's in the van and how long set-up takes, three questions clients always ask, your open dates, and any review you have permission to quote. Every post must use one item from the bank. A filled-in bank for the example month looks like this:

Using only the post bank below, plan 12 Instagram posts for four weeks, three a week (Monday, Wednesday, Friday). Mix: 2 behind-the-scenes, 3 FAQs, 2 gig recaps, 1 quoted review, 1 venue spotlight, 1 availability post, 1 seasonal post, 1 "meet the DJ". For each post give: the day, the type, a caption of up to 80 words in my voice card's style, and which bank item it uses. Put the venue or event type in plain words in the first line. At most 5 hashtags per post. Mark any post that names a client, guest, venue or reviewer with [CONSENT]. Do not invent a gig, a number, a quote or an award.

[paste voice card]
[paste post bank]

The limit of five hashtags is Instagram's own: its help page allows up to five tags on a post, a cap announced in December 2025. The old limit was 30, and a model may still reach for many more than five, so the prompt states the cap. Here is the calendar skeleton the prompt produces, with the bank item each post needs:

Twelve posts at about ten minutes each to add your facts, edit and schedule is two hours, plus the half hour for the bank. Writing the same twelve from a blank page at 25 minutes each would be five hours. Those are assumptions to replace with your own timings. The proportions are the useful part: the bank is the slow step, and it makes every later month quicker, because you only add the new gigs.

One post, before and after your edit

Suppose the bank says: Saturday wedding, 96 guests, the couple asked for a record-crackle intro on the first dance, floor full by 21:15, finish at 23:00, couple happy to be named. Here is a typical raw draft, and then what you'd publish:

Raw draft: What a night! Another unforgettable wedding in the books with an amazing couple and the best crowd. The dance floor was on fire all night! Thank you for letting me be part of your special day. #wedding #weddingdj #dj #party #love #celebration #music

After your edit: Saturday's wedding: 96 guests, a first dance that opened with the record crackle the couple asked for, and a dance floor that was full by 21:15 and stayed full until the 23:00 finish. Thanks to [couple's first names] for trusting me with it. Two summer Saturdays are still free: [dates]. #weddingdj #mobiledj

The raw draft fails four ways at once: seven hashtags against a cap of five, no fact that only you could know, stock phrases ("unforgettable", "amazing", "on fire") that your voice card should ban, and no mention of availability. The edited version keeps the specifics and drops everything a thousand other DJs could have posted. Before anything goes live, run it through a pre-publish checklist for AI-drafted posts.

Enquiry replies: a quick answer that holds the date

Most DJ enquiries arrive as a date, a guest count and "how much?". I'd rather send a quick, straight answer than a polished one a day later, and ChatGPT can draft it in seconds if you hand it your rules. It must never supply the price: every number comes from your list.

Draft a reply to this enquiry in my voice (voice card above). Use only my facts below. Answer the question asked, say whether the date is free, give the price from my list, say how long I hold a date without a deposit, and ask at most two questions I need in order to quote properly. Under 110 words. Never state a price, a date or an inclusion that is not in my facts.

Enquiry: "Hi, looking for a DJ for our wedding on [date], about 90 guests, venue is [venue]. How much?"
My facts: [date] is free. Wedding package, up to 7 hours: [price]. Includes sound system, lighting, a planning call and a wireless microphone for speeches. Date held for 48 hours without a deposit. Deposit [amount] and a signed contract to confirm.

Hi [first name], thanks for getting in touch. [date] is free. For about 90 guests, the wedding package (up to 7 hours) is [price] and includes the sound system, lighting, a planning call and a wireless microphone for the speeches. I'll hold the date for 48 hours; after that it needs [amount] and a signed contract to confirm. Two quick questions so I can check it all fits: what time does the venue's music have to stop, and is there a volume limiter? [your name]

That's sample output. The slip to watch for is generosity: a draft can add "and I can include uplighting at no extra cost", which sounds friendly, isn't in your facts, and becomes a promise the couple can screenshot. Compare every inclusion in the reply with the list you pasted. The deposit and holding rules belong in your contract too; a DJ contract template with deposit, overtime and cancellation terms covers that wording, and how wedding suppliers reply to enquiries in minutes with AI goes deeper on the speed side.

The follow-up when they go quiet

An enquiry that stalls has usually not said no; the couple are comparing three DJs and a dozen other decisions. One follow-up as the 48-hour hold runs out and one more at day five is enough, and each should carry one new piece of information instead of "just checking in".

Write two short follow-ups to the enquiry reply above, in my voice. Each under 50 words, each adding one useful thing. Day 2: the 48-hour hold ends today; offer a 15-minute call to talk through the timings. Day 5: the hold has lapsed; say whether the date is still free, using [date status], and offer to hold it again for 48 hours if they reply. Do not pressure them. Do not say other people are interested in the date unless my facts say so.

Sample output (illustrative):

Day 2: Hi [first name], your hold on [date] ends this evening. If a quick chat would help you decide, I'm free for 15 minutes this afternoon to walk through the timings. [your name]

Day 5: Hi [first name], [date] is still free as of today. If you're still deciding, reply and I'll hold it for another 48 hours. [your name]

Two checks before these go out. The hold has to match what the first reply promised: a day-5 message saying "the hold ends tomorrow" would contradict a 48-hour hold, and a couple who notice will wonder what else is loose. And the last rule in the prompt matters most. "I've had another enquiry for that date" is a pressure line models add readily, and if it isn't true it is a lie typed under your own name.

A review request the morning after every gig

Reviews are where shortcuts look harmless and aren't. Google's policy for merchants says you may not offer incentives such as payment, discounts, free goods or services for reviews. It also says you may not discourage negative reviews or selectively solicit positive ones, and that you shouldn't ask people to include specific content. Google's own help adds that you can share a review request link or QR code with customers. So the design is simple: the same message to every client, one link, nothing offered, nothing dictated.

Write a review request in my voice for a client I played for last night. Three versions: wedding (to the couple), corporate (to the organiser), birthday (to the host). Under 60 words each. Include [first name] and [review link]. Rules: ask everyone the same way; do not ask whether they enjoyed it first; offer nothing in return; do not ask them to mention anything specific; do not mention star ratings; no exclamation marks.

Sample output (illustrative):

Wedding: Morning [first name], I hope the day after is a gentle one. If you have two minutes, a short Google review of how it went would help other couples find me: [review link]. Thank you for having me. [your name]

Corporate: Hi [first name], thanks for yesterday. If it's useful to you, a short Google review of how the evening ran would be appreciated: [review link]. Happy to help with the next one whenever it comes. [your name]

Birthday: Hi [first name], thanks for letting me be part of the party. If you'd like to leave a short Google review, here is the link: [review link]. No pressure at all. [your name]

A quick sum shows why asking everyone matters. Suppose one client in four leaves a review; that is an assumption, and yours may be lower or higher. Eight requests a month gives two reviews a month and 24 in a year. Asking only the clients you judged to be happy would cut the volume and, more importantly, break the rule against selective soliciting.

Three variations of this message break the rules while looking friendly, and all three are easy to type by accident:

• "Loved it? Reply YES and I'll send the review link." That screens out unhappy clients before the link goes out, which is selective soliciting. Send the link to everyone.
• "Leave a review and get 10% off your next booking." A discount for a review is an incentive. Offer nothing.
• "Please mention the dance floor and the lighting." That asks for specific content. Let them say what mattered to them.

Send it the next morning, when the night is fresh, and from the same place every time so it becomes a habit rather than a decision. When a review arrives, reply to it, and ask the reviewer's permission before quoting it in a post: a review belongs to the person who wrote it. If you want the sending automated, how to get more Google reviews with automated requests covers the options; check that any automation still asks every client, not only the happy ones.

The three-email venue pitch: day 0, day 7, day 21

A venue's events manager gets pitches all week, so yours has to be short, specific and easy to answer. The work is in the research, not the writing: ten minutes on the venue's own website for the facts below, then ChatGPT drafts three emails from them. Don't ask it to research the venue; it will describe a plausible venue that may not be theirs.

• The kinds of events they host, and whether they list an in-house DJ or recommended suppliers.
• Any published music curfew or volume rule.
• One true feature of the room that matters to a DJ (a stage, a balcony, a long thin hall).
• The contact's role, and a named person if the site gives one.

Write a three-email pitch from me to the events manager of one venue. Emails go out on day 0, day 7 and day 21. One-to-one, plain text, under 110 words each, in my voice. One clear ask per email.

Email 1: introduce me in one sentence, mention one true thing about their venue from the venue facts, and ask whether they keep a list of recommended DJs and how a supplier gets on it.
Email 2: add something useful, not a reminder. Offer a one-page tech sheet (power, space, set-up time) so their team knows what I need. Ask whether they would like it.
Email 3: close politely. Say I will not email again, and offer to be a back-up name if a booked DJ ever cancels.

Use only the facts below. Do not say I have played at their venue unless the facts say so. Do not claim awards, numbers of events or reviews I have not listed. Leave [contact first name] for me to fill.

VENUE FACTS: converted barn; weddings and corporate hire; published music curfew 23:00; no in-house DJ listed; events manager.
MY FACTS: public liability insurance (certificate on request); equipment safety-tested each year; built-in volume limiter; 90-minute set-up; weddings and corporate parties.

Sample output (illustrative):

Day 0: Hi [contact first name], I'm [your name], a mobile DJ for weddings and corporate parties. I noticed your barn has a 23:00 music curfew, which I plan around: my system has a built-in volume limiter and I'm insured for public liability. Do you keep a list of recommended DJs, and if so, how does a supplier get on it? [your name]

Day 7: Hi [contact first name], following up with something more useful than a reminder. I have a one-page tech sheet that sets out what I need at a venue: power, floor space and a 90-minute set-up window, so your team knows before the day. Would it help to have it on file? If so, I'll send it straight over. [your name]

Day 21: Hi [contact first name], I'll leave it there so I don't clutter your inbox. If a booked DJ ever cancels and you need a reliable name at short notice, I'd be glad to be on your list. Thanks for reading. [your name]

Four checks before sending. First, strike anything the facts don't support: a common slip is a line such as "I've played at venues just like yours", which suggests a track record you haven't listed. Second, make sure the tech sheet exists before email 2 promises it. Third, use the venue's own words for its rooms and rules; a pitch that says "your ballroom" about a barn tells the manager you didn't look. Fourth, read email 1 as the events manager: does the first sentence tell them who you are and why you're writing, in under ten seconds?

Rules on marketing emails to businesses vary by where you trade, so check yours. Keep each email one-to-one to a named person or role, say who you are, honour any reply asking you to stop, and don't send a fourth. Keep a simple sheet: venue, contact role, date of email 1, reply yes or no. If you'd like a picture of the other side of the inbox, how wedding venues use AI for viewings, enquiries and follow-ups shows how venues triage what arrives.

Five edits that keep every draft sounding like you

1. Read it aloud. If you wouldn't say a sentence to a client on the phone, change it. This catches more than any checklist.
2. Delete the adjectives you never use. "Amazing", "unforgettable" and "epic" are the usual offenders, and the voice card's ban list should name them.
3. Check every fact against your records. Dates, guest counts, times, venue names, and any gig or award a draft claims. If it isn't in your post bank or your facts block, it goes.
4. Clear every [CONSENT] tag. A client, guest, venue or reviewer named or shown needs a yes before the post goes live. No yes, no name.
5. Count the hashtags and check the links. Five at most on Instagram, and a review link that opens on a phone.

A month of DJ admin, in minutes

This is a time budget, not a promised saving. If you currently spend no time on posts or venues, it is time added, and the point is that work which never gets done never brings gigs. The figures are assumptions for the example business of about eight bookings a month; replace them with your own timings.

That is about seven and a half hours in the first month and a little over six in later ones. The venue pitches are the largest block, and the one most worth protecting, because it opens a new source of bookings instead of polishing an existing one. After two months, count three things: reviews received, replies from venues, and enquiries that say where the person found you. Keep the parts that move a number and drop the rest.

Questions mobile DJs ask about using ChatGPT for admin

Can I ask ChatGPT to write reviews for friends to post?

No. A review you or ChatGPT wrote isn't a customer's review, and platforms remove reviews they judge fake. It also puts your profile at risk for the sake of a few lines. Ask real clients with the request message above, and spend the saved effort on replying to the reviews that arrive.

Do I need permission to post photos or clips from a gig?

Ask. Put a line in your contract or booking message saying you may post photos or clips from the event, and check with the client before naming them. Avoid showing guests' faces without the client's agreement, take care with children, and remove anything promptly if someone asks. Check your own contract wording.

How many venues should I pitch in a month?

For one person, ten to fifteen well-researched pitches is plenty. The research takes longer than the emails, and a pitch that mentions something true about the room works better than a bigger list with a generic opening. Track every send in a simple sheet and drop venues that never reply after email three.

What if every caption ChatGPT writes sounds the same?

Strengthen the voice card with two or three of your real captions, add a list of words you never use, and vary the post types across the week. If a draft still reads like a generic party advert, the cause is usually missing facts: add something specific from the gig, such as a request, a room or a time.

Further reads

• DJ Event Checklist: Gear, Timeline and Backup Plan Built With AI — A gear, timeline and backup checklist for the night itself.
• Wedding DJ Questionnaire: Must-Plays and Timeline Built With AI — Collect must-plays and timings from couples before the day.
• DJ Booking Software: Enquiries, Contracts and Song Requests Compared — Booking tools compared on enquiries, contracts and requests.
• How to Use AI to Respond to Google Reviews — Reply to the reviews your new requests bring in.
• How to Reply to Negative Reviews With AI: Examples and Pitfalls — Examples and pitfalls for answering a bad review calmly.
• How Much to Charge as a DJ: Wedding, Party and Corporate Packages — Set package prices before you quote them in replies.
• AI for DJ Mixing: Plan Sets and Transitions for Event DJs — A set-planning method for event DJs: client brief to energy curve, tempo and key sequencing, transition notes and a licensing check.
• Best AI for DJ Drops: Custom Voice Tags for Event DJs — How an event DJ makes custom voice tags and client name drops with AI, from script to sampler pad, with the licence and consent checks to pass first.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Maps user-contributed content policy (fake engagement) and Google Business Profile help, Manage customer reviews (checked October 2026); Instagram help page, Use hashtags on Instagram; OpenAI help page, Projects in ChatGPT. Times and minutes are illustrative.