The supervisor

Nothing slips, and you can see why.

Automation is only worth having if you can trust it. Linkbase holds every reply for a window you control, refuses to guess when it isn't confident, and stops replying when a thread starts going in circles. Every word it said is on the record, with the reason it said it.

Try the AI Book a walkthrough

From the reply to the record

Automation is only worth having if you can trust it. Scroll to follow one conversation: the window every reply waits in, what happens when you reply yourself, the switches that stop it, what it does when it is unsure, how alerts reach you, and the record it leaves behind.

Step 1 of 6 · Hold

Every reply waits, and you can change your mind

Every auto-reply is held for a window before it goes out: two minutes by default, set per property from one minute to a day. At send time Linkbase checks again for mutes, a human reply and the booking status, so changing your mind really does stop it.

What's on screen

A reply waiting to send
The checks made again at send time
A muted thread, and nothing sent

Under the hood

The checks run when the reply is due, not when it was scheduled. That is what makes the window real rather than cosmetic.

Step 2 of 6 · Takeover

Reply yourself and the AI steps back. No toggle to remember.

Your reply cancels any pending AI send and pauses the AI on that conversation: thirty minutes by default, and anywhere from five minutes to a day. You choose whether the pause means staying silent, or carrying on drafting without sending.

What's on screen

Your reply, cancelling a pending send
The AI paused on that thread
Silent, or draft but do not send

Under the hood

Taking over is the signal. There is nothing to switch on first and nothing to switch back.

Step 3 of 6 · Switches

Four off switches that stack

The AI can be stopped at four independent levels: your plan, the account's reply mode, a single property and a single conversation. Muting replies and muting alerts are separate, so you can silence the AI on a thread and still hear if it goes wrong.

What's on screen

Your plan and the account reply mode
A single property and a single thread
Replies muted, alerts still on

Under the hood

Reply mode is off, draft only or auto. Any one of the four switches is enough to stop the AI sending.

Step 4 of 6 · Unsure

It will not guess when it is unsure

When the AI is not confident enough, it stops writing and sends a brief acknowledgement, parking the full draft for you to review. An upset guest blocks auto-send outright. After three escalated exchanges on the same topic, it stops auto-replying on that topic until a person steps in.

What's on screen

A short acknowledgement, the draft parked
An upset guest blocking auto-send
A thread that is going in circles

Under the hood

It recognizes when it is going in circles and gets out of the way, instead of answering a fourth time.

Step 5 of 6 · Alerts

One alert per conversation, on the channel you choose

Escalations reach you by email, SMS or push, and overnight too if that is what you want. Repeat escalations on a conversation add to a running count instead of piling up as notifications, and the needs-reply queue ages items out so it stays a queue.

What's on screen

An alert on your own channel
A running count, not a stream
A needs-reply queue you can clear

Under the hood

The needs-reply queue drops items after a week, or three days after checkout, and has an explicit clear action.

Step 6 of 6 · Record

Every word it said is on the record, with the reason

Each AI run records what it classified the message as, the guest-facing text it drafted, how confident it was, which tools it consulted and, when it held back, why. Messages show whether the AI sent them, you did, or you approved the AI's draft.

What's on screen

The record of one AI run
Who sent each message
The reason it held back

Under the hood

The record keeps what the AI said, not how it was prompted, and is kept for ninety days.

Step 1 of 6 · Hold

Every reply waits, and you can change your mind

What's on screen

A reply waiting to send
The checks made again at send time
A muted thread, and nothing sent

Under the hood

The checks run when the reply is due, not when it was scheduled. That is what makes the window real rather than cosmetic.

What it handles

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

Replies you wanted to stop
Ops
Every reply waits in a window you set, and changing your mind stops the send.
Taking over mid-thread
Ops
Reply yourself and the AI steps back. No toggle to remember.
An AI that guesses
Ops
When it's unsure, it sends a short acknowledgement and parks the draft for you.
The one message that matters
Ops
One live alert per conversation, by email, SMS or push, overnight too if you want.
What did the AI say?
Ops
Every reply recorded, with the reason it was sent or held back.
Reporting maintenance
Ops
Pushed straight to CIBO for your vendor to pick up.

Under the hood

How it actually works

1
Every reply waits, then is checked again
Auto-replies go out after a delay you set per property, two minutes by default. At send time Linkbase checks mutes, whether a person has replied, and the booking status again.
2
Taking over is the signal
Reply yourself and the AI pauses on that conversation, for thirty minutes by default, and any pending send is cancelled. You choose whether it stays silent or keeps drafting without sending.
3
It stops when it should
When it isn't confident, it sends a short acknowledgement and parks the full draft for you. An upset guest blocks auto-send, and after three escalated exchanges on a topic it stops replying on that topic.
4
Every reply leaves a record
Each run records how the message was classified, the text drafted, the confidence, the tools consulted and, if it held back, why. Messages show whether the AI sent them, you did, or you approved the AI's draft.

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 →

CIBO
Email
SMS
Push

The jobs next to this one

AI messagingIt reads your history, so it already knowsRead more→Smart accessA code per booking, scoped to the stayRead 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

Nothing slips, and you can see why.

From the reply to the record

Every reply waits, and you can change your mind

What it handles

Replies you wanted to stop

Taking over mid-thread

An AI that guesses

The one message that matters

What did the AI say?

Reporting maintenance

How it actually works

Every reply waits, then is checked again

Taking over is the signal

It stops when it should

Every reply leaves a record

Works with what you run

The jobs next to this one

See it on a real conversation