What we mean by AI-native

Resbit is booking software first. AI is part of how guests book, how your phone gets answered, and how your team gets work done — not a chatbot you wire up with Zapier.

For a hot spring, campground, or resort, that means checking real availability, following your cancellation policy, handing off to a person when something is outside the rules, and leaving an audit trail. A generic chat widget cannot do that. Software that already has your inventory, pricing, and policies can.

Missed calls and full calendars already cost you bookings. The assistant, wait-list, phone agent, and staff automations live in one product so you do not have to stitch them together.

The AI booking assistant

The AI booking assistant lives on your public booking page. Guests can ask what you offer, search for openings across your services, and add items to a cart. They still review everything and check out on their own — the assistant does not charge a card or confirm a booking without them.

Checkout stays on the booking page, with the same policies and payment flow as a guest who never used the assistant.

When a guest needs something the assistant cannot handle — a special arrangement, a question outside your public offerings, or something a person has to decide — it forwards the conversation to your staff inbox with a summary and contact details. Your team picks up from there instead of asking the guest to start over.

AI-powered wait-list

When you are booked up, the next guest still wants a specific date, party size, and service. The wait-list connects to the booking assistant: if they cannot find an opening, they can join for what they asked for instead of refreshing your booking page all week.

When a cancellation frees a matching spot, Resbit notifies wait-listed guests by text and phone and gives them a window to confirm and book. Slots do not sit empty while your team manually works down a spreadsheet. The matching, notification, and hold logic run inside the same reservation system that took the original booking.

AI phone agent for inbound calls

Some guests call instead of using the booking page. The AI phone agent answers inbound calls with a greeting you configure, handles common questions, and can route or escalate based on your voice settings. Staff can watch the live transcript and take over the call at any time.

That covers the Saturday 7 PM call when two people are already checking guests in at the counter.

AI employees through agent integrations

Operators also want automations that can do staff work: look up a reservation, add a note, check the inbox, respond to a recurring report.

Agent integrations let you issue API keys for tools like Grok, Cursor, or your own automations. Each key acts as a staff user with a role you assign — employee, manager, or owner — and uses the same APIs as the web app. Permissions, audit logs, and revocation work the way they do for people on your team. We wrote the OpenAPI spec at /api/docs so agents can see the same routes the web app uses.

Each key is limited by the same role checks as a person on your team. The model does not get extra permissions because it asked.

Getting access control right

If you give an AI too much access, it will use it. Each integration in Resbit is scoped to what that job requires.

At the database layer, row-level security isolates each business. Whether access comes through Data Connect, the AI Consultant, or an agent API key, queries run in a tenant context that cannot cross into another organization's data. That is not a product policy we ask models to follow. It is enforced in Postgres.

Different integrations get different capabilities:

• Read-only paths. Data Connect and the AI Consultant mint short-lived, read-only credentials. They can inspect your schema and run SELECT queries — not insert, update, or delete. Connect links expire on a schedule you choose, and you can revoke them at any time.
• Limited write paths. The public booking assistant can search availability and build a cart, but it cannot complete checkout or take payment. Agent API keys inherit staff RBAC: an employee key cannot call manager-only routes, and only owners can mint owner-level keys.
• Broader staff permissions. When you need an automation to do more — adjust settings, run reports, manage inbox workflows — you assign a higher role to the key. You can see what a key can do and revoke it from Settings.
• Session-scoped integration access. Some tools need context outside the database. When you start an AI Consultant session, Resbit can also grant read-only access to your connected Stripe account — payment intents, charges, payouts, disputes, and balance. The AI cannot create charges, issue refunds, or change Stripe settings. That access lives only for the active session. End the session or leave the page and the credentials are revoked immediately, so nothing sensitive can leak into a long-lived prompt or tool configuration.

The booking assistant, the phone agent, and staff automations can sit in the same product without sharing one giant set of credentials.

Your data, available to your tools

Resbit's Data Connect gives you read-only Postgres access to your own schema — reservations, customers, payments, line items — so you can point a BI tool, a script, or an analysis workflow at real data. We wrote about this in Owning Your Data. Short-lived connect links are useful when you want a model to look at your operation without exporting a CSV every time.

Guest assistants, phone agents, and staff automations read the same reservations and customers, with the access limits above applied at each layer.

How we decide what to ship

We run Resbit on our own properties and with close partners. Every AI feature goes through the same filter as everything else in the product: would we turn this on behind our own front desk?

In practice:

• Smallest access that does the job. RLS, read-only connect links, role-based agent keys, and session-bound Stripe access.
• Checkout stays with the guest. The assistant can recommend and fill a cart. Payment still happens on the booking page.
• Staff can take over. Live call takeover, inbox handoffs, and revocable agent keys.
• It uses your live setup. Services, resources, policies, and availability — not a FAQ pasted in last season.
• One product. Booking, wait-list, voice, and staff automations share the same calendars, customers, and reports.

Hours, availability, wait-list texts, and after-hours calls are the work the software should do. Your staff still handles everything else.

Get started

AI booking assistant, wait-list, voice, and agent integrations are available in Resbit today. See the full platform on our features page, or request a demo to walk through how these tools would work for your property.

Questions? Reach me at spencer@resbit.io.

