TL;DR: Every Radius booking — and every pre-booking inquiry — has its own message thread, with the property, dates, and people already attached. Threads keep everyone in the loop on one place: the Host, the Booker, the Guest. It's the convenience, not the requirement.
Who this is for: 🏠 Host 👥 Booker 📋 Admin
What a thread is
A conversation on Radius is one thread, tied to a single property — and, once there is one, a booking. Radius is just connecting the Host to the Booker and the Guest; the thread exists so all three can stay in the loop on the same place instead of chasing each other on cell phones. After a booking is confirmed, talking off-platform (a quick text about check-in, a phone call about lockbox codes) is completely fine — but the thread is where the full record lives.
How threads start
Pre-booking inquiry. A Booker reaches out from a listing before they request. A thread opens immediately so the Host can answer questions — even before any booking exists.
A new booking. The thread opens with whatever the Booker (or Guest) wrote at checkout as the first message.
Book for Others. When a Booker places a stay on a Guest's behalf, the thread opens between Booker and Host first; the Guest joins once their account is linked.
What you can do — by role
Everyone can read, reply, mark read, archive, and rename. Companies (Bookers + Admins) get the extra tools for working as a team.
Action | 🏠 Host | 👥 Booker | 📋 Admin |
Filter by type (inquiry, booking, archived) | ✓ | ✓ | ✓ |
Sort by latest activity | ✓ | ✓ | ✓ |
Sort by move-in, move-out, owner, or status | — | — | ✓ |
Archive (hides from inbox; auto-unhides on next message) | ✓ | ✓ | ✓ |
Rename a thread (custom label) | ✓ | ✓ | ✓ |
Override the Guest's display name on the thread | — | ✓ | ✓ |
Switch between "Mine" and the whole team's threads | — | ✓ | ✓ |
Search across the company's threads (property, city, Guest name, label) | — | — | ✓ |
Transfer ownership of a thread to a teammate | — | ✓ (own) | ✓ |
Add or remove collaborators on a thread | — | ✓ (own) | ✓ |
View the activity log (who did what, when) | — | ✓ | ✓ |
🏠 Host: Booking decisions — accepting a Request to Book, accepting an extension — happen on the booking itself, not as a button in the thread. The thread shows status updates as the booking moves; the action buttons live in your bookings page. Watch the timers: Request to Book and extension requests both auto-decline if you don't respond in time.
Common situations
Off-platform contact after the booking is confirmed
Totally fine. Once a stay is confirmed, swapping phone numbers for a quick check-in question or a lockbox code is normal. The thread is a convenience, not a rule — it just keeps the full record (and anyone else on the team) in one place.
A Booker shares a Property Collection with a Guest
Property Collections are a separate Booker/Admin tool — a curated shortlist of listings a Booker can share with a Guest via a share link. Conversations stay per-listing/per-booking; a Collection doesn't bundle threads. (If the Guest picks a listing and asks a question, that's its own thread.)
A teammate needs to take over
Bookers and Admins can transfer ownership of a thread to another teammate, or add a collaborator so two people can work it together. The full activity log stays attached, so the next person sees what happened.
Frequently asked questions
Do I get notified when a new message arrives?
Yes — by email by default.
What kinds of threads show up here?
Pre-booking inquiries, confirmed bookings in progress, and Book-for-Others files — every thread tied to a property you're on.
What does Archive do?
Hides the thread from your inbox. As soon as a new message comes in, it pops back. It's a personal action — archiving a thread doesn't affect what your teammates see.
Can I change the name on a thread?
Yes — add a custom label. Companies can also override the Guest's display name (useful when the Guest's account name doesn't match how your team refers to them).
I'm the Host and want to approve a Request to Book — where?
On the booking itself, not in the thread. Same for accepting an extension. The thread is for the conversation; the booking page is for the decision.
Related articles
Still need help?
Click the chat icon at the bottom-right of any page on help.bookradius.com, then click Contact Radius Support under "Create a ticket." Full walkthrough in How do I contact Radius?