Updating “Streamline Direct or Boost” – June 2026 Alignment

Summary

• Purpose & scope

  • Align the internal “Streamline Direct or Boost” article and its comparison charts with June 10, 2026 product guidance.

  • Capture Conall’s view that Boost is near feature parity with Vrbo + Airbnb integrations, while Streamline clearly wins on messaging, especially for Airbnb.

  • Provide concrete chart updates, messaging, and an Expand macro (Notes from 6/10/26 meeting) that can be selectively incorporated over time.

• Key themes

  • Boost: now the default distribution engine – multi‑channel, automation, bulk configuration, and Booking.com V2.

  • Streamline: remains the messaging engine – full PMS data access, dynamic tags/templating, and stronger Airbnb messaging workflows.

  • The real differentiator is no longer “who has the integration,” but data access + messaging sophistication, especially as OTAs limit guest email visibility.

• Section preview

  • Section 1 clarifies the objective and scope of the update, including where to place the new Expand macro.

  • Section 2 provides concrete chart changes for Vrbo, Airbnb, Airbnb Messaging, Booking.com, and a cross‑cutting Messaging/Data row, plus a refreshed simple matrix.

  • Section 3 outlines Boost’s multi‑channel efficiencies and PMS migration/onboarding patterns.

  • Section 4 deep‑dives into PMS data access, dynamic tags, and common messaging/data challenges.

  • Section 5 summarizes Boost support structure, QA expectations, and test‑booking best practices.

  • Section 6 gives a fully drafted structure and content for an Expand macro titled Notes from 6/10/26 meeting.

  • Section 7 concludes with the recommended internal positioning: Boost for distribution, Streamline for messaging.

• Critical takeaway

  • For distribution, pricing, and cross‑channel consistency, steer teams and clients toward Boost.

  • For guest messaging, personalization, and Airbnb‑heavy workflows, steer toward Streamline direct.

  • Frame internal conversations around “Boost = distribution engine; Streamline = messaging engine”, not “which has the better Vrbo/Airbnb integration.”

1. Objective and Scope

1.1 What this update is meant to do

The immediate objective is to bring the “Streamline Direct or Boost” comparison article in line with product reality as of June 2026. Historically, some internal content implied that Streamline’s direct connections were categorically “better” for Vrbo and Airbnb, while Boost was a step down. Product and implementation experience now show that this is outdated: Boost has effectively reached parity with Streamline direct on core Vrbo/Airbnb integration behavior, while Streamline’s major advantage persists in messaging and data‑driven workflows.

Your updated article should therefore shift emphasis in three ways. First, it should explicitly note that for Vrbo and Airbnb listings, pricing, promotions, and core behavior, Boost and Streamline are “pretty similar,” using Conall’s language to anchor expectations. Second, it must highlight messaging and PMS data access as the true differentiators, especially for Airbnb. Third, it should paint Boost as the multi‑channel distribution platform of choice—including Booking.com V2, Google VR, and Marriott—rather than just another way to connect to one or two OTAs.Rezfusion Boost Product Page

A secondary objective is to make the article easier to maintain. By moving dense meeting notes, nuance, and edge‑case analysis into an Expand macro at the bottom of the page, you can keep the top‑level guidance brief and opinionated while still preserving the detail needed for later edits and training. This report therefore includes both chart‑ready content and long‑form notes that should live under Notes from 6/10/26 meeting.

1.2 Specific assets to update

The primary asset to refresh is the main “Streamline Direct or Boost” comparison chart that lives near the top of the article. That chart currently has rows by channel (Airbnb, Vrbo, Booking.com, Google, etc.) and columns for Streamline vs. Boost plus recommendation notes. You should:

• Rewrite the Vrbo and Airbnb rows to:

  • Acknowledge near parity in core integration features.

  • Reposition Boost as the default choice for Vrbo in new setups unless messaging is the deciding factor.

  • Flag Airbnb messaging as the biggest remaining gap.

