What to ask your AI assistant about your portfolio

Start with the Listing audit check under Other checks, naming one property. Confirm the team, the paired Airbnb listing and the dates behind each figure. The useful result is a short list of causes with their evidence: visibility, clicks, conversion, availability, minimum stay, reviews and prices.

In this recorded example, a three-night minimum excluded shorter stays and the audit proposed changes to the cover photo, name and facilities. Ask which comparison supports each cause before acting. Booking.com’s peer group behind funnel figures and a comp set used for prices are different populations; the answer should name each one.

Your assistant may prepare a description or gallery plan with its own document and image tools. Photo counts or tags alone do not prove what an image shows: if it cannot inspect the photos, it should say so. The recorded audit prepares recommendations. Review the edits before applying them in the extranet or PMS; where the connector can send a supported PMS change, it must explain the change and get your confirmation first.

Keep the confirmed audit as a baseline. On a later check, compare the same property and dates, distinguish new data from an applied edit, and ask what changed rather than assuming every recommendation was carried out.

Use Compare Booking.com and Airbnb prices under Other checks, with one property and the same stay dates. Check the party size, room, currency, fees, taxes, cancellation terms and when each price was read before treating a difference as a price leak. For a reservation, use Explain a booking’s price to inspect the settings in place when it was made.

The fictional recording follows a discount and markup through to a guest price. Its figures describe that example, not every stay in your portfolio. A stored price is not a live quote. With public price checks enabled, the connector can read live stay quotes on Booking.com and Airbnb. If a fresh comparable quote is unavailable, the answer should say why and leave the live price unknown.

Review the proposed setting change in myDataValue, or in the PMS or RMS that owns it. The recording reads and explains prices; it does not apply a change.

Run the current Last-minute pricing workflow under Workflows. Start with the nights still open, then check whether a gap, a minimum stay or the price against similar places explains why they are hard to sell. Compare the same dates and party, and read the minimum price it names and how far under it a guest lands beside any suggested deal.

The fictional recording reviews one property’s next two weeks. Today’s workflow follows the current catalog’s steps and may return a different view. Live Booking.com comparisons and connected PMS or RMS reads depend on your team’s enabled access and stored key. Without a connected minimum price, the answer must say which limit it used instead.

The recording reads and proposes a change. Where your connection offers staging, your assistant can prepare a promotion for you to push in myDataValue. If pushing through the assistant is enabled too, it asks for your later confirmation of the preview. A supported connected PMS or RMS write is a separate request: the assistant explains the vendor, property, dates and values, gets your confirmation, then reads the change back. Your assistant runs any schedule; myDataValue does not schedule the question.