Product ยท Operate
Unified inbox
Every conversation.
SMS, email, Airbnb, Furnished Finder. One thread per contact, triaged by Ivy.
Sarah Chen
Suite 2 ยท stay confirmed Apr 5โ9
- AIRBNB9:42 amHi! Just booked for Apr 5. What's the wifi password and parking situation?
- SMS9:43 amAlso is there a Trader Joe's nearby?
- EMAIL10:11 amHey Sarah! Wifi: Laurel-Guest / domivy2026. Park in the driveway, second spot. Trader Joe's is 0.4 mi up Forbes. Welcome!
- SMS10:14 amPerfect, thank you ๐
Ivy drafted a reply
Drafted in your voice from 47 prior replies. Reviewed against the house rules and trash schedule.
All channels, one thread
A guest who texts, emails, then DMs through Airbnb is one conversation, not three. The thread follows the human.
Ivy triage on every inbound
Category, priority, suggested reply, draft ready in one click. Before you open the app.
Canned replies + variables
Save the 20 answers you send monthly. Two keystrokes to insert. {{guest_name}} fills itself.
SLA clocks
Every inbound starts a reply-by clock. Miss it, the thread surfaces red at the top of the queue.
Role-based visibility
Cleaners see maintenance. Co-hosts see guests. Accountants see payments. No shared passwords.
Search that works
Full-text across every message, every attachment, every channel. Under one second.
One conversation, three channels
How the inbox stitches a single guest together.
Guests don't pick a lane. They text, they DM Airbnb, they reply to your confirmation email โ sometimes within an hour. The inbox treats them as one human, not three threads.
First touch ยท SMS
Guest texts your business line: 'Can we get an early check-in?' Inbox lands the message, Ivy parses it (category: check-in change, priority: medium), drafts a reply with the actual lock-code activation window.
Same guest, different channel
An hour later, the same guest DMs you on Airbnb about the same question. The inbox recognizes the email + phone match, threads the Airbnb message under the existing conversation. No duplicate triage, no "didn't I just answer this?"
SLA clock starts
Each channel has its own response-time target. Airbnb at 1 hour, SMS at 15 minutes. The clocks surface side-by-side; miss either, the thread turns red at the top of the queue.
You reply once
You hit send on the canned-reply for early check-in. Variables fill ({{guest_name}}, {{check_in_window}}). The reply goes out via SMS โ the channel they texted from โ and posts to the Airbnb thread as a logged note. One typing motion, two channels updated.
Email about checkout
Three days later, same guest emails about checkout time. Email lands as a reply to the same thread (matched on email or booking id). You see the full pre-arrival, mid-stay, and checkout context in one timeline.
Audit on demand
Six months later, an Airbnb dispute requires the conversation history. Search by name pulls the entire stitched thread โ SMS + DM + email + your replies โ in under a second. Export to PDF for the case.
Founding access
Every conversation, one place.
Three months free for founding members. Cancel anytime.