• Update the Booking.com row to make Boost’s BDC V2 integration the default recommendation for almost all cases.Booking.com (New UI) – Talking Points & Feature Comparison

• Add a cross‑cutting row on “Messaging & Data Access” that captures the central June 10 insight.

In addition, if the article currently includes a simple summary matrix (e.g., Pricing / Promotions / Multi‑channel / Messaging), that table should be updated to reflect the new parity and the messaging gap. Section 2.4 of this report provides a refreshed matrix you can drop in.

Finally, the article should end with a new Confluence Expand macro titled Notes from 6/10/26 meeting. All of the deeper analysis, example language, and extended comparison content from Section 6 can go into that Expand so you can selectively expose detail over time without cluttering the main narrative.

1.3 Scope boundaries and what not to change

It is important to keep the scope of this update bounded, so the article remains focused and manageable. This round of edits should not attempt to:

• Document every Boost‑supported OTA channel in depth; that level of detail already lives in the Online Travel Agent (OTA) Tool Kit.

• Rewrite the entire history of Boost vs. Streamline performance; the goal is to reflect current product truth, not to restage past migrations or legacy models such as older Booking.com V1 behavior.

• Replace channel‑specific setup instructions. Technical onboarding flows for Streamline‑Boost connections, Boost Partner Network channels, and new Booking.com V2 accounts are meticulously documented elsewhere and should be linked, not duplicated.Rezfusion Boost™ Implementation Overview

Instead, treat this work as a narrative and positioning layer on top of existing technical documentation. You’re answering “Which path should we recommend, and why?” rather than “How do I map a fee for Airbnb?” Those how‑to answers remain in the RUKB and product drafts.

2. Chart Updates – Core Content

2.1 Reposition Boost vs. Streamline (Top-Level Messaging)

Your first change should be to adjust the introductory text immediately above or alongside the main comparison chart. That short “high‑level summary” needs to convey Conall’s bottom‑line view:

• Boost is near feature parity with Vrbo + Airbnb integrations on core behaviors (listings, pricing, promotions).

• Streamline still clearly wins on messaging, especially for Airbnb, because it has full PMS data access and a mature dynamic templating/tag system.OTA Integration Feature Comparison Report – Inhabit Brands

A concise top‑level framing you can adopt is:

Boost = distribution engine; Streamline = messaging engine. Boost is the default for multi‑channel distribution, automation, and Booking.com/Google/Marriott. Streamline remains the default for advanced guest messaging and Airbnb‑heavy workflows that depend on PMS‑driven templates and dynamic data.

This language should then be echoed in a short legend or key near the chart, so readers can map individual rows back to the overall story. For example, you might add two bullet points under the chart:

• “Use Boost when: you need consistent pricing/promotions across multiple OTAs and care about automation.”

• “Use Streamline direct when: guest messaging and custom workflows are central to your brand.”

By setting that frame upfront, each row in the chart ceases to be a one‑off judgment and instead becomes an instance of the general rule: Boost for distribution strength; Streamline for messaging depth. That alignment is particularly helpful when new team members or adjacent Inhabit teams reference this article without full context.

2.2 Update Existing Rows in Main Comparison Chart

The core of the work is to update specific rows in the chart. Below is a shortened, ready‑to‑paste table for the most critical rows; you can merge or adapt these into your existing master chart.

Table 1 – Updated key rows for “Streamline Direct or Boost” chart

When you merge this into your existing chart, keep the bolded phrases (“pretty similar,” “BIGGEST REMAINING GAP,” “Key 6/10/26 insight”) so that internal readers can quickly scan for where June 10 feedback is embedded. That visual signaling also helps trainers and PMs point teams to the most important rows during onboarding and sales enablement.

2.3 Add Cross-Cutting Row for Messaging/Data

In addition to the explicit Messaging & Data Access row above, consider adding a short callout immediately under the chart that reiterates this theme in plain language. For example:

