Spaces

Confirmation messages for requests, bookings and sign-ups

These confirmation messages let a station or streaming service confirm a request, a guest booking, a competition entry or a plan change. They tell the person exactly what was noted.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

A confirmation is a small promise: we heard you, here is what we noted and here is what comes next. In broadcasting this matters because so much is live and changeable. A guest booked for a slot, a request for a Friday show, a competition entry: each needs a message that says exactly what was written down.

Fill in what was noted and what happens next, then copy the message that suits the request. Keep the detail line precise, with names, dates and times, so the person can spot a mistake at once. Send it as soon as the details are logged.

Song request noted

Thanks for writing to [business]. I have noted this for the show team: [detail]. We cannot promise it will be played, but [next step]. Reply if anything needs changing.

Guest or contributor booking

Hello and thank you. [business] has noted your booking: [detail]. What happens next: [next step]. Please reply here if the time changes or you need directions to the studio.

Competition entry received

Thank you for entering with [business]. We have recorded your entry: [detail]. As set out in our rules, [next step]. Please keep this message in case you need to refer to it.

Plan or account change request

Thanks for getting in touch with [business]. We have noted your request: [detail]. A person checks every account change, so [next step]. We will not change anything until it has been checked.

Why precision matters

A confirmation that says "your request is in" tells the person almost nothing. One that says "Happy by Pharrell for Joan, Friday morning show" lets them correct a wrong name or day before it goes out. That one line prevents most of the awkward moments.

For competitions, confirmation also protects you. A record of what the person entered, and the rule you pointed them to, helps if a dispute comes later.

Things a confirmation should not do

Keep these out of your messages.

  • Promise airplay, a guest slot or a win that a person has not decided.
  • Change a subscription or charge before a person has checked it.
  • Hide the next step in a long paragraph.

FAQ

Should we confirm every request?

A short confirmation helps most. If volume is very high during a live show, confirm in one line and give a fuller answer for bookings and competition entries.

What if the details turn out to be wrong?

Ask the person to reply with the correction and note it for the show team. A quick fix before broadcast is far better than a wrong name read out.

Can the agent change a subscription itself?

It can record the request and explain the steps. A person on your team should check any change that touches billing or an account before it is made.

More free tools for radio, television and streaming providers

Read the guide: Answer listener, viewer and subscriber messages in broadcasting and content.