• Corporate users:

• Intermediate users:

• Single Hotel users:

1. Go to https://rateparity.rategain.com
2. Enter your username and password
3. Click on Login

• Win

• Loss

• Meet

• Overall and Split View

• Parity Score

• Loss (Violations)

• Provisional Loss

• Parity Score Across Multiple Shop dates with Region comparison

• Criticality Distribution:

• Most Violated Properties /Distribution Health

Distribution Health:

• Top Violators –

Top OTA Violators:

1. Rate Violations: This occurs when the rate offered by an OTA is lesser than the brand-site (taking into consideration the tolerance)
2. Availability Violation: This occurs when the OTA is offering a rate while the brand is closed out.

Top Meta Violators:

Channel Performance: View by Loss/Meet/Win

• Provisional Revenue Loss

1. Amount lost (based on disparities identified in the report)
2. Transient OTA business (Number of rooms sold on OTAs)

• Meta Visibility

The detailed view of all the data points is available on the Reports Page. The shopping criteria like Hotel Name, LOS, Currency, Shop date, Check-in date would be available along with the lowest rates on each channel and Brand.

All the rates shopped from multiple POS are combined under a master channel with the prefix added in front of the rates under each master channel.

Buzz: This helps you to auto buzz violations so you don’t have to manually do it. It’s simple, just define your rule and system will buzz all the violation instances that fall within the specified rule criteria.

There are two categories of violation recorded in the reports:

1. Rate Violations
2. Availability violation

Against each violation there is a “Buzz” button which when clicked will record a buzz for this violation. The user can click on it multiple times if necessary to show higher degree of concern over the violation. Also, the common “Buzz” button when clicked will increment 1 buzz against all the violations on all the pages. The circle over the buzz shows how many times a particular violation has been buzzed.

Provide Remark: Against each of the violation there is a “provide remark” dropdown which can be used to select the reason of violation. As soon as the user selects a reason and clicks OK, the violation gets closed and after this the buzz cannot be made for this violation.

Legends:

• Closed: When the site is not showing any available room for a hotel at the time of shopping.
• No Rate: When closed is not explicitly mentioned on the site during shopping but the site does not allow booking due to some reasons. E.g. The URL of the property has changed or the rates are not loaded on the site.
• Request Failed: When the data extraction fails due to some technical failure. This may also be the case when extraction of data is stopped if the particular site takes more time to load data.
• “- -“: When a particular channel or property is not shopped and hence no rates were found.

This section is where RateGain’s Test reservation data will be shown and you can send (Notify/Warn/Terminate) mails to the wholesaler contacts.

Below are the key points to note:

• All your direct connect wholesalers as added in settings will get shown here and their respective violations will be shown under their bucket.
• Reservations for which either Wholesaler was not identified at the first place by RateGain or for which wholesaler name anything apart from the Direct connect wholesalers will get listed under “Unassigned” Bucket.
• Once you assign a direct wholesaler to any reservation from the unassigned bucket, that reservation will move into the assigned wholesaler bucket.
• You can notify wholesaler contacts about the breach by selecting the templates already made in the “Closed Loop Service” section of settings page.
• You can download the entire data as an excel using the download button
• KPIs: On the header of each Wholesaler bucket you will see the below 3 KPIs
• Total Violations: This will show the total number of reservations made/violations recorded under each wholesaler bucket
• Unattended Violations: Violations for which no action has been taken (i.e. not even a single mail has been sent) will appear here.
• Total Leakage ($): This shows the total loss incurred due to breaches under each wholesaler in USD.

• Top performing properties

It compares the overall performance of the hotels taking into consideration various factors such as:

1. Number of Violations that occur under a particular property i.e. total violations recorded at the time of shopping.
2. How many violations are in the critical bucket from the total set of violations.
3. Number of violations which are still Open and need to be responded.
4. How promptly the property responds back and closes the open violation (i.e. the days for which the violation remains open).

Properties which don’t have even a single violation are represented in green and thus are the top ranked properties. The rest of the properties are ranked based on a logic that combines above four aspects to come up with a rank. Thus, it gives entire picture, a gamification aspect where the ranking can be used to incentivize performers and penalize defectors and also assists in channelizing marketing spend on properties.

• Violation status

The bar shows the number of violations still open in each booking window. While the green bar represents how many have been closed/provided with a reason. As soon as the report is generated all will be red as none of them are yet closed by the users.

• Open Violations – Top hotels

This shows the top properties in terms of the violations recorded under them.

• Not Responding – Top hotels

This shows the top properties against which the buzz has been made but they are still non responding or in other words providing reasons.

• Violation -Top reason

This shows the top reasons that have been provided while closing the violations.

• Violation – Top wholesaler

Whenever a violation is closed with wholesaler as a reason, then wholesaler name is mandatory to be recoded. This widget shows which top wholesaler have been recorded against the violations.

• User

My Account: Login password can be changed from this section.

Access Hierarchy: This hierarchy tree shows your property distribution at different geographical levels and the access information i.e. which user has access to which all set of properties. You can change the access by selecting/deselecting people at different levels.

• System

Channel Bucket:

Gives the option to configure channels as authorized or unauthorized.

• Severity:

Each row of the report is assigned a severity level based on two criteria:

1. Average Variance: As soon as a fresh report is generated, this criterion is used to assign severity tag to each row in the report.

• Number of Buzz: Once the report is generated, this aspect also comes into picture and affects the severity level of a row in the table. This is based on the number of buzz recorded on the violations that exist in a row.

Let us consider an example here: As soon as a report is generated, based on avg. variance of the violations the row is assigned a severity level of Minor. But as the number of buzz are recorded on these violations, the bucket might shift from Minor to Major and then to Critical.

