How quickly can we start using DJ Reception?
Most teams can configure baseline locations, services, and rules in one working session, then expand incrementally.
FAQ
This page covers the most common operational questions before and after launch.
Most teams can configure baseline locations, services, and rules in one working session, then expand incrementally.
No. You can onboard by location, team segment, or service category to reduce disruption.
The AI agent depends on required setup state, such as channel connection and booking context configuration.
Conflict checks run at booking submission. A booking is blocked when slot availability is no longer valid.
Yes. Booking rules include slot interval, lead time, buffer time, and maximum bookings per slot.
Blackout windows are configured per location and are applied during availability checks.
Team-member selection can be optional based on your booking flow configuration.
DJ Reception can auto-assign the first available eligible team member mapped to the selected service.
Integration is configured per user.
You can run one shared calendar for all locations or dedicated calendars per location.
DJ Reception bookings create or update calendar events, and calendar events can block app availability.
No. Private events are represented as Private without storing event detail content.
Yes. Instagram integration supports inbound customer messaging inside booking communication flow.
The agent can issue fallback messaging and hand off to a team member for manual continuation.
No. Current launch scope includes Instagram for channel-based messaging.
Yes. DJ Reception plans begin as paid subscriptions.
Lifecycle states include active, past_due, canceled, and unpaid.
past_due includes a 3-day grace period before additional enforcement behavior.
Audit logs include communications and booking status history, with admin-restricted access.
In-app help and feedback submissions include tracking ID confirmation for follow-up.