Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Pet Limits and Fees

Currently, if you max out the guest count, you can not add a pet. If you reduce the amount of guests you can select pets. (I have been told this is a flaw and is being corrected.) 1) Currently you can add unlimited amounts of pets, I would like to be able to limit the number of pets. I don’t need 1 guest and 20 pets in my home. 2) If you are trying to adjust a reservation, the pet fee is not visible to select. Please add this option. Guests often forget to add their pet or think that ESA are included under the Support Animal Guidelines and the are not, therefore adjustments must be made manually.

Patty Deutmeyer 1 day ago

💡 Feature Request

More AI Agent Control Options

We would like to request additional controls for the AI Agent to give property managers more flexibility in managing guest communications. The ability to disable the AI agent for a specific reservation. The ability to disable it for a specific period during a specific reservation. The option to decide whether a delayed AI draft should be canceled or still be sent.

Gasper Bulhoes 7 days ago

2

💡 Feature Request

Allow multiple guest email addresses on a reservation so automated messages (e.g., check-in instructions) are sent to all guests

As a short-term rental host managing multiple Airbnb and VRBO listings, I frequently have reservations where more than one guest on the same booking needs to receive automated communication—especially check-in instructions. Currently, iGMS only supports one guest email per reservation. Automated messages (welcome, check-in, pre-arrival, checkout, etc.) are sent only to the primary guest email synced from Airbnb/VRBO/Booking.com. Other guests on the same reservation do not receive these messages automatically. This creates a gap in guest experience and forces me to manually forward or re-send check-in instructions to additional guests for every booking, which is inefficient and error-prone. What I need On each reservation, be able to add additional guest email addresses (e.g., 1–3 extra emails) alongside the primary guest email. When automated messages are sent (via triggers or scheduled templates), iGMS should: Send the message to all guest emails on that reservation, or Provide an option like “Send to all guests on this reservation” when configuring automated messages. At minimum, this feature should support: Multiple guest emails for check-in instructions (the most critical message). Optionally extend to all automated guest messages (welcome, pre-arrival, checkout, review requests). Example use case Booking: 3 guests on the same reservation (primary guest + 2 extra guests). Primary guest email: primary@example.com Extra guest emails: extra1@example.com, extra2@example.com When the check-in instructions message is triggered (e.g., “On check-in day”), all three emails receive the same message automatically. Benefits Improves guest experience: all travelers get clear, timely check-in information. Reduces host workload: no need to manually forward check-in emails per booking. Makes iGMS more competitive with platforms that support multiple guest contacts per reservation. I’d appreciate this feature being considered for future versions of iGMS.

Guntis Stirna 7 days ago

💡 Feature Request

Message Reminders for Unanswered Conversations

Introduce a message reminder system similar to Gmail's "Nudge" feature to help users avoid forgetting to respond to guest messages. Problem: Users managing multiple conversations may occasionally overlook messages that require a response. This can lead to delayed guest communication, lower response rates, and missed booking opportunities. Proposed Solution: Add the ability to set reminders on individual conversations. When a reminder is due, the conversation would reappear prominently in the inbox and/or generate a notification to remind the user to follow up.

Gasper Bulhoes 10 days ago

💡 Feature Request

Display who performed the action after the date/time in the chat.

Currently in a thread, each guest, AI, or team member message shows the date/time sent and by whom (for example: “Jan 1, 1:00 PM by John Joe”). However, automated template messages and reservation alterations created or accepted currently show the date/time only, without showing who performed the action. I’d love for these activities — along with any other thread actions — to also display who performed the action after the date/time, so all thread activity has consistent attribution.

James Gray 17 days ago

💡 Feature Request

Direct Booking Price Comparison Widget

do you all have plans to add the "Direct Booking Price Comparison Widget", where you can show airbnb, and vrbo total prices along with the direct book price on our websites? to help drive more business to our local site versus airbnb/vrbo/booking. here is an example -> https://warrenbeachrentals.com/property-details/share-my-lowecation/?fbclid=IwY2xjawR5M91leHRuA2FlbQIxMABicmlkETFpdEV6RXJ4R0tFU0hWbk5lc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHjkedt7DAh3uVrbYaHYdIjLcDBv3h_wbKQ0KzHIhtRrFpLPO3oc4KfSS7_nn_aem_lpzyXy7Qc6UEqjqrJ10YJw

Bryan Overton 24 days ago

💡 Feature Request

Rotate weekly 1st priority cleaner for a property

I want to be able to rotate the list weekly so each cleaner has a chance to be allocated cleans as no.1 cleaner. I share cleans evenly at some properties. IGMS told me this wouldn't be a problem, but it is. It cancels all previously accepted cleans from the prior no.1 and gives them to the new no.1. It should only give any new cleans, or not accepted cleans to the new no.1 when I change it. Please fix! Thanks!

Daniel Kogoy 28 days ago

💡 Feature Request

Make Templates Available for New Listings Automatically

When a new listing is grouped to a property, the message templates are not automatically made available for it. This is easy to miss and can result in guests not receiving their templates. Please change this so that any time a new listing is added to a group, it is automatically added to the “Available for” list of all templates.

Santiago Mayaud 30 days ago

💡 Feature Request