Superintelligence Prep for Wedding DJs: Contracts and Set Lists
Keep contract terms, planner messages and set-list requests in one client record, so an AI agent answers from signed details only for wedding DJ bookings.

AI for a wedding DJ business works best when the agent answers from one client record that holds only what has been signed, confirmed or formally requested. Contracts, planner emails and set-list changes usually arrive through different channels at different times, so an assistant that searches them separately will eventually state a term nobody agreed to. This guide shows how to organize that record before any agent writes to a couple or a planner.
Key takeaways
- Keep one client record per event, and label every field as signed, requested or unconfirmed.
- Let the agent quote only signed terms, and route anything outside the contract to a named person.
- Store planner messages, ceremony timing and set-list changes in the same record, each with an author and a date.
- Start with one narrow task, such as set-list status replies, before giving the agent availability or fees.
Why wedding bookings drift away from the contract
A wedding booking changes shape many times between the signature and the reception. A couple asks by phone whether the first dance can run longer. A planner sends a revised run sheet by email with the ceremony moved earlier. A bride shares a playlist link with a note calling half of it must-plays and saying nothing about the rest. None of these messages is wrong by itself, but together they create a second version of the agreement that lives only in inboxes and text threads.
For a DJ company, the cost of that drift appears on the day. Someone requests a song that sits on a venue's restricted list, a ceremony cutoff is missed because the planner's timing was never recorded, or the crew arrives with equipment for a room the venue no longer uses. An experienced coordinator can catch much of this from memory. An AI agent cannot, unless the memory it reads is structured, bounded and dated.
What belongs in the client record
The record should be the single place where the agent looks for facts about one event. Keep it small enough to review in a few minutes and strict enough that every entry has a source.
- Signed terms: performance window, included hours, ceremony and reception coverage, equipment list, and the clauses that govern changes, cancellation and rescheduling.
- Contacts and authority: the couple, the planner, the venue coordinator, and a note on who may approve a change. A planner may suggest a song but may not approve an extra hour.
- Timing: the run sheet version currently in force, with the date it arrived and the name of the person who sent it.
- Music rules: must-play songs, do-not-play songs and venue content restrictions, each tagged with its source.
- Access and logistics: load-in window, power, parking and any room notes that affect setup.
- Change log: every request or approved change, with what was asked, who asked, the response, and whether the DJ lead confirmed it.
A step-by-step plan for separating signed details from requests
Use this sequence when you move an existing booking into a shared record. Work through the steps in order, and do not connect an agent to client messages until step five is complete.
- Step one: export the signed contract and mark each term that affects the day, such as the performance window and the equipment included.
- Step two: list every open request from planner emails, texts and voicemails, and tag each one as requested, approved or declined.
- Step three: assign an owner to each open item. The DJ lead usually owns music decisions, and the operations coordinator usually owns timing.
- Step four: write the rule the agent must follow for each category. Signed terms may be quoted directly, requests may be acknowledged but not confirmed, and anything about money, cancellation or liability goes to a person.
- Step five: test the record with questions you already know the answers to, including several the agent should refuse, and confirm that it refuses them.
- Step six: review the record before each event, so it reflects the latest run sheet rather than the version from the first call.
How do you handle set-list requests without over-promising?
Set lists are where couples most often expect a yes. A request is not a commitment until the DJ confirms it against the music rules and the timeline. An agent can collect requests, check them against must-play and do-not-play entries, and explain what happens next. It should not say a song will be played, because the DJ may judge that the moment does not suit it or the venue has restricted it.
Illustrative scenario: a couple sends a list of a dozen reception songs through their planner a few weeks before the date. Two of them appear on the do-not-play list because the venue asked for a quieter dinner service. The agent acknowledges the full list, logs the songs with no conflicts as requested, and tells the planner that the two restricted songs are with the DJ lead for a decision. The planner gets a clear status, and the DJ lead sees only the items that need a human call.
Who can change the record, and how do you protect it?
Planners are useful intermediaries, but they are not always the contracting party. Decide in advance which messages can change the record and which can only propose a change. A planner's suggestion can be logged as a request. Changes to hours, fees, cancellation terms or equipment should be recorded only after the person with authority confirms them in writing. This follows the principle in OWASP's authorization guidance: the system should check who is asking before it acts on a request.
Incoming messages can also contain text that reads like instructions to an AI system, such as a line telling the agent to ignore earlier terms. Treat client and planner text as content to be read, not as commands to be followed. The OWASP prompt injection prevention guidance explains why this separation matters. Add one more rule: the agent may never create a new term from a message, even when the message sounds official.
How a managed setup keeps the record current
Be Human designs and operates this kind of record as part of a managed setup for a wedding DJ business. The first engagement defines one useful role, such as set-list intake and status replies, the memory the agent may read, the messages it may send, and the decisions that stay with the DJ lead. Ongoing operations include monitoring the agent's answers, checking them against the signed terms, reviewing permissions when staff or planners change, and making controlled updates when a venue alters its rules. The work is remote and available in English or Portuguese. Take the free Be Human AI diagnostic to find the first task worth handing to an agent.
Frequently asked questions
Can an AI agent quote prices to couples? It can quote a fee only when that fee is a signed term in the client record and the agent's rules permit it. Anything involving new charges, discounts, extra hours or refunds should go to a person with authority. Keeping that boundary written down prevents the agent from improvising a number a planner later repeats.
Should the agent read planner emails directly? It can read them, but the messages should be stored as requests with an author and a date, not as instructions. The agent should summarize what was asked and flag any change that touches signed terms. Human approval remains the step that updates the record.
What happens when a requested song conflicts with a venue rule? The agent should not decide the outcome. It should log the request, mark the conflict against the source of the rule, and send the item to the DJ lead with the planner copied on the status. The couple then receives an honest answer about what is pending.
Does a shared client record create privacy obligations? It does, because it holds personal details about couples, their families and their vendors. Limit access to the people and agents that need each field, decide how long records are kept, and check the data protection rules that apply to your clients, including guidance from Brazil's ANPD when Brazilian clients are involved.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


