If you search for a VRBO co-host, the most important distinction is between what hosts may arrange privately and what the platform actually documents. I found no published co-host role, permission tier, invitation flow, or co-host marketplace in the platform’s help centre. That does not prove what may appear inside every owner account; it establishes what the platform publishes for owners to follow.
This distinction matters because the old advice to open an access setting, invite a helper by email, and assign permissions is not supported by the published documentation. I will not invent that workflow. Instead, I will explain the documented account model, the practical limits created by authentication, the alternatives the platform does publish, and how those alternatives differ from an Airbnb co-host.
VRBO does not document a co-host. Its help centre contains no co-host role, no permission tier, no invite flow, and no co-host marketplace. The word does not occur in any language across 4,122 help records queried through the platform’s own search index with typo tolerance switched off. A control term returned 407 records, confirming that the search index was returning results rather than simply failing.
That is a documentary finding, not an absolute claim about every screen an owner might see. I can read what the platform publishes, but I cannot log into every owner account. The honest formulation is therefore “VRBO does not document a co-host,” not “the product definitely has no undisclosed co-host feature.”
That documentary gap means I cannot give you a legitimate co-host setup procedure. There is no published screen I can direct you to, no documented role name, and no documented set of permissions to describe. If another page tells you to open a users menu, enter an email address, and choose a permission tier, ask that page to produce the platform documentation behind those steps.
The phrase normally describes a working relationship rather than a platform feature. An owner may want another person to answer guest questions, coordinate cleaners, respond to maintenance problems, or take responsibility while the owner is unavailable. Those are real jobs, but calling the helper a co-host does not create an account role or give the arrangement platform-defined boundaries.
Consider a host with 3 units who wants evening coverage. The owner could privately assign a helper responsibility for guest issues after a chosen hour, but the platform does not publish a messaging-only role that limits that person to those 3 units. The owner must separate the job from the technical access question instead of assuming that the word “co-host” solves both.
This is also why I distinguish guest communication from broader property management. Software for messages is not automatically a channel manager, and a person who answers messages is not automatically a property manager. The different jobs are mapped in our overview of VRBO software and tools, while channel managers for Airbnb and VRBO covers calendar and reservation distribution.
If the problem is mainly repetitive guest communication, read the breakdown of VRBO automated messages. If the problem is physical turnover work, the relevant category is closer to vacation-rental task management. Neither category should be relabelled as a documented co-host role.
You can privately hire a helper and call that person a co-host, but VRBO does not publish a way to add that person as a co-host. In practice, a helper attempting to work directly inside the owner account confronts an account built around the owner’s own credentials.
The platform’s account documentation says, “You’ll still use the same email address and password to log in.” That wording appears on the official page about the new VRBO owner sign-in page. It describes 1 email address and 1 password, not separate identities for an owner and helper.
The platform also enumerates the information available through Account Settings. The published list includes account-level contact information, login email, password, security questions, two-factor authentication phone numbers, pay-per-booking payment preferences, and commission settings. User management is not included in that list. The list appears in the VRBO dashboard documentation for integrated property managers.
I would not treat omission from a settings list as conclusive proof that no undisclosed control exists. I would treat it as another reason not to promise readers an invitation flow that the documentation never describes.
The published two-factor authentication process sends a one-time code by SMS or automated call when someone signs in from a new, different, or unrecognised device. The code goes to the owner’s registered phone number. The same number is used when Support verifies a caller.
The official VRBO two-factor authentication page says that codes remain valid for 30 minutes, can take up to 1 minute to arrive, and that 5 incorrect entries lock the account. Two-factor authentication requires setup, so I would not claim that it is active on every account.
For a concrete example, imagine an owner with 2 units and a helper signing in from a new laptop. If two-factor authentication is enabled, the helper may need the code sent to the owner’s phone. If the helper enters the code incorrectly 5 times, the published process says the account is locked. That is not a permission system; it is identity verification attached to the owner’s credentials.
My advice is not to give another person your owner password. That is my security recommendation, not a rule I attribute to VRBO. Its searchable documentation publishes nothing either way about sharing owner credentials. I therefore cannot say password sharing violates a published platform rule, but I can say that sharing a single credential creates obvious operational dependence on the owner’s password and phone.
If you need remote coverage without inventing an account role, start by listing the exact work involved. Our guide to managing multiple listings remotely separates communication, physical access, cleaning, and maintenance. The maintenance-tracking overview covers the work that still needs a person or local vendor.
Answering guests at 11pm is the part software should do.
Start free — first 500 messagesOr book a demo callYou cannot follow a documented “add co-host” procedure because there is no documented co-host role to add someone to. I cannot responsibly provide steps for an unpublished users menu, email invitation, permission level, or second-host account.
What VRBO does document are 3 different routes, each meant to solve a different problem: transferring a listing, moving it to a new property manager, or connecting property management software. None is a co-host invitation.
The platform’s transfer article says: “If you are selling your vacation rental property or are moving it to a new property manager, refer to our Property Sale and Host Transition Policy.” That sentence is the complete operational direction published on the VRBO listing-transfer help page.
A transfer addresses a handover. It does not document simultaneous access for an owner and helper. If an owner with 1 unit sells that unit, transfer is the relevant category. If the same owner merely wants someone to answer weekend messages, transfer solves the wrong problem.
The linked Property Sale and Host Transition Policy returned an HTTP 429 I therefore will not describe the policy’s contents, deadlines, requirements, or consequences. The readable help article provides only the quoted sentence.
The same transfer documentation explicitly identifies moving a vacation rental to a new property manager as a transition. This is a change in who manages the listing, not a published method for adding a second host beside the owner.
Suppose an owner has 4 units and wants another business to assume operational responsibility for all 4. Moving the listings to a property manager may fit that objective. If the owner wants a helper to cover only evening questions while retaining every other responsibility, a management transition is much broader than the requested job.
Before making that decision, I would define whether the actual need is guest communication, turnovers, repairs, pricing, accounting, calendar distribution, or complete management. The tools and responsibilities differ. Our comparison of when a PMS is needed explains the systems question, while cleaning applications and turnover software cover narrower operational work.
The documented third-party route authorises software. The official integration page says that connecting property management software to a VRBO account allows listings to be managed from one system and updates to be distributed across connected channels.
This route involves a connectivity provider, a software account ID, a credit card on file, and onboarding through a self-service link or an Account Manager. It authorises software rather than creating a named helper with personal permissions.
For example, if a manager wants 6 units distributed through an integrated management system, the software route addresses cross-system operation. It still does not create 6 co-host invitations or a messaging-only identity for an assistant.
BnBGenius is not a channel manager and does not connect through that documented PMS integration route. We do not synchronise calendars, distribute reservations, or replace a PMS. For those needs, see channel managers for small hosts and syncing Airbnb and VRBO calendars.
Because the platform publishes no co-host roles, everything a permission screen might ordinarily clarify must instead be settled between the owner and helper. The written agreement is job design. It is not a feature that VRBO creates, approves, monitors, or enforces.
I would divide the agreement into 6 practical subjects: jobs, coverage hours, decision authority, spending authority, compensation, and termination. Each subject should answer a concrete question rather than rely on a vague instruction to “help manage the property.”
List what the helper is responsible for and what remains with the owner. Guest messages, cleaner coordination, supply checks, maintenance dispatch, in-person visits, and review follow-up are separate jobs. A helper assigned to messages should not assume responsibility for repairing an appliance unless the agreement says so.
A useful responsibility list for a host with 3 units could assign the helper guest communication and cleaner confirmation for all 3, while leaving pricing, listing edits, and financial decisions with the owner. That division is private job design; it is not a platform permission tier.
“Available when needed” is difficult to measure. A better agreement defines when the helper is on duty and what happens outside that window. It should also identify issues that must be escalated immediately, such as loss of access, active water damage, or a guest safety concern.
For example, an owner might divide each day into 2 coverage blocks, with the owner taking one and the helper taking the other. The agreement should say who handles a conversation that begins in the first block but continues into the second. That prevents both people from replying differently to the same guest.
A guest-facing helper needs a clear boundary around refunds, fee waivers, replacement accommodation, early arrivals, and late departures. The agreement should distinguish routine replies from commitments that cost money or change a reservation.
If a host manages 5 units, one practical rule might require owner approval before the helper makes any paid commitment, while allowing the helper to provide existing check-in information without approval. The specific threshold is the owner’s decision; the platform does not publish or enforce it.
For related operational design, early check-in and late checkout explains the questions that should be resolved before an offer is made. Our guest-message templates help separate routine information from judgment calls.
State whether the helper may hire a cleaner, purchase supplies, call a tradesperson, or authorise emergency work. Include how receipts are submitted and how quickly the owner reimburses approved expenses.
For a fictional 4-unit operation, the agreement could require the helper to log every purchase against the affected unit and obtain approval before non-emergency spending. If the helper handles 3 purchases during a turnover, the owner should be able to match all 3 receipts to that unit. Those are internal controls, not platform settings.
Write down whether payment is tied to hours, completed tasks, a recurring period, or another privately agreed measure. Define which work is included, when an invoice is due, and how disputed work is handled. I would avoid relying on a verbal promise or an undefined “share,” especially when the scope changes by season.
The agreement should not assume that the platform splits payouts between two people. No payout-splitting procedure for an owner and helper appears in the verified documentation, so I cannot describe one. Payment terms belong in the private agreement.
Termination terms should cover notice, unfinished guest conversations, keys, codes, documents, equipment, and any credentials the owner chose to disclose. The agreement should identify the date on which the helper stops representing the owner.
If a helper covers 2 units and leaves while both have upcoming stays, the handover checklist should address both units separately. Completing the first unit’s notes does not complete the second unit’s handover.
For hosts deciding which work can be systematised before hiring, vacation-rental automation software and common automation mistakes provide a useful division between repeatable work and human judgment.
Response speed and calendar hygiene, handled for you.
Start free — first 500 messagesOr book a demo callAirbnb publishes the opposite model. Co-host access is granted per listing, and its documentation says that “the listing owner or a co-host with full-access permissions can add a co-host to their Airbnb listing.” That is a documented role attached to an individual listing rather than an informal label for someone using the owner’s credentials.
The platform also publishes 3 permission levels: full access, calendar and messaging access, and calendar access. The permission table states that a co-host with calendar access can “View but not edit the calendar.” All 3 levels can view the calendar and see guest check-in and checkout information, while calendar access alone does not include guest messaging.
Those details appear in the official what co-hosts can do on Airbnb. They should not be projected onto VRBO, which publishes no corresponding permission table.
| Question | Airbnb | VRBO |
|---|---|---|
| Is a co-host role documented? | Yes, per listing | No documented co-host role |
| Are permission levels published? | 3 levels are published | No co-host permission tier is published |
| Can calendar-only access edit the calendar? | No; it is view-only | No comparable co-host level is documented |
| Is an invitation flow documented? | The listing owner or a full-access co-host can add a co-host | No co-host invitation flow is documented |
| Does the co-host role count toward host status? | Co-hosts are not evaluated for Superhost status in that role | No comparable co-host status rule is documented |
For a concrete example, an owner with 2 Airbnb listings grants access per listing. Access to the first listing does not automatically become access to the second merely because both belong to the same owner. That listing-level structure is the central difference from a single owner credential.
The Superhost distinction matters as well. The official Airbnb Superhost requirements say that co-hosts are not evaluated for Superhost status in the co-host role. Assessments occur every 3 months and examine the previous 12 months, but reservations where someone acts only as a co-host do not establish that person’s eligibility.
I am not attributing payout splitting or a co-host marketplace to Airbnb here. Neither capability appears in the verified records available for this comparison. The documented contrast is narrower and sufficient: one platform publishes per-listing co-host access and 3 permission levels; the other publishes no co-host role or invitation procedure.
Our Airbnb co-host overview examines the work itself. For a broader platform comparison, see Airbnb versus VRBO for hosts. Hosts sharing operational information with cleaners should also read sharing an Airbnb calendar with a cleaner, because calendar sharing is not the same as creating a co-host.
Software can cover defined repetitive work, but it does not turn an undocumented co-host into a documented one. It also does not perform every job a property manager or PMS performs. I separate the jobs before choosing a tool: guest communication, reviews, tasks, calls, upsells, calendars, pricing, accounting, and on-site work are different categories.
BnBGenius answers guest messages on Airbnb and VRBO around the clock. It requests a guest review and publishes the host’s review, creates cleaning and repair tasks after checkout, answers guest calls through a voice AI agent, and sells empty nights, early check-in, and late checkout.
It installs as a browser extension in about 5 minutes, without API keys or password transfer. It can run without a PMS. That means there is no need to give the software the owner password, but it does not mean BnBGenius performs the missing PMS functions.
We do not provide a channel manager, calendar synchronisation, direct bookings, a pricing tool, or owner accounting. We do not support SMS, WhatsApp, Facebook Messenger, Booking.com, or Expedia.
We also do not perform physical inspections, replace locks, clean a unit, or carry out repairs. A helper may still be necessary when the job requires a person on site. Our role is narrower: handling the supported guest communication and operational automation described above.
| Job | BnBGenius | Human helper or another system |
|---|---|---|
| Guest messages on supported platforms | Yes, around the clock | A helper may handle exceptions |
| Guest calls | Yes, with Voice Concierge | A person may handle escalations |
| Cleaning and repair tasks after checkout | Creates the tasks | A person performs the physical work |
| Empty-night and stay-time offers | Yes | A helper could handle them manually |
| Calendar synchronisation | No | Requires the platform’s calendar tools, a channel manager, or another suitable system |
| Direct bookings | No | Requires another system |
| Pricing changes | No pricing tool | Owner, manager, or pricing system |
| Owner accounting | No | Accounting process or software |
| On-site repairs and cleaning | No | Human worker required |
Pro costs $10 per month. A unit is one rentable home, and the same home advertised on Airbnb and VRBO still counts as one unit. Voice Concierge adds $7 per month per unit.
Voice includes 20 resolved calls per month. Additional resolved calls cost $0.35 each. The included 20 calls are not described as a per-unit allowance, so I do not multiply that allowance by the number of units.
For a host with 4 units, Pro costs 4 × $10 = $40 per month. Adding Voice Concierge costs another 4 × $7 = $28 per month, making the subscription $68 per month before calls beyond the included allowance. If the account records 26 resolved calls, the extra 6 calls cost 6 × $0.35 = $2.10, making that month’s total $70.10.
The free tier covers the first 500 messages, includes every function, and requires no card. That allows a host to test the supported work before deciding whether it reduces the need for message coverage. Full details are on BnBGenius pricing.
If your problem is double-booking risk, BnBGenius is not the answer because we do not synchronise calendars. Start with calendar synchronisation between Airbnb and VRBO or compare small-host channel managers.
If your problem is pricing, use the framework in pricing tools for short-term rentals. We do not change nightly prices. If your problem is bookkeeping, see accounting and tax software; we do not provide owner accounting.
If your problem is guest messages, review follow-up, calls, post-checkout task creation, or offers for empty nights and stay-time extensions, BnBGenius covers those supported functions. The related breakdowns are available in review-management tools, AI concierge tools, gap-night revenue, and early check-in and late checkout.
The practical conclusion is straightforward. VRBO does not document a co-host role, so there is no supported co-host setup sequence for me to give you. A private helper arrangement needs a written job definition, while a property-management transition or software integration solves a different, broader problem. BnBGenius can cover specific repetitive work, but we do not provide platform roles, channel management, calendar sync, pricing, direct bookings, accounting, or physical property management.