When a flag appears
The source doesn’t change the request itself; it sets a flag and notifies the agency when:
- the request has a client (the calendar, BIO and Bandsintown don’t move such requests);
- the request has several artists and one of them moved the event;
- the request’s date has passed or the performance is recorded;
- money has been received;
- the source only observes the request (for example, “Same concert: keep our data” was chosen);
- the request has several driving sources, or the artist has left the agency.
The flag shows where the change came from — “on Bandsintown” or “in the artist’s calendar” — and, for a move, the old and new dates.
What the agency should do
- Check with the artist and, if there is one, the client what happened.
- If the show really moved, change the request date manually. You don’t need to unlink the request from Bandsintown for that: locked fields.
- If it was cancelled, decline the request (if money was received, the agency owner does this with a reason).
- If the change is a mistake, leave the request as it is.
Notifications
- The regular sync notification goes to agency members according to their regions.
- Warnings that an event was moved to a date with active holds or one taken by another request come in a separate push category that can’t be switched off, because they need attention. During quiet hours the push waits until morning; the email is sent right away.
See also: how sources change requests, notifications you can’t turn off.