The assistant sits in every view of the console. It answers questions about your bookings, places, and numbers, takes you to the right screen — and prepares changes right up to the point where only your confirmation is missing.
No credit card required — after 14 days the trial ends by itself.
1 question
Instead of setting filters, switching views, and scanning lists
Countless actions
From a price change to an invoice — prepared, never executed
0 surprises
The assistant changes nothing without your confirmation
Reading, calculating, and proposing are its job. Executing is yours.
How many requests are open? What did the studio earn in July? Which places are free over Easter? The assistant reads bookings, places, invoices, and figures, and answers in a sentence — with a link to the screen where you carry on.
Adjust a price, block dates, issue an invoice, confirm a booking, send a reply: the assistant can prepare countless kinds of change. Each arrives as a card with the actual values filled in — only your click carries it out.
For a guest message, the assistant proposes a reply that already knows the booking behind it. You read it, adjust it, send it — or throw it away.
Setup questions are answered from the Reynt documentation rather than from thin air — with a pointer to the article it came from.
The assistant only sees what your account may see: every access is permission-checked on its own, and every request lands in the audit log. It always works inside the tenant you are currently in.
The same job, two routes through the console.
With the assistant
By hand
Find open requests
With the assistant
By hand
Change a season price
With the assistant
By hand
Reply to a guest message
With the assistant
By hand
Revenue for one place
With the assistant
By hand
Settle a setup question
With the assistant
By hand
Control
With the assistant
By hand
No command vocabulary, no syntax.
From “Ask Reynt” in the header or with ⌘ J — out of any view.
In plain sentences. The assistant knows which tenant you are working in.
When a change is involved, a card with the actual values appears before anything happens.
Only your click carries the change out. Discarding is just as quick.
Answers to questions that would otherwise take three screens
Changes arrive prepared, with the values already filled in
Reply drafts that know the booking context
Nothing is executed before you confirm it