Airbnb Co-Hosts: Responsibilities, Costs, Payouts, and Alternatives

Updated September 16, 2026

What is an Airbnb co-host?

An Airbnb co-host is a person the listing owner authorizes to help manage an Airbnb listing. Access is granted at the listing level: the listing owner, or a co-host with full-access permissions, can add another co-host to that listing. This is not the same as giving somebody the credentials to the owner’s entire account.

The owner controls how much access the person receives. I would also treat the owner as operationally responsible for deciding who gets access, supervising the arrangement, and making sure any work outside the platform is completed. Adding a co-host does not by itself settle who cleans the home, attends emergencies, approves expenses, or deals with local compliance.

For a concrete example, an owner with 3 listings may grant a co-host access to only 1 listing. The authorization is per listing rather than an automatic account-wide appointment, according to the Airbnb co-host introduction.

A co-host is therefore best understood as a listing-access role plus a separate working relationship. The access controls what the person can do inside the platform. A private agreement controls the wider job: response coverage, cleaning coordination, onsite assistance, expenses, compensation, and termination.

What does an Airbnb co-host do?

The duties depend on both the permission level and the private arrangement. Airbnb documents 3 permission levels: full access, calendar and messaging access, and calendar access.

The narrowest level matters. A calendar-access co-host can view the calendar but cannot edit the calendar, price, or listing. That person also cannot message guests. By contrast, calendar and messaging access adds guest communication. The detailed distinctions are published in the Airbnb co-host permissions table.

Platform permissions are not the same as offline responsibilities. Cleaning, physical check-ins, supply runs, damage inspections, and repairs happen outside the dashboard. An owner could give someone calendar and messaging access while hiring a different local contractor for cleaning. Conversely, a cleaner might receive calendar access without agreeing to answer a single guest message.

Suppose a host receives 30 new guest messages during a busy weekend. A co-host with calendar and messaging access could handle those conversations, while a calendar-only cleaner could see the relevant check-in and checkout dates but could not reply. The number is an illustrative workload; the permission distinction comes from the linked platform documentation.

For message operations, compare that division of labor with Airbnb automated messages, guest message templates, and the workflow in maintaining an Airbnb response rate.

How much does an Airbnb co-host cost?

I would not budget around a supposedly universal co-host percentage. Compensation belongs in the arrangement between the owner and the co-host, and the workload can vary substantially. A remote messaging role is not equivalent to a local operator who inspects damage, manages vendors, and attends emergencies.

Consider a clearly labeled example rather than a market benchmark. If an owner and co-host privately agree to 15% of $96,000 in annual booking revenue, the calculation is:

$96,000 × 0.15 = $14,400 per year.

Those figures are assumptions for this example, not a published standard co-host rate. At the same percentage, compensation rises when revenue rises. If the workload stays similar while annual revenue increases, the cost still follows the agreed revenue share.

The first 2 rows are hypothetical private compensation arrangements. The BnBGenius figure uses our published $10 per month Pro price. A unit means one rentable accommodation. It remains one unit when the same accommodation appears on more than one supported platform.

Cost alone should not decide the matter. A percentage may cover onsite availability that software cannot provide. Before comparing prices, list the actual work: guest communication, calendar visibility, turnovers, inspections, repairs, vendor coordination, or financial administration. The Airbnb owner operations overview helps separate platform activity from the work surrounding each stay.

How do Airbnb co-host payouts work?

Co-host compensation and co-host platform permissions are separate questions.

I would put the payout formula in writing rather than relying on a verbal description such as “a share of each stay.” The agreement should specify whether compensation is based on booking revenue, a fixed amount, cleaning work, completed tasks, or another clearly defined basis. It should also identify exclusions, refunds, cancellations, taxes, and the treatment of any separately charged cleaning amount.

For example, imagine a booking with an illustrative $1,000 compensation base and a privately agreed 15% share. The result is $150. If the parties disagree about whether a separate cleaning amount belongs in that base, they can reach different totals. That is why the definition belongs in the contract.

I would record at least these payout details:

• Formula: the exact amount or calculation method.
• Base: which booking amounts are included or excluded.
• Timing: when compensation becomes earned and payable.
• Adjustments: treatment of refunds, cancellations, and altered reservations.
• Cleaning: whether cleaning compensation is separate from management compensation.
• Termination: how unfinished bookings are handled after access ends.

The owner should confirm the current payout controls inside the listing before promising that the platform will execute a particular structure. For broader booking economics, see Airbnb service fees. That subject is different from privately negotiated co-host compensation.

