Vanio monitors every message in both directions, alerts you with failure causes when sends don't reach guests, and automatically recovers messages blocked for containing links or contact details.

Guest Message Delivery Monitoring

Vanio now watches whether guest messages actually reach you — and whether your replies actually reach guests. If anything gets stuck or goes missing along the way, you'll hear about it right away instead of finding out from an unhappy guest.

What It Does

This feature adds a layer of protection that sits underneath your everyday messaging. While your inbox already flags unanswered messages, it couldn't catch a message that never arrived in the first place. Now Vanio actively monitors the full journey in both directions — inbound messages from guests and outbound messages from your team — and alerts you the moment something looks wrong. Think of it as a silent watchdog that keeps an eye on your message pipeline around the clock.

Getting Started

There's nothing you need to set up. Message delivery monitoring is active automatically for your account. Here's how to confirm everything is working and where to find your alerts:

Log in to your Vanio dashboard.
Go to Settings → Notifications.
Scroll to the Messaging Alerts section.

[Screenshot: Settings panel showing the Messaging Alerts section with delivery monitoring toggle]

Confirm that Delivery Monitoring is enabled. It's turned on by default.
Check that your preferred alert destination (email or Slack) is connected under Alert Channels.

[Screenshot: Alert Channels section showing email and Slack options]

That's it — Vanio is now watching your message flow. No further action is needed unless you want to adjust where alerts are sent.

How It Works

Vanio runs regular checks in the background, several times per hour, examining the flow of messages across all your properties. Here's what happens automatically:

Arrival checking: Vanio looks at when guest messages were sent versus when they showed up in your inbox. If there's an unusual gap — longer than what's normal for your account based on historical patterns — it flags that as a potential delay.
Silence detection: Vanio learns what a typical quiet period looks like for your portfolio (for example, how long gaps between messages usually run overnight or on slow days). If the silence extends far beyond your normal pattern, it treats that as a signal worth investigating.
Outbound delivery tracking: Every message your team sends to a guest is checked to confirm it was delivered. If a message fails to send, Vanio catches it. When the failure is caused by content that the booking platform won't allow — such as a link or contact detail — Vanio automatically rewrites the message with the blocked portion removed and delivers the rest to the guest. Those recovered messages are noted in your digest but do not trigger an alert, because your guest was reached.
Abandoned message detection: Occasionally, a message can get stuck mid-delivery and ultimately be dropped entirely. Vanio identifies these situations — including cases where a guest's message was never received at all — and surfaces them so nothing falls silently through the cracks.

When any of these checks surfaces a problem that left a guest without a response, you receive an alert through whichever channel you've configured (email, Slack, or both). The alert tells you what was detected and why each message failed, so you can take action quickly.

[Screenshot: Example alert notification showing a failed outbound message with property name, timestamp, and failure cause]

Understanding Failure Causes

When outbound messages fail, your alert and delivery digest now tell you exactly why — because the right fix depends on the cause. You may see any of the following:

Cause	What it means	What to do
content-blocked	The booking platform refused the message because it contained a link or contact detail.	If the message was not auto-recovered (see below), resend it without the blocked content, or contact the guest through an alternative channel.
credentials	Vanio's connection to the booking platform has expired or been rejected.	Go to Settings → Connected Channels and reconnect the affected platform.
no-recipient	No valid phone number is on file for the guest.	Check the guest's booking record and add or correct their contact information.
conversation-gone	The thread or booking no longer exists on the platform — for example, a cancelled reservation.	No action is usually needed; verify in your inbox that the booking is genuinely closed.

If the cause shown is unknown, the platform returned an error Vanio doesn't yet recognise. Contact Vanio support and share the message ID from the alert so the team can investigate.

Recovered Messages

When a booking platform refuses a message because it contains a link or contact detail, Vanio attempts to automatically recover it. Here's what that looks like:

The blocked portion (for example, a website URL or email address) is removed and replaced with a short note such as [link removed by Airbnb].
A brief explanation is added to the end of the message so your guest knows a piece was taken out and can ask for it if needed.
The rewritten message is delivered to the guest — so they're not left waiting in silence.

Recovered messages appear in your delivery digest with a count alongside your failed sends — for example, Abandoned outbound sends: 2 (+1 recovered by rewrite). They do not trigger an alert because the guest was successfully reached. You may still want to follow up if the removed content was important to your guest's question.

[Screenshot: Delivery digest showing failed send count with recovered count in parentheses]

Note: Recovery only applies when the booking platform clearly identifies what it objected to. If the rejection can't be safely rewritten — for example, when too much of the message would need to be removed — the original failure is reported to you instead so you can handle it directly.