Messaging & Data Access summary (June 2026) Boost increasingly matches Streamline on core Vrbo/Airbnb connectivity, but its messaging is limited by OTA policies and the subset of PMS data exposed for distribution. Streamline continues to have a structural advantage in messaging because it sees the full PMS and can drive dynamic, property‑ and reservation‑specific communication. If OTAs further restrict guest contact info, this gap becomes even more pronounced.

This short paragraph reinforces the idea that integration parity does not translate to messaging parity, which is exactly where confusion has arisen historically. It also prevents the Messaging & Data row from being overlooked among many channel‑specific rows.

From an implementation standpoint, think of this as the bridge between the chart and the rest of the article. After readers see per‑channel recommendations, they can then read this cross‑cutting note and understand the higher‑order pattern: Boost = integration parity + multi‑channel power; Streamline = messaging depth.

2.4 Simple Summary Table Refresh

Many internal readers prefer a compact matrix view summarizing the key comparison dimensions. The outline already proposes such a matrix, and you can now safely adopt it as is, with minor wording tweaks to align with the updated chart.

Table 2 – Simple capability snapshot (Vrbo/Airbnb focus)

Place this matrix either directly under the main chart or midway through the article under a heading such as “Quick internal reference.” That gives account teams a single view they can screenshot or reference in calls, without scrolling the entire page.

3. Multi-Channel Management & Migration

3.1 Multi-Channel Efficiency

One of Boost’s core selling points—and a central reason to prefer Boost over Streamline direct for most OTA distribution—is its ability to centralize and standardize multi‑channel management. Boost’s Partner Network and direct integrations now cover Airbnb, Vrbo, Booking.com (new UI), Google Vacation Rentals, Homes & Villas by Marriott Bonvoy, HomeToGo, Hopper, VacayMyWay, Whimstay, Savvy, Livly, and more in a unified interface.(draft) Boost PMS and OTA Integration List

Operationally, that means a property manager can:

• Configure global settings (e.g., house rules, cancellation policies, lead times) once and apply them across many listings and, in some cases, channels.

• Use Amenity Mapping to connect PMS amenities to OTA‑specific amenity taxonomies, with automatic mapping for VRM, LiveRez, Streamline, and iTrip, and guided mapping for Escapia and Track.Amenity Mapping (Boost New UI)

• Rely on Boost’s data synchronization framework, which generally pushes fee/content updates to OTAs within hours and rate/availability changes within 5–15 minutes, depending on PMS and queue load.(Draft) Boost Data Synchronization

By contrast, Streamline’s direct integrations are typically managed one channel at a time. Each integration has its own settings surface, taxonomy, and sometimes external Extranet dependencies, which is manageable for one or two channels but becomes unwieldy at scale. The practical result is that Boost simplifies life as channel count grows, both by concentrating configuration and by abstracting away per‑OTA quirks.

For your article, this section should emphasize that multi‑channel efficiency increases linearly with the number of OTAs. A client on just Vrbo might feel fine on Streamline direct, but a client concurrently on Airbnb, Vrbo, Booking.com, Google VR, and Marriott will quickly feel the pain without Boost. That argument is particularly compelling for enterprise‑scale PMCs, whose portfolios and owner expectations inherently push them toward broader distribution.

3.2 PMS Migration & Onboarding

Another area where Boost materially outperforms “PMS‑only” direct paths is in PMS migrations and onboarding transitions. Boost’s architecture and tooling allow you to preserve OTA connections and configuration as clients move from one PMS to another (e.g., VRM to Streamline) or from legacy Boost engines to new ones.Boost PMS Migration Instructions (PMS Transition Tool – Updated Draft)

Key patterns to highlight:

• The PMS Transition Tool exports listings and configuration from a source Boost engine and imports them into a destination engine. This prevents having to rebuild every fee, tax, and amenity mapping by hand.

• For Streamline users, the Streamline On‑Boarding Instructions for Rezfusion Boost describe a predictable 4‑step process: Get Tokens, Enable Units, Update Documents, and Update Taxes & Fees. Token creation auto‑configures Boost reservation types, processor type, travel agents, and copies HAXML taxes/fees into Boost‑specific reservation types.Streamline On‑Boarding Instructions for Rezfusion Boost™

