What is a Booking Request?
A Booking Request is the simple, structured way to start a private conversation with one provider about a suggested time and context. It opens a negotiation. It does not confirm a booking.
Applies to: Escort Service, Private Sex, Kink & Fetish, Adult Media Talent, Erotic Show & Performance, Booth Babes & Promotion, Care & Companionship
Quick answer
A Booking Request opens a focused negotiation with one provider. It includes who is asking, desired timing, region or city, the service context, and a brief respectful note. Providers review and can accept, modify, request changes, issue a Proposal, decline, or block for safety. A request may progress to a Proposal and then a confirmed Booking upon acceptance, or it may be declined or expire. Providers remain fully in control throughout.
Overview
A Booking Request is a structured, reviewable signal of intent—not a confirmed booking. Sending one creates a single, organized negotiation thread with the provider you chose. Requests carry context from the listing (Service World, region) and can reference the provider’s Availability to cut down on back-and-forth. Verification can add confidence but never replaces provider choice. Outcomes include more clarification, a Proposal, a confirmed Booking, a decline, or expiry. Requests open focused negotiations where terms, timing, and boundaries become clear. Providers remain in control of visibility, services, pricing, availability, and booking approval.
Provider-first control
Manual review is standard. Providers decide services, pricing, availability, and whether to accept, adjust, or decline—at any time.
- Review, ask for changes, propose, decline, or block for safety
- Pause or limit visibility with no obligation to accept
- Verification can add confidence but never overrides choice
Structured negotiation, not instant booking
A Booking Request starts a focused, private thread with clear history and context. It isn’t a public comment, a mass lead, a contract, or a payment authorization.
- Single-provider, centralized conversation
- Custom requests welcome—clarified into explicit terms first
- Can progress to a Proposal and then a Booking, or be declined/expire
Privacy and trust by design
Only the needed details are shared, based on platform rules and consent. Tools and AI support clarity, safety, and cross-language communication.
- Respectful tone reduces friction and escalation
- Blocking and reporting protect against harassment or unsafe behavior
- AI helps with phrasing, missing details, summaries, and translation
How a Booking Request works
Entry points: Clients find providers through Service Worlds and Regional Billboards, then start a Booking Request from the provider’s listing.nnRequired elements (high-level):n- Who: client account and optional verification statusn- When: desired date/time window (aligned with provider Availability where possible)n- Where: region/city; optional logistics notesn- What: service context from the Service Menu; optional extras/outfit preferences or a custom requestn- Notes: brief, polite details or questions; acknowledge boundariesnnSubmission: The system bundles these details into one structured thread.nnProvider review options:n- Accept as proposedn- Ask for changes or more informationn- Send a Proposal (a concrete offer)n- Decline, or block/report if safety is at risknnOutcomes:n- Move into Negotiation for clarificationn- Result in a Proposal and, if accepted, a confirmed Bookingn- Be declined or expire after a policy-defined windownnStatus progression (examples): sent → under_review → needs_info → proposal_issued → confirmed → declined/expired
Etiquette, safety, and privacy
For clients:n- Be concise, respectful, and realistic about timing and contextn- Offer time windows and service context; avoid explicit descriptionsn- Respond promptly; accept “no” without pressurennFor providers:n- Keep Availability updated to reduce mismatchesn- Reply clearly and when comfortable; use Proposals for clarityn- Use blocking and reporting when needed; you are never obligated to continuennTrust and safety:n- Verification signals can increase confidence but never remove provider choicen- All requests must respect legal boundaries, consent, and platform rulesn- Underage or non-consensual contexts are categorically rejectednnPrivacy by design:n- Only necessary information is shared in contextn- Providers control what is visible and wherennDiscoverability behavior:n- Requests inherit Service World, region, and relevant menu contextn- Availability signals reduce back-and-forth and improve qualityn- AI guidance helps clients focus on one relevant provider at a timen- The system may limit simultaneous negotiations to encourage intentional interaction
Common questions
No. A Booking Request starts a private negotiation with one provider. It can lead to a Proposal and, if accepted, a confirmed Booking, or it may be declined or expire.
Include who you are (account and any verification), a desired date/time window, region or city with any logistics notes, the service context from the provider’s menu (or a concise custom request), and a brief, respectful note.
You can clarify or update details within the negotiation thread. Withdrawing may be possible before a Proposal is accepted; once confirmed, changes follow the provider’s stated policies.
Focus on one relevant provider at a time. The system may limit simultaneous negotiations to encourage intentional, high-quality interactions.
Response times vary. Availability signals and clear details can help. Requests may expire after a policy-defined window if there is no response.
If declined or expired, review your details and try another provider respectfully. Accept “no” without pressure and avoid repeated outreach.
You may submit a concise custom request. The provider can clarify terms in negotiation, issue a Proposal, or decline.
A Booking Request itself is not a contract or payment authorization. Any deposit or payment requirements, where applicable, are clarified later by the provider and may vary by jurisdiction and policy.
Only necessary information is shared within the private, structured thread. Providers control what is visible and where, and platform rules reinforce discretion.
Follow the provider’s stated policies for changes or cancellations. Communicate promptly within the negotiation thread to minimize confusion.
Final thoughts
A Booking Request starts a focused, respectful negotiation with one provider. Keep it concise, respect boundaries, and let clarity determine whether it becomes a Proposal and then a confirmed Booking.
Read next
- How Privacy and Discretion Work (Safety Trust)
- How Provider Onboarding Works (For Providers)
- How to Accept, Decline, or Approve Bookings (For Providers)
- How to Activate and Deactivate Billboards (For Providers)
- How AI‑assisted onboarding works (For Providers)