Key Features

Inbound arrival gaps If a guest's message takes significantly longer than expected to reach your inbox, you're alerted before the delay turns into a guest complaint.
Outbound failure alerts with failure causes When a message from your team fails to deliver to a guest, Vanio catches it and notifies you — and now tells you exactly why it failed (content blocked, connection issue, missing phone number, or conversation no longer active). That means you know at a glance who needs to act and what they need to do.
Automatic blocked-content recovery If the booking platform refuses a message because it contains a link or contact detail, Vanio rewrites the message with the blocked content removed and delivers it to the guest automatically. Recovered messages are counted separately in your digest and never raise a false alarm.
Abandoned message detection Some messages get stuck in delivery and are eventually dropped without a trace. Vanio identifies these lost messages on both sides and reports them to you.
Baseline-aware silence detection Vanio learns your property portfolio's normal quiet periods from your own messaging history. This means it won't cry wolf during a genuinely slow night, but it will alert you if the silence stretches into something unusual.
Smart alert throttling You won't be bombarded with repeated notifications for the same ongoing issue. Alerts are intelligently spaced so you get the signal once and clearly, not on a loop.
Continuous background monitoring Checks run automatically throughout the day and night. There's no dashboard you need to refresh or report you need to pull.

Tips & Best Practices

Connect a Slack channel for faster response. Email alerts are reliable, but a dedicated Slack channel for Vanio messaging alerts means your whole team sees issues in real time. Go to Settings → Alert Channels → Connect Slack to set this up.

Use the failure cause to decide who acts. Your alert now shows why each message failed. A credentials failure needs someone with platform admin access to reconnect the channel. A no-recipient failure needs a guest record update. A content-blocked failure that wasn't auto-recovered needs a manual resend. Reading the cause before you act saves time.

Check your digest for recovered messages. A recovered message count in your digest means guests were reached, but the content that was removed may have been useful to them. Scan these occasionally — if a message type keeps getting blocked, your team may want to adjust how those messages are worded.

Don't dismiss an alert without checking your inbox. If you receive a delivery alert, open the relevant conversation in your Vanio inbox before assuming it resolved itself. In some cases a guest message may be partially delayed and worth a proactive follow-up.

Follow up with guests when outbound failures occur. If Vanio alerts you to a failed outbound message that was not recovered, your guest hasn't heard from you. Reach out through an alternative channel (phone or the booking platform's native messaging) and let them know you're on it. A quick "just following up" goes a long way.

Keep your contact details current. Alerts can only reach you if your email or Slack connection is active and up to date. Check Settings → Notifications after any team changes to make sure the right people are receiving alerts.

Treat repeated alerts as a pattern, not a one-off. If you're seeing delivery alerts regularly, even if each individual incident seems minor, it's worth reaching out to Vanio support. Recurring delivery issues can indicate a problem with a connected booking channel that support can help you address.

Common Questions

Will I get alerted every time there's a short delay in message delivery?

No. Vanio uses your account's own historical messaging patterns to set the threshold for what counts as an unusual delay. Brief slowdowns that fall within your normal range — like a slightly slower gap between messages during low-season — won't trigger an alert. You'll only hear from us when something is genuinely outside the norm for your portfolio.

What does it mean when a message says it was "recovered by rewrite"?

It means the booking platform refused your original message because it contained something it doesn't allow — usually a link or contact detail. Vanio automatically removed the blocked content, noted in the message what was taken out and why, and delivered the rest to your guest. Your guest received the message; they were not left without a reply. You'll see these counted separately in your delivery digest. You don't need to take action, but you may want to follow up if the removed content was important to answering the guest's question.

What should I do when I get a "failed outbound message" alert?

Check the failure cause shown in the alert first — it tells you exactly what went wrong. If it's a credentials issue, go to Settings → Connected Channels and reconnect the affected platform. If it's a no-recipient issue, check the guest's booking record for a missing or invalid phone number. If it's content-blocked and the message wasn't auto-recovered, resend it without the link or contact detail, or reach out through the booking platform's native messaging. If you see repeated failures on the same property or channel, contact Vanio support so they can investigate.

Can I turn these alerts off if I don't want them?

You can adjust your alert preferences at any time under Settings → Notifications → Messaging Alerts. That said, we strongly recommend keeping delivery monitoring active. The alerts are designed to catch failures that are otherwise completely invisible — a guest message that never arrived won't appear in your unanswered messages queue, so without monitoring, you'd have no way of knowing it happened.