Run a Test Inquiry & Booking Response Drill
Practice the first renter interaction before launch so you know where requests appear, how to verify inventory, and how to move the conversation forward.
A vendor should not be considered operationally ready only because listings are published. Run at least one friendly test inquiry so you can prove the response workflow works.
What the drill should test
- You can find the request in Bookings or the current request workflow.
- You can identify the listing, dates, quantity, and fulfillment request.
- You can confirm inventory before replying.
- You know where Messages is and can respond clearly.
- You can identify the next PartyShare step without moving the transaction into an unsupported off-platform process.
Step by step
Create a realistic inquiry
Use a friendly tester and a real listing with dates and quantity that resemble a normal event.
Find the request
Open the Vendor Dashboard and locate the booking/request indicator or Bookings area.
Verify before responding
Check inventory, dates, fulfillment, and any listing-specific terms.
Respond through PartyShare
Answer the renter's question directly and keep material booking details in the marketplace workflow.
Record friction
Note any screen, terminology, or step that was confusing. Fix the listing or ask Vendor Success before live renter demand arrives.
Completion checklist
- Test inquiry received.
- Request found without assistance.
- Listing/dates/quantity verified.
- Availability verified.
- Response sent through PartyShare.
- Next step understood.
- Any confusing workflow was documented.
FAQ
Why test if my listings are already live?
Because launch readiness includes the operational response, not just publication. A test inquiry catches support problems before a real event depends on your answer.
