The AI assistant

Ask Reynt is the console’s built-in assistant. Open it with the Ask Reynt… button in the top bar or Cmd/Ctrl + J — it docks as a panel on the right, so you can keep working while you talk to it. It reads your tenant’s live data to answer questions, and it can prepare changes for you — but it never changes anything on its own: every change is shown as a proposal card that you review and confirm first.

The panel

The panel is the chat, and only the chat. Two related things sit next to it:

• AI activity — the icon beside the notification bell in the top bar opens a tray of running and recently finished AI workflows (imports, content generation, translations). Watch progress and open results for review there instead of waiting on the page that started them; a badge shows how many runs are in flight or awaiting review. Because it’s a separate tray, you can keep an eye on a run while you carry on chatting.
• Help — written guidance for the page you’re on, opened by the Help button in that page’s header. It slides over the chat inside the same panel, so it stays beside the content it describes; Back to chat returns you.

The Ask AI entry at the top of the command palette (Cmd/Ctrl + K) hands your typed question straight to the chat.

Chat, and what it’s talking about

There is one conversation, and it always knows what you’re looking at.

When you’re on a record — a booking, a request, a listing, an invoice, a guest, an owner, an inbox thread, or a storefront page — a small chip appears above the message box naming that record. Anything you send while the chip is there can say “this booking” and skip the reference.

The chip is a hint, not a wall:

• Remove it with its × if your question isn’t about that record. Nothing else changes — the assistant can do exactly as much either way.
• Leave it and ask something else anyway. A tenant-wide question (“how was revenue last month?”) asked from a booking page is still answered as a tenant-wide question.
• Add more with + Add context to put several records in front of the assistant at once — for example a booking and the listing you’re thinking of moving it to.

Sent messages keep the chips they were sent with, so the transcript shows exactly which questions carried context and which didn’t.

The Ask about this booking / listing / page action in a record’s header just opens the chat — the chip is already there.

Conversation history is one list. If a chip is attached, the history menu offers to show only the conversations that were about that record.

What it can answer

The chat reads from your real data, so answers cite actual records rather than generic advice. It can look up and summarise:

• bookings, requests and offers, and their activity
• listings, prices, and availability — including “is this place free 3–7 August?”, answered with the booked and blocked stretches and the free gaps between them
• what a specific property actually has — its amenities, tags, attributes and distances, its extras and discounts, its seasonal stay rules, and whether its imported calendar feeds are still syncing
• why a listing is not publishable yet, item by item, with the tab that fixes each
• customers and owners
• invoices and payments, and the tax rules behind their lines — city/tourist tax and VAT rates
• cancellation policies, and what cancelling a specific booking would refund
• inbox conversations
• promo codes and storefront pages
• reports for a period you name — the revenue summary, revenue over time, the per-listing and per-booking breakdowns, and the commission review. These come from the same source as the console’s Reports page, so the numbers it quotes match what you see there
• dashboard figures (all-time) and occupancy reports for a period you name
• listings via smart search (“a sea-view place that allows dogs”)

Owner banking and tax details are never shared with the AI — those fields stay masked.

What it can do (with your confirmation)

When you ask for a change, the assistant prepares it and shows a proposal card describing exactly what will happen. Nothing runs until you confirm, and confirmed actions land in the same audit trails as manual ones. It can propose, among other things:

• Bookings — confirm, cancel, or close out a booking. A cancellation card names the policy behind the refund and shows both the policy entitlement and what the guest actually gets back
• Requests & offers — create a request, prepare and send an offer, publish or decline a request, or draft a whole multi-option offer with AI from the request’s captured wishes
• Availability — block or unblock dates
• Listings — update listing details, manage prices, assign an owner, or generate listing content with AI
• Invoices & payments — issue an invoice, mark it paid, cancel it, create a credit note, or mark a payment transfer as paid
• Inbox — draft a reply, assign a conversation, or change its status
• People — create or update customers and owners
• Promotions — create or disable a promo code
• Storefront — generate a new page section or edit an existing one

Cost

On the platform key, the assistant has its own generous daily token allowance, separate from the AI-workflow limits described in AI overview. Repeated context is cached and weighted cheaply, so normal day-to-day use stays well inside it. With your own API key connected there is no platform limit — usage is billed to your provider account directly.