• Clients can optionally enable unique Streamline‑Boost reservation types per channel (Google‑Boost, Marriott‑Boost, Booking.com‑Boost, etc.), which allows channel‑specific documents, taxes, and markups without significant extra setup.Draft Enabling Unique Streamline‑Boost Reservation Types

You can summarize the migration process in a small table for internal reference:

Table 3 – High-level Boost migration/onboarding sequence

This structured view makes it clear that onboarding to Boost is not just a one‑time connection, but a disciplined process with clear hand‑offs and QA built in. That is a key part of the value proposition when compared with manual direct integrations.

4. Messaging, Data Access, and Dynamic Tags

4.1 PMS Data Access & Dynamic Tags

Streamline’s data access and templating are at the heart of why it still wins on messaging. As the PMS of record, Streamline stores rich data about each property (amenities, location, capacity), each reservation (guest details, dates, line‑item charges, payment status), and numerous operational/custom fields (door codes, notes, configurations). Its internal messaging and document systems can pull from this full data set.

Dynamic tags—tokens like {reservation.first_name}, {unit_name}, {lockbox_code}, {arrival_date}, {balance_due}—allow templates to render personalized, property‑specific, and reservation‑specific content at send time. This makes it possible to maintain a library of high‑touch communications without manually editing each email when something changes. The PMS simply re‑evaluates the tags against the current reservation data.

Because Streamline controls both the data layer and the messaging layer, it can support complex conditions (e.g., different instructions per property, custom sequences by channel or reservation type) that Boost cannot. Boost’s dataset is necessarily narrower: it receives what it needs to publish listings and to persist OTA reservations back into the PMS, but not the full suite of PMS‑internal details needed for sophisticated messaging.

In practice, this means that if a client emphasizes guest experience, bespoke arrival instructions, and property‑level nuance, we should explicitly direct them toward using Streamline’s messaging engine as the primary communication tool. Boost can and should still manage distribution for those reservations, but not the core messaging strategy.

4.2 Common Challenges

Although the division of labor (“Boost for distribution, Streamline for messaging”) is conceptually clean, there are several practical challenges that come up in implementation and support. Your article can briefly call these out, both as caveats and as guidance for internal teams.

First, there is often confusion about where a message originates—Boost, the OTA, or the PMS. For example, Airbnb supports an “Instant Book Welcome Message” and a “Booking Confirmation Message” within Boost’s Airbnb Channel Settings, but those messages are constrained by Airbnb’s policies (e.g., no phone numbers or URLs in the pre‑booking message).Airbnb Channel Settings Meanwhile, Streamline may be sending its own confirmation and pre‑arrival emails based on reservation type. Internal teams must help clients decide which layer “owns” each communication, and avoid duplicate or conflicting messages.

Second, data mapping and field availability vary by PMS and OTA. Auto‑mapping is strong for some PMSs (Streamline, VRM, LiveRez, iTrip) and weaker or more manual for others (Escapia, Track).Amenity Mapping (Boost New UI) As messaging workflows rely more heavily on amenity and property configuration, inconsistencies in mapping can surface as incorrect or incomplete information in emails. Implementation and Support should therefore treat amenity and policy mapping as first‑class QA items, not afterthoughts.

Third, OTA policies around guest contact information are shifting. Airbnb already obscures guest email addresses for channel managers, forcing reliance on the Airbnb messaging app. Booking.com and Vrbo still expose more guest detail today, but there is no guarantee this will remain true in the medium term.Booking.com FAQsOnline Travel Agent (OTA) Tool Kit Conall has explicitly flagged that if Vrbo/Booking.com adopt Airbnb‑style restrictions, Boost’s messaging options will shrink while Streamline’s PMS‑driven messaging remains viable.

