Skip to main content

Hotel CMS for Multi-Property Operators

Write it once per language. Every channel gets it in the form it takes.

One content master per property and language: texts, rooms, photos, amenities and policies. See what's missing across the portfolio at a glance, then send it everywhere, from the channels that take content by API to the extranets that don't.

ChannelRUSH photo manager for Marivela Beach Resort: photo targets with counts, the main photo and its pixel and file size
What your partners open
Marivela Beach Resort's public content page: Copy name and address, a language switch, the ZIP download and the same photos in the same order

The main photo leads on every channel

A 14-property operator cut content updates from 6 hours a week to 20 minutes.

Three people on a regional operator's marketing team spent 6 hours a week syncing photos, descriptions and policy changes to nine OTAs, the website and the booking engine. Six months in, one person keeps every channel current in under 20 minutes.

Regional operator, 14 properties, US Southeast.

BeforeWith ChannelRUSH
Time on content updates6 hrs a week20 min
People keeping channels current31

ChannelRUSH today

  • 200+ Channels connected
  • 100+ Attributes per property
  • 500+ Properties live
  • <15m Median update to channel
  • Booking.com
  • Expedia
  • Agoda
  • Ctrip
  • HotelTonight
  • HotelBeds
  • Hotels.com
  • Sabre

The content back office

Every property and every language on the same screens. These are real screens from our demo account.

Content settings for Marivela Beach Resort: English, German and Spanish profiles, the profile's language and its public content link

One profile per language

Each language is its own content profile, with its own descriptions, facts, amenities, policies and pages. The demo runs English, German and Spanish; a profile can be any language your guests read.

  1. English, German and Spanish side by side. Add a profile for any other language.
  2. Each profile has a language, so channels and sites get the right one.
  3. Every profile has its own public content link, switched on or off.

One master, three ways out

Every channel takes content differently. ChannelRUSH sends it in the form each one accepts, from the same master.

Straight into the channels that take content by API

Descriptions, photos, room and rate plan content, amenities, contacts, fees and taxes, and settings such as pets and payments go straight into the channels that support content push. Create a listing's content, update it, or switch it on and off.

  1. Choose the property, its room types and rate plans.
  2. Pick the content to send to each channel.
  3. Send, and see each request come back accepted or rejected, with a retry for anything that didn't land.
Content delivery statusExample
ContentItemOutcome
DescriptionPropertyAccepted
PhotosProperty, 14 photosAccepted
Room contentOcean View KingAccepted
AmenitiesProperty, 16 codesAccepted
PhotosGarden View Two QueensPhoto 4 is below the channel's minimum size.RejectedRetry
Representative example. Demo accounts never send content to channels.

Every other channel gets a link

Each language profile has its own content page, no login needed. Send the link to whoever loads an extranet without a content API: they copy each value with one click instead of digging through documents and photo folders.

  1. Copy the name and address in one click.
  2. Switch language: every profile has its own page.
  3. Download every photo and text as a ZIP.
Open a live content page(opens in a new tab)
The Cordwainer's public content page: name and address with Copy buttons, a language switch, the ZIP download and a numbered photo mosaic
  • A Copy button on every value, and a character count on every text.
  • Rooms, extras, booking policies, fees and taxes, each in its own section.
  • A 'Not provided' list wherever something is missing, so nobody hunts for it.
  • Download it all as a ZIP (an offline copy of the page, the data as JSON, and every photo at full size and at 1200 px) or as JSON.
The Studio King room on the public content page: sleeps, beds, bed type and size, photos with the main one marked, and a 191-character description with a Copy button
A room, ready to copy
Zirbenhain Alpine Lodge's German profile: tagline, short and long descriptions, each with a character count and a Copy button
The German profile, same layout
The Content Delivery screen: an email to a channel with the public content link, ready to copy
The email, written for you
Marivela Beach Resort's own website on the Lanai theme, opening on the same main photo
The same main photo, on the resort's own site.

Your own sales, from the same content

The profiles that feed the channels also run your direct sales. Change a description once and your own site has it too.

  • Your booking engine and its widget.
  • Hosted websites and themes, including one site for the whole group.
  • Google Hotels: room names, capacity and the search photo.
  • The CRS API, in every language.

CRS APIGET /api/v3/settings/{propertyId}/{language}

Built for portfolios

Ten properties or a hundred, in every language your guests read, kept by one team.

Before
Word documents and photo folders emailed to every extranet, one property and one language at a time, with no way to see which listing is out of date.
With ChannelRUSH
One content master per property and language, one push to the channels that take it, one link for the ones that don't, and one login for the team.
  • One login, every property

    A property switcher across the whole account. Staff get their own logins, limited to the properties and permissions they need.

  • Group-level content

    Org content profiles, photos, pages and testimonials for multi-property sites, plus wording overrides for the whole group.

  • Templates for the whole group

    Org Templates apply channel settings across properties, including whether each channel receives content.

  • Vacation rentals too

    Bedrooms, bathrooms, beds and sleeps for every home, on your rental site and in each home's room content.

  • More than rooms

    Restaurants, spa, events and nightclub venues, each with its own description, photos and amenities.

  • Answers and guest messages

    Ask the AI assistant, or your own AI over MCP, which properties can't take bookings yet and why. Guest messages and reviews from the channels arrive in one place, with permissions per user.

How hotel groups run on ChannelRUSH

Live in 2–4 weeks

01

Connect

We connect your properties to their channels, next to the PMS and channel manager you already use.

02

Load

We bring in the content you have: texts, photos and room details, per property and language.

03

Fill the gaps

The Content Summary shows your team what's missing, property by property.

04

Go live

Push to the channels that take content, send the link to the rest, and switch on your sites.

Want to see it with your own properties?

Talk to us about your portfolio

Talk to us

Show us your portfolio's content.

Tell us how many properties and languages you run. We'll walk you through the content back office with your channels in mind, in about 20 minutes.

/ FAQ /

Frequently Asked Questions

Your master stays in ChannelRUSH. The next push to a channel that takes content by API sends your version again, and the public content page always shows the current master. Most teams make ChannelRUSH the one place content gets edited.

Descriptions, photos, room and rate plan content, amenities, contacts, fees and taxes, and settings such as pets and payments, to the channels that support content push. Each channel takes what its API allows, and the send screen offers only what that channel accepts. Every other channel gets the public content page.

Each language is its own content profile, with its own texts and its own public content page. Photos and amenity codes are shared by every language, so you manage them once. Channels, your sites and the CRS API each get the language they ask for.

Most operators in this range are live in 2–4 weeks. We connect your channels, bring in the content you already have, and the Content Summary shows your team what's left to fill in, property by property.

Yes. Content management sits next to the PMS and channel manager you already use: your PMS keeps rates, availability and reservations, and ChannelRUSH handles the content that channels and websites need.

No. Content management works on its own. If you use our booking engine or hosted websites, they read the same content, and the CRS API serves it to any site you already have.