What we mean by AI-native

Resbit is booking software first. AI is part of how guests book, how your phone gets answered, and how your team gets work done — not a chatbot you wire up with Zapier.

For a hot spring, campground, or resort, that means checking real availability, following your cancellation policy, handing off to a person when something is outside the rules, and leaving an audit trail. A generic chat widget cannot do that. Software that already has your inventory, pricing, and policies can.

Missed calls and full calendars already cost you bookings. The assistant, wait-list, phone agent, and staff automations live in one product so you do not have to stitch them together.

The AI booking assistant

The AI booking assistant lives on your public booking page. Guests can ask what you offer, search for openings across your services, and add items to a cart. They still review everything and check out on their own — the assistant does not charge a card or confirm a booking without them.

Checkout stays on the booking page, with the same policies and payment flow as a guest who never used the assistant.

When a guest needs something the assistant cannot handle — a special arrangement, a question outside your public offerings, or something a person has to decide — it forwards the conversation to your staff inbox with a summary and contact details. Your team picks up from there instead of asking the guest to start over.

AI-powered wait-list

When you are booked up, the next guest still wants a specific date, party size, and service. The wait-list connects to the booking assistant: if they cannot find an opening, they can join for what they asked for instead of refreshing your booking page all week.

When a cancellation frees a matching spot, Resbit notifies wait-listed guests by text and phone and gives them a window to confirm and book. Slots do not sit empty while your team manually works down a spreadsheet. The matching, notification, and hold logic run inside the same reservation system that took the original booking.

AI phone agent for inbound calls

Some guests call instead of using the booking page. The AI phone agent answers inbound calls with a greeting you configure, handles common questions, and can route or escalate based on your voice settings. Staff can watch the live transcript and take over the call at any time.

That covers the Saturday 7 PM call when two people are already checking guests in at the counter.

AI employees through agent integrations

Operators also want automations that can do staff work: look up a reservation, add a note, check the inbox, respond to a recurring report.

Agent integrations let you issue API keys for tools like Grok, Cursor, or your own automations. Each key acts as a staff user with a role you assign — employee, manager, or owner — and uses the same APIs as the web app. Permissions, audit logs, and revocation work the way they do for people on your team. We wrote the OpenAPI spec at /api/docs so agents can see the same routes the web app uses.

Each key is limited by the same role checks as a person on your team. The model does not get extra permissions because it asked.

Getting access control right

If you give an AI too much access, it will use it. Each integration in Resbit is scoped to what that job requires.

At the database layer, row-level security isolates each business. Whether access comes through Data Connect, the AI Consultant, or an agent API key, queries run in a tenant context that cannot cross into another organization's data. That is not a product policy we ask models to follow. It is enforced in Postgres.

Different integrations get different capabilities:

• Read-only paths. Data Connect and the AI Consultant mint short-lived, read-only credentials. They can inspect your schema and run SELECT queries — not insert, update, or delete. Connect links expire on a schedule you choose, and you can revoke them at any time.
• Limited write paths. The public booking assistant can search availability and build a cart, but it cannot complete checkout or take payment. Agent API keys inherit staff RBAC: an employee key cannot call manager-only routes, and only owners can mint owner-level keys.
• Broader staff permissions. When you need an automation to do more — adjust settings, run reports, manage inbox workflows — you assign a higher role to the key. You can see what a key can do and revoke it from Settings.
• Session-scoped integration access. Some tools need context outside the database. When you start an AI Consultant session, Resbit can also grant read-only access to your connected Stripe account — payment intents, charges, payouts, disputes, and balance. The AI cannot create charges, issue refunds, or change Stripe settings. That access lives only for the active session. End the session or leave the page and the credentials are revoked immediately, so nothing sensitive can leak into a long-lived prompt or tool configuration.

The booking assistant, the phone agent, and staff automations can sit in the same product without sharing one giant set of credentials.

Your data, available to your tools

Resbit's Data Connect gives you read-only Postgres access to your own schema — reservations, customers, payments, line items — so you can point a BI tool, a script, or an analysis workflow at real data. We wrote about this in Owning Your Data. Short-lived connect links are useful when you want a model to look at your operation without exporting a CSV every time.

Guest assistants, phone agents, and staff automations read the same reservations and customers, with the access limits above applied at each layer.

How we decide what to ship

We run Resbit on our own properties and with close partners. Every AI feature goes through the same filter as everything else in the product: would we turn this on behind our own front desk?

In practice:

• Smallest access that does the job. RLS, read-only connect links, role-based agent keys, and session-bound Stripe access.
• Checkout stays with the guest. The assistant can recommend and fill a cart. Payment still happens on the booking page.
• Staff can take over. Live call takeover, inbox handoffs, and revocable agent keys.
• It uses your live setup. Services, resources, policies, and availability — not a FAQ pasted in last season.
• One product. Booking, wait-list, voice, and staff automations share the same calendars, customers, and reports.

Hours, availability, wait-list texts, and after-hours calls are the work the software should do. Your staff still handles everything else.

Get started

AI booking assistant, wait-list, voice, and agent integrations are available in Resbit today. See the full platform on our features page, or request a demo to walk through how these tools would work for your property.

Questions? Reach me at spencer@resbit.io.