For internal readers, the net message is: treat messaging and data access as evolving constraints, not static features. When OTAs tighten access, the value of a PMS‑centric messaging engine like Streamline’s rises; when OTAs remain open, Boost can coexist with (but not replace) PMS messaging for transactional communication.

5. Support, QA, and Best Practices

5.1 Support Structure

Given the complexity of multi‑PMS, multi‑OTA distribution, the support structure around Boost is a key part of the choice between Boost and Streamline‑direct. Your article should reassure internal teams that when they steer clients to Boost, they are not leaving them to navigate complexity alone.

Boost has:

• A dedicated implementation team (Software Implementation Specialists) responsible for onboarding new Boost clients, configuring channels, running test bookings, and handing off successful projects to Success and Support.Boost Implementation Overview

• A formal Boost Support organization, with tiered roles (Support Specialist, Senior Product Support, future Technical Support Engineer) and documented SLA targets for first response and resolution across ticket severities.Boost Support – Service Targets

• Internal issue‑escalation procedures, including when to raise bugs to Product/Engineering, how to include OTA and PMS partners, and how to communicate root‑cause analyses back to customers.Draft Boost Support Documentation & Issue Escalation

A small internal table can clarify roles for readers:

Table 4 – Boost support roles (internal)

By spotlighting this structure, the article reinforces that Boost is safe to recommend even for complex portfolios: the combination of process (onboarding, QA) and people (implementation, support) is designed to mitigate the risk inherent in multi‑channel distribution.

5.2 QA and Validation

The last core theme to surface is that QA is non‑negotiable for any Boost deployment—whether a first‑time onboarding or a migration from Streamline direct to Boost for a given channel. Internal documentation emphasizes that configuration is not “done” until test bookings have been run and validated against PMS expectations.

Standard QA steps include:

• Running at least one test reservation per OTA (often using “real” credit cards, then cancelling for a refund) to validate rent, tax, and fee behavior.Completing a Test Reservation

• Verifying that the reservation shows up in the PMS under the correct reservation type and with accurate totals (including commissions, markups, and any booking fees).

• Reviewing listing data sources and overrides in Boost to ensure that content is coming from the PMS where expected, and that any manual overrides are intentional and documented.Identifying Listing Data Sources and Removing Listing Overrides in Boost

For Streamline‑Boost users, QA includes confirming that Boost (PDWTA) and any unique per‑channel reservation types have the correct taxes, fees, and documents enabled.Streamline On‑Boarding Instructions for Rezfusion Boost™

Your article should remind internal readers that the reason we can confidently recommend Boost over Streamline direct for many channels is not just product capabilities, but also process discipline. When we follow the QA playbook—test reservations, validation against PMS, and early monitoring—clients are far less likely to encounter unpleasant surprises after going live.

6. Insert Expand Macro – “Notes from 6/10/26 meeting”

6.1 Location and Macro Setup

To keep the main article concise while preserving all of the nuance from the June 10 meeting, add a Confluence Expand macro at the very end of the document, after any existing appendices or legacy notes.

• Title: Notes from 6/10/26 meeting

• Placement: End of article, before any final “Last updated” footers.

• Contents: All subsections 6.2–6.7 below should live inside this Expand.

This structure allows the top‑level guidance (charts and short narratives) to stay tight and readable, while power users, trainers, and product owners can expand the macro to see the full details of Conall’s feedback, including example phrasing and deeper analysis.

What follows are drafted subsections you can paste directly into the Expand. You can trim or adjust the level of detail later without affecting the main narrative.

6.2 High-Level Summary (Inside Expand)

Use this subsection to state, in unambiguous language, what changed on June 10 and why it matters. A simple three‑point structure works well:

1. Parity statement. Spell out that Boost is now “close to feature parity” with Streamline on core Vrbo and Airbnb integrations: listings, pricing, promotions, and basic behavior. You can briefly mention that this is consistent with internal comparison work and Boost’s use of Streamline Total Logic for reservation creation.Boost‑Streamline: Reservation Logic & Price Adjustments

