Back to journal
Support2 min read

Booked Provider Not Responding: A Practical Escalation Protocol

If a booked provider is not replying, document the missing confirmation and escalate with the event timing and booking record. Keep replacement decisions separate from cancellation and refund status.

Written byBookaBooking guides

Last reviewedBooka

Event professionals calmly resolving a technical issue backstage
Booka Journal / South Africa

The short answer

What to know before you start

Send a clear follow-up in the booking thread, record your contact attempts and tell Booka support how close the event is. Ask for a status review and assess backup options, but do not treat silence as a completed cancellation or authorisation to pay for a replacement.

At a glance

Booked Provider Not Responding: A Practical Escalation Protocol quick facts
First stepAsk for specific confirmation in the existing booking conversation.
EscalationGive support the event time, booking reference and contact timeline.
ReplacementCheck existing obligations before committing to another booking.

Start with documented contact attempts

Check the last agreed response time and the current booking status. Send one concise request for the missing confirmation and a deadline appropriate to the event.

Provider follow-up

Booking/reference: [reference]
Our event is on [date/time]. Please confirm [arrival, scope or outstanding detail] by [requested time]. I last contacted you on [dates]. If you cannot deliver the agreed service, please tell us promptly so we can contact Booka support about the next step.

Escalate by event proximity

Escalate based on the actual risk, not a rigid waiting period. If the event is imminent or a critical requirement is unresolved, contact support promptly with that context.

Practical checklist

  • For a later event, agree a realistic confirmation deadline and track it.
  • If a promised deadline is missed, send the timeline to support.
  • For an imminent event, state the event start time and immediate operational risk.
  • Explore alternatives without assuming the original booking has been cancelled.

Escalate to support with evidence-ready context

Give support the booking reference, event time, the last response and your dated contact attempts. Identify exactly what decision you need help with.

Keep relevant screenshots or messages, but avoid repeatedly opening duplicate requests. Support needs to review the record; this guide does not promise an emergency response time or a replacement provider.

Next step

Ask support to review the booking

Include the reference, event start time and contact-attempt timeline.