Product introduction: submitting does not always mean booking
After finding a suitable place for a weekend trip, you usually want to settle your accommodation quickly. But listings use different confirmation methods: some can be booked directly, while others require the host to respond first.
Airbnb distinguishes these paths as Instant Book and Request to book. The first does not need separate host approval; the second includes a period of waiting for a decision. Official booking guide
This article focuses on telling “submitted” from “confirmed” after choosing a listing. For a traveler, that difference affects more than a line on a screen: it affects whether you can move on with the rest of your plans.
Core workflow: move from a listing to a definite result
Suppose you have set up your Airbnb account and want to book a two-night stay on the website.
1. Check the listing and terms, then identify the booking method
Choose your dates and guest count, then select Reserve. Review the price, house rules and cancellation terms. If the next step is Confirm and pay, you are using Instant Book. Request to book instead asks you to provide the relevant details and send a request to the host. Your account may also need identity verification. Booking steps
2. Treat waiting as a separate stage
After sending a request, open Messages, find the reservation message with your host, and check the status in that conversation. Confirmed means the reservation is confirmed; you will also receive a confirmation email. Where to check status
While waiting for the host, watch the status and email updates. The host has 24 hours to accept or decline; otherwise the request expires. Pressing Submit is not confirmation. Avoid sending multiple requests for the same dates, since more than one host could accept. Response deadline and updates
3. Choose the next action from the current status
Before the host accepts, open Trips and select the reservation. For a reservation marked Pending, choose Withdraw request, then Cancel request to confirm. Once it has been accepted, use the cancellation rules for a confirmed reservation instead. Withdrawal steps
If a request is declined or expires, you can choose another stay. Check the result of the existing request first, so two uncertain arrangements are not mistaken for one settled plan.
Payment timing varies by region. A waiting status does not prove that no charge has occurred. Check the actual order and applicable policy for amounts and cancellation results. This workflow is complete when you see a definite confirmation, not just a successful submission.
Design lessons: show how far the commitment has progressed
Let the button explain who acts next
Confirm and pay and Request to book help users anticipate whether someone else still needs to respond. This can reduce confusion between a successful submission and a completed transaction. The tradeoff is that users must understand two methods; a vague single “Done” button would merely postpone that distinction.
Give waiting an understandable boundary
A waiting state should explain both what remains uncertain and the deadline and actions available. Before acceptance, withdrawal and continued waiting still make sense. After confirmation, a different set of rules applies. A useful principle is to make a state answer both “What is happening?” and “What can I still do?”
Automatic confirmation depends on preparation
The host settings guide presents automatic acceptance and manual responses together, and reminds hosts to maintain their calendars. Automation moves some decisions into availability and rules; manual responses leave some decisions to each request. When applying this idea elsewhere, examine the freshness of the information supporting automatic confirmation as well as the steps it removes.