2. Messaging gap statement. Emphasize that Streamline Direct still clearly wins on messaging, particularly for Airbnb, where Boost’s capabilities are constrained by OTA data and policies. Point to the lack of guest email visibility for channel managers and the depth of Streamline’s PMS‑driven dynamic templating.

3. Key differentiator. Explicitly conclude that the critical differentiator going forward is “depth of PMS data access + dynamic templating,” not simply “who has the integration.” This is the conceptual lens through which all other notes should be read.

Keeping this summary short and declarative gives future editors an easy way to refresh the rest of the Expand without losing the main signal from the meeting.

6.3 Where Boost Is Strong (Inside Expand)

In this subsection, list Boost’s strengths as articulated in the meeting, with enough detail to support future sales and training materials.

Start with channel parity for Vrbo and Airbnb. Quote Conall’s characterization that Boost parity with Vrbo is “pretty similar” to Streamline direct, meaning that listings, pricing, promotions, and core behavior are closely aligned. Note that, for those channels, Boost leverages Streamline’s Total Logic to create reservations, which ensures consistent fee/tax behavior compared with Streamline’s own directs.Draft Rezfusion Boost vs. Streamline Direct: OTA Performance Comparison

Next, highlight promotions and pricing. Clarify that Boost supports OTA‑native promotions such as Airbnb Early Bird and Last Minute discounts and Vrbo promotions, and that Boost manages markups centrally while OTAs manage merchandising (ranking, strikethroughs, badges).Airbnb – Last Minute & Early Bird DiscountsVrbo – Promotions (Discounts)

Finally, underline multi‑channel consistency, including Booking.com V2. Briefly recap that Boost standardizes behaviors across Vrbo, Airbnb, BDC, Google VR, Marriott, HomeToGo, Whimstay, and others via a single configuration layer, with self‑service mapping, bulk settings, and near real‑time updates for Booking.com in particular.Booking.com (New UI) – Talking Points & Feature Comparison

These three paragraphs together tell the “steelman” case for using Boost wherever distribution, pricing, and channel count dominate decision‑making.

6.4 Where Streamline Is Stronger (Inside Expand)

This subsection should, by contrast, steelman the case for Streamline direct, focusing on messaging and data.

Begin with messaging as the biggest gap. Describe how Streamline Direct has full PMS data access for messaging—property‑level fields, reservation details, guest information, and custom fields—and supports dynamic tags like {reservation.first_name}, {unit_name}, and {lockbox_code} in its templates. Explain that this enables highly dynamic, personalized, property‑specific messages that respond automatically to reservation events and guest status, and that this capability is explicitly called out as a differentiator in internal comparison documents.OTA Integration Feature Comparison Report – Inhabit Brands

Next, detail Boost’s limitations. Note that Boost does not have access to all PMS data needed for advanced templating and that internal docs currently mark Airbnb and Vrbo messaging integrations as “Does NOT Support” for Boost. As a result, Boost cannot fully replicate Streamline’s dynamic tags and conditional workflows; its messaging is inherently less powerful and less dynamic.

Then, call out the Airbnb‑specific constraint and future OTA email risk. Explain that Airbnb does not provide guest email to channel managers, so Boost is limited to the Airbnb messaging app with reduced PMS context. Streamline, by contrast, can work around some of these constraints using internal messaging triggered by Airbnb bookings. Close by reiterating Conall’s warning that if Vrbo or Booking.com restrict guest emails in a similar way, Boost will face the same limitations there, while Streamline’s PMS‑centric messaging remains viable.

Together, these paragraphs justify the article’s strong recommendation to use Streamline direct for Airbnb‑heavy, messaging‑centric portfolios.

6.5 Practical Comparison Snapshot (Inside Expand)

Here, you can embed a concise overview table that internal readers can reference without scrolling the full article. The outline already includes such a table; you can paste it directly inside the Expand.

Table 5 – Practical comparison snapshot (inside Expand)