> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/your-hotels-setup/integrations/getting-connected.md). # Getting connected What your hotel provides, what Revhero does, and what to expect over the first couple of days. Setting your property up is our work, not yours. You provide a few things that only the hotel knows, and Revhero does the rest. Allow a couple of days from the start of the work until the system is fully working. In that time your data is ingested, every screen is updated, the system refreshes, your reservations are pulled from your property management system, and your first recommendations are generated. ![Four steps from your details to your first numbers](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-4e64cdb0d21bb9029cfb89eb738978bf1658d2cb%2Ffrom-details-to-first-numbers.svg?alt=media) *Four steps over the first couple of days. Two of them are yours, and completing Settings is the one that matters most.* ## What to have ready | What we need | Where it comes from | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Your property in webhotelier | Revhero connects to the property you already run in your webhotelier account. We set up the connection itself — you never hand over a personal password | | Which property management system you run | Your IT lead or your PMS supplier, plus a named contact there | | Your competitor list | You — the hotels you consider your direct competitors | | Your room counts | You — the exact number of physical rooms per room type, because every occupancy figure depends on them | | Who owns what at the property | One name per system, so questions go to the right person first time | Your operating season is read from webhotelier, so there is nothing to tell us about seasonal closures. ## Who does what | Task | Who | | -------------------------------------------------------------------- | ---------------------------------------------------------------- | | Setting up your property in Revhero | Revhero | | Connecting your systems | Revhero, with your PMS contact where the PMS needs to approve it | | Agreeing your competitor set | You and Revhero together | | Completing Settings — room counts, base room, base board, rate plans | You | | Checking the first numbers | You and Revhero | ## What happens over the first couple of days 1. **Your property is created** in Revhero and your systems are connected. 2. **Your setup is ingested.** Your room types, rate plans, rates and availability appear in [Settings](/revhero-docs/your-hotels-setup/settings.md). 3. **Your competitor set is agreed** and added, so competitor rates start arriving. 4. **You complete Settings** — room counts filled in, base room and base board chosen, rate plans assigned to boards. This is the longest step and the one that sets the pace. 5. **Your reservations are pulled** from your property management system, and your screens are updated as the data lands. 6. **The system refreshes** and your rate recommendations start to be generated. 7. **You check the first numbers** — room nights and revenue for last week, against the report you already trust. You can move around the product while this is happening. Screens continue to fill as each part of your data arrives, so a figure that is not there in the morning can be there in the afternoon. By the time your first recommendations appear, the system is fully working and your screens are steady. {% hint style="info" %} Your [Dashboard](/revhero-docs/your-hotels-performance/dashboard.md) appears as soon as your first reservations arrive. [Pricing](/revhero-docs/setting-your-rates/pricing.md) and the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) stay locked until Settings is **Complete** — so if you cannot yet yield, that is the place to look. {% endhint %} ## Keeping it connected | What changed | What you do | | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | You added a room type or a rate plan in webhotelier | It arrives with the next refresh. Then fill in the new room's inventory, or assign the new rate plan to a board, in [Settings](/revhero-docs/your-hotels-setup/settings.md) | | Your webhotelier sign-in details changed | Email , so the connection is updated before your data stops arriving | | A competitor closed, opened or repositioned | Email to update your competitor set | | You are moving to a different PMS | Email well ahead. Both systems run in parallel over the switch, and your history stays intact | | Your property closes for the season | Nothing — your operating season is read from webhotelier | ## If something stops arriving | What you see | Usual cause | What to do | | ------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **Last Upd.** on the Dashboard is not current | Your booking data has not come through | Email before you act on the numbers | | New rooms or rate plans missing in Revhero | They were added in webhotelier after the last refresh | Email if you need them in Revhero straight away | | Competitor rates blank | Your competitor set or room mapping is not complete | Email | | Your numbers do not match your PMS report | Usually a difference of convention, such as gross against net, or how cancellations are counted | Check [the glossary](/revhero-docs/support/glossary.md) for how each figure is defined, then raise it with support with one example date | | A rate went out but has not appeared on a channel | Channel-side mapping | Check the mapping in webhotelier | ## Related * [Where your numbers come from](/revhero-docs/your-hotels-setup/integrations/supported-systems.md) * [What data flows into Revhero](/revhero-docs/your-hotels-setup/integrations/what-data-flows.md) * [Settings](/revhero-docs/your-hotels-setup/settings.md) * [Getting help](/revhero-docs/support/getting-help.md) *** **Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20integrations%2Fgetting-connected.md) and quote this page: `integrations/getting-connected.md`. Say what you expected to find — that is the part we can fix.