How do you add or remove a co-host on Airbnb?

The documented starting point is the individual listing. According to Airbnb’s listing-level co-host guidance, the listing owner or a full-access co-host can add a co-host. The practical principle is to open the listing’s co-host controls, select the person, and choose the minimum permission level required for the work.

There are 3 permission levels, so I would make the access decision before sending an invitation. A cleaner who only needs arrival and departure timing may fit calendar access. A remote guest-service operator may need calendar and messaging access. Full access should be reserved for duties that genuinely require the broadest control.

1. Identify the specific listing that needs help.
2. Define the duties before selecting access.
3. Choose among the documented permission levels.
4. Use the listing’s current co-host controls to add the person.
5. Confirm separately that the private agreement matches the access granted.

When the relationship ends, platform access and contractual obligations must both be addressed. Removing listing access does not by itself answer who will handle an existing guest issue, an unfinished turnover, keys, vendor invoices, or compensation associated with future bookings.

For example, if access is due to end while 2 active stays still need support, the owner should assign those conversations before removing access. The figure is illustrative, while the listing-level access rule and the 3-level permission structure are documented by the linked platform pages.

Hosts who only need a cleaner to see turnover timing should also consider sharing an Airbnb calendar with a cleaner. That can be a narrower operational answer than granting messaging or full access.

Do you need a local Airbnb co-host?

A co-host does not have to be local for work that happens online. Guest messaging, calendar review, check-in instructions, and issue triage can be handled remotely when the selected permission level supports the task. Physical work is different.

Only somebody near the accommodation can personally perform a physical check-in, inspect reported damage, deliver replacement supplies, attend an urgent repair, or verify that a turnover was completed. Software and remote operators can notify the right person, but they cannot enter the home and do the work.

The access facts in the table come from the Airbnb permission comparison. The onsite distinctions are physical realities rather than platform features.

As an illustrative staffing test, record every intervention across 30 days. If all but 1 can be completed remotely, a local emergency contact plus automation may fit better than a broad management arrangement. If repeated visits are necessary, local coverage has real value.

For a wider remote-operations framework, see managing multiple Airbnb listings remotely, the turnover cleaning checklist, and maintenance tracking for short-term rentals.

How do you find someone through the Airbnb Co-Host Network?

I would treat any network as a discovery route, not as a substitute for due diligence or a private agreement. Availability, eligibility, presentation, and contact controls can change, so the current platform page and the interface shown for the listing’s location should be checked before relying on the network.

Whether a candidate comes through a network or a personal referral, I would use the same screening process:

1. Write down the precise duties.
2. Separate remote duties from onsite duties.
3. Ask who covers absences and emergencies.
4. Check whether the candidate has relevant local vendor relationships.
5. Negotiate compensation and define its calculation base.
6. Select the minimum platform permission level required.
7. Put termination and access removal in writing.

For a concrete example, interview 3 candidates against the same written scope rather than comparing an hourly quote from one person with a revenue-share quote from another. The number is my suggested procurement example, not a platform requirement.

If the problem is primarily repetitive guest communication, compare human coverage with Airbnb automation software and AI property-management applications before agreeing to a permanent revenue share.

How do you become an Airbnb co-host?

The direct route is to be added to a specific listing by its owner or by a full-access co-host. That authorization is listing-specific, and the person adding the co-host selects an appropriate permission level from the 3 documented options.

Joining a network is a separate matter from receiving a direct invitation. I would not merge the two routes. A listing owner may already know the person they want to add, while a network is intended to help people discover potential working relationships where that service is available.

I also would not publish unsourced network thresholds as permanent rules. Eligibility requirements can change, and the current official network page should be checked when applying. That is particularly important for claims involving recent stays, booked nights, ratings, cancellation performance, identity verification, or account standing.

Someone preparing for the role should be ready to explain:

• Which guest conversations they will handle.
• Whether they provide onsite coverage.
• What response hours they offer.
• How they coordinate cleaning and maintenance.
• Which of the 3 permission levels they need.
• How they expect compensation to be calculated.
• How access and unfinished work will be handled at termination.

For example, a candidate offering coverage for 2 listings should distinguish a messaging-only service from a package that includes physical inspections. Those jobs expose the owner to different costs and require different operational resources.

Superhost status should not be confused with the co-host role. Airbnb states that co-hosts are not evaluated for Superhost status in that co-host role. Its Superhost assessment looks back over the previous 12 months and occurs every 3 months. More detail appears in the Superhost requirements overview.

