Use cases
AI guest operations for every stage of a growing vacation-rental portfolio.
RentaraAI drafts, triages, and escalates guest communication for operator review and approval — covering hosts across 1–3, 4–9, 10–29, and 30+ active-property bands. Outbound guest messages wait for a human to approve them. Per-property context + a per-property audit trail travel with every action.
Portfolio segments
1–3 · Active-property operator
1–3 Properties
1–3 Properties · $15 USD/property/month · 14-day evaluation on one property · no charge during the pilot · explicit price and terms consent required before any paid subscription begins · no automatic conversion from pilot to paid.
Verified use cases
- 1–3 active properties — the on-the-ground host who is still answering messages themselves.
- Guest question routing — what time is check-in, where is parking, where is the lockbox code.
- Property-by-property check-in instructions, updated in one place and broadcast on the channel you operate.
- Maintenance intake — drafted for review with severity grading by RentaraAI.
- Post-stay follow-up — review ask, supply restock, payout summary, all drafted on per-property context.
- Per-property house rules broadcast — the rules you set as a host.
- Per-property context applied on every draft — address, bedrooms, in-stay date, latest 5 turns of the guest thread.
Approval-first flow on 1–3 Properties — guest message arrives, property + reservation context evaluated, draft prepared, flagged issue escalates, you review, you approve or edit, your action is logged to the per-property audit trail:
- Guest message arrives through a live RentaraAI channel — Direct booking requests or Email.
- Property + reservation context evaluated per call site — address, city, bedrooms, in-stay date, the latest 5 turns of the guest thread.
- Draft prepared — composed in your tone, with your style block and the property’s operational house rules.
- What escalates: anything you mark off-limits — refund math, late-stay complaints, anything asking to bend house rules or skip payment.
- You review, approve or edit; your action is logged in the per-property audit trail with timestamp + named operator.
4–9 · Growing host
4–9 Properties
1–3 Properties: $15 USD/property/month · 4–9 Properties: $10 USD/property/month · 10–29 Properties: $7 USD/property/month · 30+ Properties: $5 USD/property/month.
4–9 Properties · $10 USD/property/month · 14-day evaluation on one property · no charge during the pilot · explicit price and terms consent required before any paid subscription begins · no automatic conversion from pilot to paid.
Verified use cases
- 4–9 active properties — growing hosts who need repeatable guest operations.
- Per-property configuration and approval-first guest communication.
- Shared workflows and a per-property audit trail for every action.
Approval-first flow on 4–9 Properties — the selected USD band rate applies to every active property, and the exact monthly total is shown before any paid activation.
- Active properties are counted for the billing period.
- Property and reservation context is evaluated before drafting.
- You review, approve, edit, or refuse each outbound message.
- The selected 4–9 band rate applies to every active property.
- Cancel from your dashboard at any time; no email or call is required.
10–29 · Multi-property manager
10–29 Properties
1–3 Properties: $15 USD/property/month · 4–9 Properties: $10 USD/property/month · 10–29 Properties: $7 USD/property/month · 30+ Properties: $5 USD/property/month.
10–29 Properties · $7 USD/property/month · same 14-day one-property pilot · no card · no charge during the pilot · no automatic conversion · explicit consent required before paid activation.
Verified use cases
- 10–29 active properties — multi-property managers running 2+ doors at once.
- Simultaneous property messages — drafts each reply with the right per-property context.
- Per-property configuration — house rules, style block, escalation routing per property, multi-manager routing per address.
- Named-operator routing — escalate to the operator on shift, not a queue.
- Multi-manager workflows — escalation routing configurable per address.
- Per-property audit trail — exportable for your compliance team.
- PMS connection on request — Hostaway, Guesty, Lodgify, OwnerRez, configured per address and per PMS.
Approval-first flow on 10–29 Properties — the same one-property, 14-day pilot as every band. No card and no charge during the pilot; the selected USD rate and exact monthly total are shown, and paid activation starts only after explicit consent:
- Start with one selected pilot property while the 10–29 band rate remains available for the full portfolio.
- Per-property configuration drives the draft — house rules, style block, multi-manager escalation routing per address.
- Operator reviews each flagged item; approve, edit, or refuse — your action logs to the per-property audit trail with timestamp + named operator.
- Review the exact $7 USD/property/month band total and published terms before deciding whether to activate paid service.
- If you continue after the pilot, explicitly consent before paid activation; there is no automatic conversion.
30+ · Property-management team
30+ Properties
30+ Properties · $5 USD/property/month.
30+ properties · $5 USD/property/month · same 14-day one-property pilot · no automatic conversion · explicit consent required.
Verified use cases
- 30+ active properties — the same flat $5 USD/property/month band applies to every active property after explicit consent.
- House rules + style block per address, with multi-manager escalation routing.
- PMS that ships for 30+ Properties — August + igloohome smart locks included; Hostaway, Guesty, Lodgify, OwnerRez on request.
- 30+ properties use the same self-serve pilot and $5 USD/property/month rate.
- Month-to-month USD billing, dashboard cancellation, and the same active-property definition used across every band.
- Named-operator escalation routing — the human stays the licensee of record on the markets that require it.
- Self-serve monthly USD checkout follows explicit price-and-terms consent.
Approval-first flow for 30+ properties — the same explicit-consent pilot and flat USD band pricing apply:
- Enter 30 or more active properties and review the exact $5 USD/property/month calculation before consent.
- Review the exact monthly total for your active-property count and the published billing terms.
- Attach the required payment method and explicitly consent before the paid subscription is created.
- Outbound guest communication waits for operator approval; the named-operator escalation routes the flagged issues to the human on shift.
- Renewal cadence, cancellation, and active-property definition follow the published monthly USD terms.
Outbound guest communication waits for operator approval — never automatic, never silent.
Which fits me?
Four bands, end-to-end.
The fields below come from the same canonical pricing + integrations the rest of the site reads. All four bands use the same self-serve calculator and checkout flow.
1–3 Properties
1–3 Properties
1–3 Properties · $15 USD/property/month
4–9 Properties
4–9 Properties
4–9 Properties · $10 USD/property/month
10–29 Properties
10–29 Properties
10–29 Properties · $7 USD/property/month
30+ Properties
30+ Properties
30+ Properties · $5 USD/property/month
| Verified field | 1–3 Properties · 1–3 Properties | 4–9 Properties · 4–9 Properties | 10–29 Properties · 10–29 Properties | 30+ Properties · 30+ Properties |
|---|---|---|---|---|
| Portfolio size | 1–3 Properties · $15 USD/property/month | 4–9 Properties · $10 USD/property/month | 10–29 Properties · $7 USD/property/month | 30+ Properties · $5 USD/property/month |
| Purchase path | Self-service — Sign up, choose 1–3 Properties, complete the 14-day pilot, then convert on price + terms consent. | Self-service — Sign up, choose 4–9 Properties, review the band-locked monthly amount, confirm explicit price + terms consent. | Self-service — Sign up, choose 10–29 Properties, review the band-locked monthly amount, confirm explicit price + terms consent. | Self-service — Sign up, choose 30+ Properties, review the exact monthly amount, and confirm explicit price + terms consent. |
| Guest-message drafting | ✓ — drafts prepared on per-property context. | ✓ — drafts prepared on per-property context. | ✓ — drafts prepared on per-property context. | ✓ — drafts prepared on per-address context. |
| Approval before send | ✓ — operator approves or edits; no automatic send. | ✓ — operator approves or edits; no automatic send. | ✓ — operator approves or edits; no automatic send. | ✓ — operator approves or edits; no automatic send. |
| Escalation routing | Named-operator-only routing — one human at a time. | Named-operator routing with shared workflows across the band. | Per-property multi-manager routing, configured per address. | Per-property multi-manager routing, configured per address. |
| PMS availability | PMS integrations on request — Hostaway, Guesty, Lodgify, OwnerRez. | PMS integrations on request — Hostaway, Guesty, Lodgify, OwnerRez. | PMS integrations on request — Hostaway, Guesty, Lodgify, OwnerRez. | Smart locks: August + igloohome included. PMS on request: Hostaway, Guesty, Lodgify, OwnerRez. |
| Multi-manager workflows | Not in scope — one named operator on a 1–3 Properties account. | Shared workflows across active properties; multi-manager routing is not required for this band. | Configured per address — multi-manager per property, escalation routing per named human. | Configured per address — multi-manager per property, escalation routing per named human. |
| Audit trail | Per-property audit trail — every draft, every approve, every send. | Per-property audit trail — every draft, every approve, every send. | Per-property audit trail — every draft, every approve, every send. | Per-property audit trail — every draft, every approve, every send. |
| Commercial model | Banded pilot — 14-day evaluation on one property, then the selected USD rate applies after explicit consent. | Banded subscription after explicit price + terms consent on the selected USD rate. | Banded subscription after explicit price + terms consent on the band-locked subscription. | Banded subscription after explicit price + terms consent on the band-locked subscription. |
| CTA | /onboarding?units=1&source=pricing_starter | /onboarding?units=4&source=pricing_starter | /onboarding?units=10&source=pricing_growth | /onboarding?units=30&source=pricing_custom |
Status legend
The four pills below mirror the categories the integrations directory surfaces, and each pill carries the same glyph + label the directory shows.
- Booking platforms·planned·2 on plan, 0 on request
- Booking platforms·planned·2 on plan, 0 on request
- Booking platforms·planned·2 on plan, 0 on request
- Booking platforms·planned·2 on plan, 0 on request
- Property-management systems·planned·2 on plan, 0 on request
- Property-management systems·planned·2 on plan, 0 on request
- Property-management systems·planned·2 on plan, 0 on request
- Property-management systems·planned·2 on plan, 0 on request
- Messaging & email·planned·2 on plan, 0 on request
- Messaging & email·planned·2 on plan, 0 on request
- Messaging & email·planned·2 on plan, 0 on request
- Messaging & email·planned·2 on plan, 0 on request
- Smart locks & access·planned·2 on plan, 0 on request
- Smart locks & access·planned·2 on plan, 0 on request
- Smart locks & access·planned·2 on plan, 0 on request
- Smart locks & access·planned·2 on plan, 0 on request
Workflow examples
Four scenarios, one approval-first flow.
Each scenario follows the incoming → draft → escalation → operator-review → logged pattern. Outbound guest communication waits for operator approval; the desk never sends automatically.
Early check-in request
Guest asks to arrive five hours before the published check-in window.
- Incoming: guest message lands on a live RentaraAI channel — Email or Direct booking requests.
- Draft prep: the desk pulls the reservation, the published check-in window, and the per-property house rules; it composes the apology + the asks.
- What escalates: any guest push-back against the published check-in time; the desk hands that to the named operator with full thread + per-property context.
- What the operator reviews / approves: the police reply, the offered alternative (later arrival, paid early check-in if applicable), the relief line, and the close-out sign-off.
- What is logged: the per-property audit trail records who drafted, who approved, who sent, and when — exportable for your compliance review.
2:00 a.m. lockout
Guest is locked out at 2 a.m. and the support line is the operator or a contracted crew.
- Incoming: guest message arrives; the channel reads the priority + the per-property address.
- Draft prep: the desk pulls the active reservation, the lock vendor status, the per-property house rules, and the operator-on-shift routing.
- What escalates: anything that crosses a per-property rule (refund math, late-stay complaints, anything asking to bend house rules or skip payment) — those escalate to the human.
- What the operator reviews / approves: the priority reply, the dispatch routing, the relief reply, and the close-out sign-off.
- What is logged: every action is logged in the per-property audit trail with timestamp + named operator + the relief reply that went out.
Maintenance issue during a stay
Guest reports a clogged shower or a broken appliance mid-stay; the relief reply is the top priority.
- Incoming: guest message arrives; the channel reads the priority + the per-property address.
- Draft prep: the desk pulls the active reservation, the maintenance roster, the per-property context (house rules, vendor list, named operator), and composes the relief + the vendor dispatch.
- What escalates: anything that crosses a per-property rule (refund math, late-stay complaints, anything asking to bend house rules or skip payment) — those escalate to the human.
- What the operator reviews / approves: the relief reply, the dispatch decision, the optional credit / comp if relevant, and the close-out sign-off.
- What is logged: every action is logged in the per-property audit trail with timestamp + named operator.
Post-checkout follow-up
Payout summary, supply restock, review ask — the standard post-stay check.
- Incoming: the channel reads — the post-stay pattern fires on the published check-out window.
- Draft prep: the desk pulls the reservation, the per-property house rules, the supply check, and composes the relief + the optional review-ask.
- What escalates: anything that crosses a per-property rule (refund math, late-stay complaints, anything asking to bend house rules or skip payment) — those escalate to the human.
- What the operator reviews / approves: the post-checkout reply, the optional review-ask, the supply-restock note, and the close-out sign-off.
- What is logged: every action is logged in the per-property audit trail with timestamp + named operator.
Outbound guest communication waits for operator approval — never automatic, never silent.
Integrations
Bookings, PMS, comms, locks — same status on /integrations.
Each row below reads from the canonical integrations registry. Status pills carry the same glyph + label the directory shows; “Beta” and “Planned” are not presented as fully live.
Booking platforms
Included on 1–3 Properties + 4–9 Properties + 10–29 Properties + 30+ Properties
Messaging & email
Included on 1–3 Properties + 4–9 Properties + 10–29 Properties + 30+ Properties
Booking platforms
Available across all bands or on request depending on the integration.
Booking platforms
Available across all bands or on request depending on the integration.
Booking platforms
Available across all bands or on request depending on the integration.
Property-management systems
Available across all bands or on request depending on the integration.
Property-management systems
Available across all bands or on request depending on the integration.
Property-management systems
Available across all bands or on request depending on the integration.
Property-management systems
Available across all bands or on request depending on the integration.
Messaging & email
Available across all bands or on request depending on the integration.
Messaging & email
Available across all bands or on request depending on the integration.
Messaging & email
Available across all bands or on request depending on the integration.
Smart locks & access
Available across all bands or on request depending on the integration.
Smart locks & access
Available across all bands or on request depending on the integration.
Smart locks & access
Available across all bands or on request depending on the integration.
Smart locks & access
Available across all bands or on request depending on the integration.
Trust + control
The four facts every portfolio a Human stays in charge of.
Same facts the rest of the site carries on /security and /privacy. No marketing claims added — only what the canonical product copy surfaces.
Outbound guest messages wait for operator approval.
Nothing leaves the account without your click. Drafts land in your inbox; you approve or edit; we send. Anything you mark off-limits the desk never sends — it escalates to the named human with the full context.
Per-property audit trail — exportable.
Every action is logged per property — who drafted, who approved, who sent, and when. The audit trail is yours to export, review, and share with your compliance team.
Data-minimization posture.
Guest and reservation data is encrypted at rest and in transit. Access is scoped per account with the principle of least privilege — every AI call is narrowed, per call site, to the data that call needs.
City rules are not legal advice.
On the markets where the named operator must stay a human, the desk escalates rather than interprets. Verify the rules that apply to your address with the city and a licensed attorney — RentaraAI is a configurable workflow and checklist layer.
Frequently asked
Six qualifying questions, no soft answers.
Same canonical facts the rest of the site carries on /faq. Outbound guest communication waits for operator approval; 30+ users use the same self-serve calculator and checkout.
Yes — the 14-day evaluation runs on one property with no card and no charge during the pilot. Afterward, the selected USD rate applies to every active property, and explicit price-and-terms consent is required before any paid subscription begins.
The selected rate applies to every active property: $15 USD for 1–3, $10 USD for 4–9, $7 USD for 10–29, and $5 USD for 30+ properties.
No. The drafts the desk prepares are queued for operator review; nothing leaves the account without your click. Anything you mark off-limits the desk never sends — it escalates to the named human with the full thread + per-property context. Outbound guest communication waits for operator approval; the desk never sends automatically.
On 10–29 Properties and 30+ Properties, escalation routing is configurable per-property and per-address; multi-manager routing is the standard shape. On 1–3 Properties the band is single-operator — there is one human reviewing every flagged item, not multi-manager queues.
You use the same 14-day, one-property pilot and self-serve monthly checkout. The 30+ Properties band is $5 USD per active property/month, applied to every active property after explicit price-and-terms consent.
Booking: Direct booking requests is native; Airbnb, Vrbo, and Booking.com are planned. PMS: Hostaway, Guesty, Lodgify, and OwnerRez are planned. Comms: Email is native; SMS, WhatsApp, and Airmsg are planned. Locks: August, Schlage, igloohome, and Yale are planned. The integrations directory at /integrations is the canonical list and stays in lockstep with the live status pills here.
Final choices
Pick the band that fits your portfolio shape today.
You can move up or stay as you grow — and the human approval flow follows you across bands. 30+ properties use the same self-serve checkout after explicit consent.
1–3 properties
Start a one-property pilot
10–29 properties
Start the 14-day pilot
30+ properties
Start the 14-day pilot