Violation Reasons:

These are the reasons that the violation responder can select while providing a response to the violation occurrence. 4 default reasons are provided and you can create your own customized reasons. Each reason will exist in two states (Open & Closed) in the response dropdown in reports section. Open and Close define the state of the reason. A reason with Open tag represents that the reason is known but is not yet fixed. While a reason with Closed tag represents that the reason is known and resolved.

Tolerance:

Tolerance (%) represents the percentage variance till which the deviation of OTA rate from the brand rate is tolerable. You have an option to define tolerance at global level, regional level or city level. Any change made in the tolerance will get reflected in the subsequent reports.

Wholesaler:

In this section, you need to provide your wholesaler details:

1. Wholesaler name
2. Point of contact details within wholesaler
3. Select the properties names

Based on these settings you will be able to Warn/Alert the wholesalers notifying them about the breach where they were involved.

Step 1 Click on “Add Wholesaler” to start adding wholesaler details.

Step 2 Enter Wholesaler name, contact person email ids (comma separated if multiple) and select the properties from the drop down. By default, all the properties will be selected and you can select/de-select as per your requirement.

Due to GDPR Compliance, you need to get a consent from the recipients for them to receive further notifications from the UI. You can send them consent mails.

Without approving the consent mail, they will not receive any further mails from you via the product. Below is the way you can check the status quo of the recipient’s consent status: Pop-up will show the present status of consent mail approvals.

1. Pending: Those email ids which have received the consent mail but haven’t approved and thus your further notifications will not be delivered to them. You need to contact them to approve the consent mail.
2. Approved: Those email ids which have provided consent approval and your further notifications via the product will be delivered to them.
3. Mail not sent: Those email ids to which the consent mail is not yet sent. To such recipients you can send the consent mail using “Get Consent” as explained above.

Meta Source Channels:

1. Inclusion:
   In this section you need to provide the names by which your brand site is seen/listed on the Meta channels. Against every Meta channel configured under your subscription, you need to provide the comma separated names (if on a Meta channel your brand is identified by more than 1 name).
2. Exclusion::
   In this section you need to provide the names of the source channels which you want to be excluded from the list of Meta channels. Once you have done the same, they will no longer appear under the Violation- Meta widget and the violations from these channels will not be taken into account.

• Auto Buzz Engine

This section helps you define rules to auto buzz violations so you don’t have to manually do it. It’s simple, just define your rule and system will buzz all the violation instances that fall within the specified rule criteria.

There are two categories: Rate Violations Buzz Rule and Availability Violation Buzz Rule. You can define rule/s within each rule bucket.

Part A: Rule Creation

1. Rate Violation Buzz Rule Bucket >>> Clicking on “Add Rule” button will show the below screen with a popup:
   You can define the criteria based on which the rule engine will buzz the rate violation instances. If Variance is >= % on and if Check-in dates is <= _ days out from shop dateHere you can keep a rule like: “If variance is >= 5% on Booking.com, Expedia.com and if check-in dates is<= 10 days out from shop date” This means all the violations where variance from benchmark site rate>5% on mentioned channels will be auto buzzed for check-in dates till 10 days out from the shop date. Also, this rule can be made to trigger when:
   a) As soon as the report is generatedb) After X number of days’ post report generation. You can create multiple rules within the rate violation buzz rule bucket.
2. Availability Violation Buzz Rule Bucket >>> Clicking on “Add Rule” button will show the below screen with a popup:You can define the criteria based on which the rule engine will buzz the availability violation instances.
   and if Check-in dates is >= days out from shop date. Here you can keep a rule like: “Booking.com, Expedia.com and if check-in dates are >= 10 days out from shop date”.
   This means all the availability violations on the mentioned channels will be auto buzzed for check-in dates till 10 days out from the shop date.
   Also, this rule can be made to trigger when:
   a) As soon as the report is generated.
   b) After X number of days’ post report generation You can create multiple rules within the availability violation buzz rule bucket.
   Part B: Rule Settings Elements within each rule card >> • You can edit the rule at any time as per your business requirements and focus area. • You can delete any rule permanently from the system. • Use the expand arrow to see the criteria within that rule.

• Closed Loop Services

This section consists of wholesaler templates and wholesaler reasons.

Wholesaler Templates:

In this section you can create max 3 mail templates which can be used to send violation notifications to the wholesaler contacts.

Step 1 Click on “Add Template”.

Step 2 You need to enter the details in the template.

1. Template Title: This is the template name which helps you identify which template is being sent when you notify the wholesaler.
2. Message: This is the body/message that you want to send to the wholesaler in the notification mail.
3. Attachment: You can attach a default attachment in each template that you create and whenever this template is chosen to send notification, this default attachment will be sent along.

Wholesaler Reasons:

In this section, you can create your own customized wholesaler reasons, which can be used in the rate related fields under the closed loop service section.

STEP 1 Click on “Add Wholesaler Reason”

STEP 2 Add the customized wholesaler reason under the reason section.

Once the same is done, click on Save or Add more reasons as per requirement. Also once saved the same reason can be edited anytime and deleted only if it is not used for any test reservation.

RateGain Support Team, enhances your experience with RateGain solutions throughout the lifetime of your relationship with RateGain.

Write to support team at help@rategain.com or use the following contact numbers to get in touch with our customer support team.

Toll Free US Number: 1-800-987-1508

Europe Support Number: +44-203-514- 2345

China Support Number: +86-400-120-3069

Indian Support Number: +91-120- 509-7001

Indonesia Support Number: 1-803-015-205-0063