🐞 Duplicate notification emails (RESOLVED)

Some users may have received duplicate notification emails between ~7pm PST on May 20,2020 and 5pm PST on May 21, 2020.

This issue has been resolved and our apologies for any inconvenience or frustration caused here 🙏

Thanks to our #1 🐞bug hunter Ben @ Volo for helping us catch this pest!

🐞 Incorrect minimum review threshold in vendor dashboard after the recent update (RESOLVED)

With the rollout from the latest HT Score update from April New Quality Signal Variables Update we noticed that the counter for minimum review threshold in the dashboard wasn't showing the correct number (see below).  

Thanks to our bug hunters of the day--Marvin and Ari @ RoomPriceGenie for spotting this pest so we could squash him like the bug that he is.

Status: This issue has been resolved and the dashboard now shows the correct variance from the minimum review threshold per the April HT Score update.

Want to check the category average to double check?

Head to your category, click the compare button on the upper right of any product tile and take the average # of reviews for products in your category with at least 30 reviews. 

Like many of you, we've taken the current crisis as an opportunity to refactor some of our code base and inevitably, a few pesky 1 🐞s will slip through the cracks and this is one of those bugs so appreciate your patience and you bringing anything you find to our attention so we can fix it asap 🙏

Issue accepting leads (RESOLVED)

Status update: RESOLVED

Yesterday we rolled out some performance improvements to the lead inbox so that companies with hundreds of leads whose dashboards previously took up to 15 seconds to load (so sorry!) they will now load instantly.

The good news...we deployed the code refactoring update last night (May 7th) and your dashboard will now load all leads instantaneously without any load time (woot!).

The bad news...users have pointed out 3 little bugs that we're working on fixing:

  1. 🐞Bug #1: After you purchase a lead, the details don't appear (RESOLVED)
  2. 🐞Bug #2: Lead pricing doesn't show in the accept modal (RESOLVED)
  3. 🐞Bug #3: The forward to CRM feature is passing through 'matched' as the source for RFP leads even though the source should be RFP. (RESOLVED)

Thanks to our bug hunters of the day Chris @ Protel, Gustav @ ASSA ABLOY, Nancy @ Pegasus and Valyn @ Nor1 for hunting down these pests.

🐞 Bug #1: After you purchase a lead, the details don't appear (RESOLVED)

Temporary fix, just make sure to reload your page after you purchase a lead and the details will appear correctly.

🐞 Bug #2: Lead pricing doesn't show in the accept modal (RESOLVED)

When accepting leads, price was missing in the modal after pressing the 'accept' button.  

🐞 Bug #3: CRM forwarding showing incorrect source for RFP leads (PENDING)

RFP leads currently are sending the source as 'matched' in the CRM forwarding feature of the lead inbox when in fact the source is RFP and they are direct leads.

(we are working on a fix for this)

Phantom lead notifications (RESOLVED)

Since the library/framework updates we've had a handful of vendors report 'phantom' notifications where if they have already accepted/declined a lead, they still get the checkin/reminder notification about viewing the lead before it expires (shown below).

Shout out and special thanks to our bug hunters of the day, Ben @ Volo and Nora @ OTA Insight.

  • Fix in progress: Reminder notification will de-activated once company has accepted/declined a lead
  • Reported: January 22, 2020
  • Resolution status: In progress

CRM forwarding email not saving (RESOLVED)

  • THE BUG: When trying to add a new CRM forwarding email address for leads, the success modal shows but when you refresh the page the address looks like it wasn't saved properly.
  • REPORTED: Shout out to our bug hunter of the day Gustav @ ASSA ABLOY (1/20/20 @ 2am PST)
  • RESOLUTION STATUS: Resolved (1/20/20 @ 9am PST)
  • THE CAUSE: We recently rolled out some library and framework updates last week and this is a side effect/bug that arose from it. We are working to get it resolved and apologize to any companies that have been inconvenienced by it

📬 Subscribe to the notification center updates to get notified when the fix has been deployed.

Linkedin login has been removed from Hotel Tech Report

Historically, vendors have had to claim their profiles and login using Linkedin to verify their identity as an employee at their company and access their vendor dashboard.


  1. Linkedin login has caused several UX issues including duplicate accounts and notifications as well as confusion around accessing the vendor dashboard
  2. As a result, Linkedin will be removed as an authentication and login option from the HTR web-app the week of January 20th
  3. If you are a vendor used to logging in with Linkedin, you will need to reset your password the next time you login by pressing the 'forgot password' button on the login modal

How to sign in as a vendor and create a password once Linkedin has been removed from HTR?

Problem: Issues and confusion caused by Linkedin login

Linkedin login has caused the following UX issues as follows which is why it is being removed (and how it will benefit you):

  1. Users creating duplicate accounts: Some vendors come to HTR and forget that they have to use Linkedin login to access their vendor dashboard so they try to login with their email address and it accidentally creates a duplicate account for them causing confusion because it looks like they are logged in, but for some reason can't access their vendor dashboard as they usually do (since they usually login with Linkedin but this time forgot to)
  2. Duplicate company connections created by teammates: In some cases, users have already claimed their profile but then a team member tries to invite them again which creates a duplicate connection to the company on behalf of the invitee.
  3. Duplicate notification emails: If you were a user who experienced either #1 or #2 above it is possible that you are/were receiving duplicate notification emails for your company

Review form leading to error page Friday 1/17/20 (RESOLVED)

The review form is currently leading to an error page as shown below.

The issue is due to the recent library upgrades and maintenance and we are currently working on a resolution.

Status: Resolved and users impacted notified

Duplicate notifications (RESOLVED)

A handful of vendor users have reported duplicative notifications. We have been investigating the issue and found that in some cases vendors who had either (a) created an account with email and another with Linkedin or (b) vendors who had an account but then also were sent an invitation to the vendor dashboard had multiple connections to their company and were therefore being sent multiple connections.

This issue is in the process of being resolved. Duplicate account connections will be de-duped and we are also adding a final check for notifications that ensures that notifications are only sent to unique emails as an extra precaution/safeguard.

Unable to accept new leads (RESOLVED)

  • THE BUG: A handful of companies are experiencing a bug where they are blocked by an overlay when trying to accept new leads.
  • REPORTED: Shout out to our bug hunters of the day Ben @ Volo and Amy @ GuestRevu for finding this critter (1/15/20 @ 10:05am)
  • RESOLUTION STATUS: The bug has been escalated and our dev team is looking into the issue. We'll post an update let you know as soon as its been resolved. Appreciate your patience in the meantime! (1/15/20 @ 9:20pm)
  • THE CAUSE: We are currently working through some code refactoring and unfortunately the side effect is weird random bugs like this popping up on occasion so we apologize to any companies that have been inconvenienced by it.

Invoices showing incorrect dates in dashboard (Resolved)

Over the holidays HTR updated several libraries and frameworks which has the one of which was Stripe.

One of the bugs that popped up was that dates were being sent incorrectly to the HTR app and invoices in the vendor dashboard were all showing from 1970 (cue the Back to the Future theme song...).

Reported: January 4, 2020 | Status: Resolved January 7, 2020

Thanks to Romain @ Mews for catching this nasty little pest 🐛 .

Show Previous EntriesShow Previous Entries