Skip to main content
Question

Booking Window setting not being recognized in any channels

  • August 19, 2026
  • 1 reply
  • 11 views

suzanneBB1
Participating Frequently
Forum|alt.badge.img

For multiple weeks now my Hospitable calendar has been BLOCKED starting in June 2026 although my Hospitable calendar setting has the booking window set to 24 months.  After reporting via the “smarty” AI bot, I finally got a response from a human and they told me they pushed a sync, to wait a bit and check.  I waited 48 hours - still had the issue and let the support rep know.  

They escalated to engineering and closed my ticket!!  So not way to follow-up via “smarty”.   After escalating to a human again, I got a message the next day that they are “working on it” and said it had something to do with the new VRBO connection and the old VRBO connection.  I asked for the ticket to remain open until the issue was closed.  (seriously, what software support department just closes tickets when the issue is still open and impacting a subscriber’s business?).  

 

So it’s been a week - got an update yesterday that they are “still working on it”.  I asked for an ETA and what level this defect was classified as - more than 24 hours later, no response.

 

2 questions:

  1. anyone else had this calendar issue after moving to the new VRBO integration?  
  2. anyone else had issues with getting a response from a HUMAN on the status of a critical defect?  if so, any suggestions on how to get a response with more substance than “we’re working on it”? 

1 reply

Nouran Smogluk
Hospitable Team Member
Forum|alt.badge.img+2
  • Hospitable Team Member
  • August 20, 2026

Hi Suzanne,

I just picked up your ticket and replied to it. Your Vrbo calendar should be correct now, please let me know if you’re still seeing issues.

We dropped the ball on our side here. Smarty had initially suggested the right solution but my team went down the wrong rabbit hole and assumed the issue was related to your Vrbo connection, which it wasn’t. It should never have been escalated to engineering, and we should’ve resolved it immediately when you contacted us.

I’m sorry it took us so long. I’ve of course addressed this internally with my team as well.