What does it take to add a co-host on Airbnb?

Less than you'd think, and one thing nobody warns you about. You open your listing's co-host settings, enter their email address, choose how much access they get, and Airbnb sends an invite that expires in 14 days. To accept it, your co-host needs three things: an Airbnb account on that exact email, agreement to Airbnb's Community Commitment, and — the step that stalls people — a verified identity. We walked this flow on a live listing in September 2026. Here is what actually happens, including the parts the help pages skim.

Access is scoped before the invite is sent

You pick the permission level when you create the invite, not after. The scope we used — calendar and messaging access — lets a co-host answer guests and manage the calendar without touching payouts or the listing itself; fuller levels exist if you want them editing the listing too. Choose deliberately, because the choice shapes the relationship: a messaging co-host can handle every 2am question without ever being able to change your price. The invite email landed within a minute of sending, addressed to the co-host, with an accept link inside.

Accepting requires a verified identity

This is the step the invite email doesn't mention. Our invitee had an Airbnb account on the invited email and had accepted the Community Commitment; the accept page loaded, showed the listing and the access level — and the Accept button returned "Verify your identity to continue." Airbnb requires government-ID verification (in the US, an ID or the last four of an SSN) before anyone can become a co-host, and it asks at the moment of acceptance, not at signup. Verification isn't always instant. So if your co-host is new to Airbnb, have them verify their identity in account settings before they click accept — especially if the invite is already a week old, because the 14-day clock does not pause while a verification is pending.

The small print that costs an afternoon

Two more things we hit. The invite is bound to the email it was sent to — an account on any other address cannot accept it, and the fix is to cancel and re-send to the right one, which is cheap on day 2 and painful on day 13. And the accept link carries a one-time code: if clicking it sends you through a sign-in and you land on a page that errors, don't navigate to the co-hosting page by hand — go back to the email and open the original link again, intact.

What changes on day one

The moment they accept, your guest inbox is shared — and shared inboxes have a failure mode worth agreeing on in advance. When anyone opens a guest thread in the app, Airbnb can treat the message as seen and skip the email notification for everyone else. So decide the rule on day one: whoever opens a thread owns it, or explicitly hands it off. Airbnb's response-rate clock doesn't care which of you replies — only that one of you does, within 24 hours, every time.

Hiring a stranger instead of inviting a friend

If you don't have a trusted person to invite, Airbnb runs a Co-Host Network — a marketplace of hosts who co-host for a share of the payout. Candidates there have already cleared a bar: an active listing, recent hosted stays, high ratings, and the same identity verification. The mechanics at your end converge on the flow above either way: an invite, a scope, an acceptance.

A co-host is coverage only if the message reaches someone

Adding a co-host splits the work; it doesn't guarantee the work happens. A message both of you assume the other saw is answered by no one. That is the gap StayPilot sits in: it watches the message stream itself, answers what it knows, drafts what it almost knows for approval, and escalates the rest — so "I thought you had it" stops being a failure mode. If you're weighing whether you need a co-host at all, a fair first test is seeing how much of the job is answerable on the spot: paste your listing into the demo at /try and ask it the last three questions your guests asked you.