What should an Airbnb co-host agreement include?

A written agreement should connect the real-world job to the platform permission level. This checklist is practical planning information, not legal advice. Local counsel should address employment classification, agency, licensing, insurance, tax, and liability questions that depend on the jurisdiction.

• Compensation: percentage, fixed fee, hourly amount, task rate, or another formula.
• Cleaning amounts: whether they belong to the compensation base or pay for separate work.
• Responsibilities: messages, turnovers, check-ins, inspections, supplies, vendors, and emergencies.
• Response hours: the exact coverage window and backup procedure.
• Account permissions: which of the 3 documented access levels will be granted.
• Spending authority: what can be purchased without advance approval.
• Damage claims: who gathers evidence, communicates, and tracks deadlines.
• Insurance and liability: which policies apply and who bears specified risks.
• Termination: notice, final compensation, property return, and access removal.
• Unfinished bookings: responsibility for guests who booked before termination but arrive later.

For example, an agreement could authorize emergency purchases up to an illustrative $200 without advance approval while requiring written approval above that amount. The number is an example for drafting clarity, not legal advice or a platform rule.

The permission schedule should quote the selected access level accurately. Under Airbnb’s 3-level structure, calendar access is view-only and does not permit guest messaging. If the contract requires the co-host to answer guests but the owner grants only calendar access, the written scope and technical permission contradict each other.

I would also add an offboarding checklist covering keys, smart-lock administration, vendor contacts, documents, pending reimbursements, scheduled messages, open maintenance, and future reservations. Removing platform access should be one item in the process, not the entire process.

What is the difference between an Airbnb co-host and a property manager?

A co-host is an Airbnb listing-access role. The person’s actual duties depend on the selected permissions and the private agreement. A property manager usually describes a broader operational relationship that may include maintenance, vendors, finances, compliance, staffing, and work across multiple booking channels.

The co-host facts are supported by the Airbnb's introduction to co-hosts and its 3-level permissions table. The property-manager column describes a typical contractual scope, not a universal legal definition.

BnBGenius is not a property management system and does not replace one. We do not provide a channel manager, calendar synchronization, direct bookings, pricing tools, owner accounting, or support for every booking channel. The distinction matters when comparing it with the systems in the small-host channel-manager comparison and the guide to deciding whether a PMS is necessary.

For example, an owner with 3 units who needs synchronized inventory across channels needs a channel manager or another suitable calendar solution. BnBGenius does not provide that synchronization. Its role is narrower automation around supported guest communication and operations.

Is an Airbnb co-host worth it, or is automation cheaper?

The answer depends on whether the missing work requires a person. Automation can be much cheaper when the problem is repetitive communication and task routing. It is not a substitute for physical check-ins, inspections, repairs, or other onsite work.

Here is the corrected 3-unit example. Assume the owner and co-host privately negotiate a 15% share of $96,000 in annual booking revenue:

• Illustrative co-host cost: $96,000 × 15% = $14,400 per year.
• BnBGenius Pro cost: $10 × 3 units × 12 months = $360 per year.
• Illustrative difference: $14,400 − $360 = $14,040 per year.

The co-host percentage and revenue are hypothetical inputs, not a standard market rate. The BnBGenius price is ours: Pro is $10 per month. Our free tier includes the first 500 messages, all functions, and no card requirement.

BnBGenius installs as a Chrome extension in about 5 minutes, without API keys or password sharing. It can be controlled through Telegram. Voice Concierge costs an additional $7 per month per unit. It includes 20 resolved calls each month, followed by $0.35 per resolved call.

The narrower product boundary is important. BnBGenius can automate guest messaging, review activity, offers, calls, and task routing. It cannot enter a property, greet a guest physically, inspect damage, complete a repair, reconcile owner accounts, set prices, take direct bookings, or synchronize calendars.

I would keep a human when the operation repeatedly needs local judgment or physical action. I would consider automation first when the workload is dominated by predictable questions, review follow-up, extension offers, calls, and task creation. Useful next steps include Airbnb automation, AI guest-call coverage, upsell tools, vacation-rental task management, and the practical automation workflow.

The final decision need not be all human or all software. An owner can automate repetitive work while retaining a local person for the smaller set of tasks that require physical presence. In the 3-unit example, the $14,040 difference is not proof that automation provides identical service. It is the budget available to buy local coverage selectively rather than automatically assigning a percentage of every booking.