Threaded to the booking
Every message a guest sends lands on the reservation it belongs to - no more hunting through a mailbox for the thread that matches a name.
Connect the mailbox you already run your business from. Every reply from a guest lands on the reservation it belongs to, and every reply you send goes out from your own address - not a shared inbox nobody checks.
Her reply about the deposit lands on the same booking she enquired about at midnight.
OAuth for Gmail and Outlook, or plain IMAP/SMTP for anything else - gizmostours.com uses their existing Gmail account, no new address to give out.
Every message a guest sends lands on the reservation it belongs to - no more hunting through a mailbox for the thread that matches a name.
Replies go out from your connected mailbox, not a shared no-reply address, so a guest sees exactly who they are talking to.
Save the replies you send most - a quote follow-up, a deposit reminder, a welcome note - and drop them into a thread in one click.
Connect Gmail or Outlook with OAuth, or point TBW at any IMAP/SMTP mailbox - your existing provider, not a new one to manage.
No. Connect the mailbox you already use - Gmail, Outlook, or any IMAP/SMTP provider - and TBW reads and sends through it.
Yes. Seats with inbox access see the same threads, so a booking is never stuck waiting on one person’s laptop.
They land in the inbox unthreaded so you can still read and reply to them - TBW only links a thread to a booking when it can match one.
Connect your mailbox and every reply finds its booking automatically.