The data entry clerk

Your data, entered once, by nobody.

Nobody should re-type a portfolio into another tool. Connect once and your listings arrive, bookings follow within seconds, and replies go back to the channel your guest used.

Try the AI Book a walkthrough

From your system to the guest's thread

One connection brings your portfolio in, and a push-first pipeline keeps it true. Scroll to follow a booking: how you connect, how it arrives, what catches a miss, how a duplicate is prevented, and how the reply finds its way back to the channel the guest used.

Step 1 of 6 · Connect

One connection reaches thirty-plus systems

Linkbase connects through Calry, so a single connection reaches Hostaway, Guesty, Lodgify, OwnerRez, Hospitable and more, with your Airbnb, Vrbo and Booking.com reservations riding in underneath. You pick your system, authorize it, choose your listings, and your history imports in the background.

What's on screen

Picking your system
Choosing which listings come in
History importing in the background

Under the hood

Authorization is OAuth where your system supports it, or an API key where it does not. No developer, no CSV, no mapping spreadsheet. It is one aggregated connection, not a separate build for each system.

Step 2 of 6 · Arrive

A booking is correct within seconds of being made

The normal path is push, not poll. Your system sends a signed webhook when a reservation is created or changed, so the door code, the scheduled messages and the AI's context are right for a booking made four minutes ago.

What's on screen

A reservation made in your system
The webhook arriving in Linkbase
Door code, messages and AI context

Under the hood

Date changes and cancellations arrive the same way as new bookings, as updates, and are applied when they land.

Step 3 of 6 · Backstops

Three backstops catch what a webhook misses

An hourly sweep compares Linkbase with your system instead of trusting that every webhook arrived. A change fingerprint keeps the sweep cheap, and it still checks any stay arriving soon that has no door code. When your system reports its own sync finished, Linkbase re-imports to close the gap.

What's on screen

An hourly sweep against your system
A fingerprint that skips what did not move
Recovery after an outage window

Under the hood

The fingerprint covers dates, status, cancellation, room, guest contact and security requirements. Everything is refreshed every 24 hours anyway, spread out so a whole portfolio does not refresh at once.

Step 4 of 6 · Once

The same reservation never becomes two bookings

A reservation can arrive twice, once from a webhook and once from the sweep. A short-lived lock on each reservation, plus indexed lookups, means one booking and one door code. Imports are paced per system, so a big portfolio does not get you rate-limited out of your own PMS.

What's on screen

One reservation arriving from two directions
One booking and one door code
Pacing that suits each system

Under the hood

Systems throttle very differently, so each one has its own pacing. If the lock itself ever hiccups, the worst case is a little duplicate work, not sync stopping.

Step 5 of 6 · Replies

Replies go back to the channel the guest used

A guest messages on Airbnb and the thread arrives over the same connection. The reply lands in that Airbnb thread, or in Vrbo, Booking.com, email, SMS, WhatsApp or Messenger, whichever the conversation is. Guests are never pulled off the platform, and read state syncs back.

What's on screen

A guest message arriving on Airbnb
The reply, sent in the same thread
The booking already known to the AI

Under the hood

Only new messages are written, matched by message ID and by a content and time check that catches your own sends coming back. If the preferred channel is rejected, a fallback ladder tries the next. Attachments pass both ways.

Step 6 of 6 · Safeguards

A platform notice or a replay cannot fool the AI

A message whose sender cannot be positively identified is treated as a system message, never as a guest, so a platform notice is not read as a guest instruction. A replayed webhook cannot make the AI answer the same guest twice.

What's on screen

An unknown sender, set aside
A replayed webhook, answered once
Failed work kept, not lost

Under the hood

Work runs through managed queues, with retries and timeouts on every call to your system. Anything that keeps failing goes to a dead-letter queue instead of disappearing.

Step 1 of 6 · Connect

One connection reaches thirty-plus systems

What's on screen

Picking your system
Choosing which listings come in
History importing in the background

Under the hood

What it handles

Each of these used to be a task on someone's list. Here's what runs it now.

Re-typing your properties
Admin
Pick your listings and they import. No CSV, no mapping sheet.
Copying booking details
Admin
Guest names, dates, and phone numbers arrive with the reservation.
Changes and cancellations
Admin
Applied within seconds by webhook, with an hourly sweep behind it.
Updates that never arrived
Admin
A fingerprint check, a daily refresh and outage recovery close the gaps.
Answering in the wrong place
Admin
Replies go back to the thread, email, SMS or WhatsApp the guest used.
Pasting the guest app link
Admin
Written back into each reservation in your PMS automatically.
Writing house manuals
Admin
Drafted by AI from your own PMS data, for you to edit.
Occupancy in a spreadsheet
Admin
The dashboard does it, across the whole portfolio.

Under the hood

How it actually works

1
One connection, then walk away
Linkbase connects through Calry, so a single connection reaches 30+ property management systems. You authorize over OAuth, or paste an API key where OAuth is not offered, choose your listings, and the history imports in the background.
2
Push first, with backstops
Webhooks apply changes within seconds. An hourly sweep, a change fingerprint and missed-webhook recovery catch the rest. Your PMS stays the source of truth.
3
Replies go where the guest is
Airbnb, Vrbo and Booking.com threads arrive through the same connection, and replies go back in the same channel, so guests are never pulled off the platform.
4
Built so a duplicate or a replay does nothing
One reservation makes one booking and one door code. Senders that cannot be identified are treated as system messages, and failed work lands in a dead-letter queue instead of vanishing.

Connects to

Works with what you run

Your existing tools stay where they are. Linkbase connects to them instead of asking you to move.

See every integration →

Calry
30+ PMSs
Airbnb
Vrbo
Booking.com

The jobs next to this one

AI messagingIt reads your history, so it already knowsRead more→Screening & formsID checks, agreements and forms, trackedRead more→

See it on a real conversation

The live demo runs the same AI on a sample booking. Ask it what your guests ask you.

Try the AI Book a walkthrough

Your data, entered once, by nobody.

From your system to the guest's thread

One connection reaches thirty-plus systems

What it handles

Re-typing your properties

Copying booking details

Changes and cancellations

Updates that never arrived

Answering in the wrong place

Pasting the guest app link

Writing house manuals

Occupancy in a spreadsheet

How it actually works

One connection, then walk away

Push first, with backstops

Replies go where the guest is

Built so a duplicate or a replay does nothing

Works with what you run

The jobs next to this one

See it on a real conversation