Co-host status takes three clicks to set up. That is exactly why it misleads. It opens access. It does not move responsibility. Here is what each level gives, then the three things none of them will ever give.
- The three levelsWhat each box actually opens
- The ceilingPayouts, responsibility, availability: none of them delegate
- What remainsThe part of the job the platform does not model
What Airbnb means by a co-host
A co-host is someone you open all or part of a listing's management to. The help centre describes a family member, a neighbour, a trusted friend or someone you pay to help. You can add up to ten per listing.
That ceiling is almost never the constraint. The real threshold arrives well before ten: as soon as two people answer guests, the question stops being who is allowed and becomes who says what.
The three permission levels
This is the part most guides skim. The status is not binary. It comes in three notches, from widest to narrowest.
| Level | They can | They cannot |
|---|---|---|
| Full access | Manage the listing, pricing included. Manage reservations, accept and decline trip requests. Invite other co-hosts. View earnings | Payout method and tax details |
| Calendar and messaging access | Message guests. View the calendar | Edit the calendar. See earnings. Manage reservations |
| Calendar access | View the calendar | Edit the calendar. Message guests |
The line that matters is the last one. The most restrictive level does not allow communicating with guests at all. Plenty of hosts grant it believing they are handing over backup access, then wonder why the person never sees any messages. If you want somebody to answer, the minimum is the second level.
The middle level grants messaging without reservation management. Your co-host can therefore discuss an early arrival with a guest but be unable to confirm it. It is the setting hosts choose most often and the one that creates the most promises nobody can keep. If you pick it, decide in advance what your co-host is allowed to announce.
The three things the status does not give
1. Payouts, at any level
No permission notch opens payouts. Co-hosts can neither view nor change the payout method or tax details, even with full access, although they do see earnings.
The pay itself does exist on the platform, under a different setting: Airbnb lets you send a co-host a share, by splitting the cleaning fee, a percentage per booking, both or a fixed amount. That setting belongs to the listing owner alone, never to the co-host, whatever their access level. The four shapes and what each one implies are covered in co-host pay.
What follows from that matters more than the setting: an unwritten pay agreement becomes a dispute at the first quiet month. The amount, the basis it is calculated on, what happens when a guest cancels and how the arrangement ends all deserve to exist on paper before the first booking.
2. Responsibility, ever
The primary host remains responsible for what their co-hosts do, whatever their access level. Handing over messaging does not move the weight of a problem. It only moves who types it. A promise made by a co-host commits the listing.
3. Availability, which is the real subject
The status opens an inbox. It answers nobody. A co-host with messaging access receives the messages. Somebody still has to be present when the guest writes.
You do not choose the hour. On a three-property portfolio measured in our database over eight months, the highest point of the day falls at 8 pm, well after office hours. The thread only really stops between 2 am and 5 am. The full curve sits in common guest questions.
What you still have to organise yourself
Once the boxes are ticked, three things remain entirely yours. They decide whether the delegation holds.
Who answers, and during which hours. A co-host available in the daytime does not cover the window that matters. Write the ranges down, including the ones where nobody answers rather than discovering them on a Sunday evening.
What the co-host may promise. Late checkout, early arrival, a gesture after an incident: the list fits in five lines and removes half the friction.
What the co-host needs to know about the property. Where the fuse box is, the exact movement that opens the door, the keybox code. Those are the same instructions a well-run self check-in needs. One difference: they have to be readable by somebody who was not there.
None of that needs a contract. It needs one page. Here is the order that avoids the back and forth.
Pick the level, listing by listing
Start from the work expected, not the trust granted. If the person has to answer guests, the first level is not enough. If they have to confirm an early arrival, only full access allows it. A level can be changed later, but every change happens listing by listing.
Write the scope before the first guest
Five lines are enough: what gets decided alone, what comes back to you, the hours covered, the hours nobody covers, then the pay and the basis it is calculated on. That is the document missing from almost every delegation that goes wrong.
Write down the property instructions
The movement that opens the door, where the fuse box is, the keybox code, the plumber's number. Written for somebody who has never set foot there. That is what lets two people give the same answer to the same question.
The third point is the one people postpone. It pays the most. As long as the instructions live in your head, every evening question routes back through you, whatever permission level you granted. The status changes nothing there: it opens access to an inbox, not to what you know about the property.
Three ways to hold the inbox- CopiloteThe reply is drafted and waiting. You reread, you correct, you send. Useful while your instructions are still moving.
- HybrideReplies go out on their own during your hours, and control returns to you outside them.
- AutopiloteThe reply goes out alone. Anything outside what is known comes back to you instead of being invented.
Co-host, management company, or tool
The three answer different questions. Confusing them is expensive.
A co-host fits when the load is moderate, the person is available at the right hours and you accept staying responsible. It is the most flexible arrangement but the most fragile to absences.
A management company takes the ground: cleaning, keys, incidents. Judge it mostly on what it does with messages, not on its photographs.
A messaging tool replaces neither. It handles what is repetitive and predictable so the person who remains, co-host or company, deals with what needs a judgement call. The guide to automated messages describes where that line sits.
What each one costs
The gap is not only an amount. It is the basis it is calculated on. A co-host and a management company are both paid out of your revenue, so their invoice rises with your season. A tool is paid per property per month, so its invoice does not move.
The figures below start from one property taking €1,500 in rent over the month, with shares of 10 % and 20 %. Yours are negotiated privately because none of this goes through the platform.
| Billing basis | On that €1,500 month | |
|---|---|---|
| Paid co-host | share of revenue, paid out by Airbnb or invoiced separately | €150 at 10 % |
| Management company | share of revenue, cleaning and ground work included | €300 at 20 % |
| Sentioo | flat fee per property | €9.90 excl. VAT, tapering to €6.90 |
The three do not do the same work. A management company sends somebody to the property. A tool does not. So the useful comparison is not which one is cheapest but what is left to do once it is paid. A co-host on 10 % who does not cover the 8 pm peak leaves the evening load exactly where it was. That costs €1,800 over the year, more than a month of rent.
So the question is not whether to add a co-host, but how many hours a week your inbox costs today, and at which hours they fall. One very busy property often weighs more than five quiet ones.
