CRM playbook: work the conversations inbox

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page
Working an inbox across a laptop and phone at a desk

When a signed-in visitor has a question on one of your listing pages, they can ask it right there — the thread opens against that property, titled by its address, and lands in your CRM’s Conversations inbox. It is the highest-intent channel you have: a known person, on your site, on a specific home, right now. Handled well, these threads convert faster than any form fill; handled like email, they quietly expire. This lesson is the routine that does it justice.

Step 1: wire the alerts before the first message

New visitor messages notify the assigned seat — bell, email, and push. The one that changes outcomes is web push on your phone: a chat answered while the visitor is still on the page reads as service; the same answer the next morning reads as voicemail. Turn push on for every seat that might own a thread.

Step 2: read the person before you type

Every thread carries a link to the person behind it. Take sixty seconds there first: what they have viewed, what they have favourited, what they searched. The behaviour timeline lesson covers reading it in depth — the point here is simply that “great question — this one also has the garage you were filtering for” is a different conversation than a cold answer.

Step 3: answer like an operator

The pattern that converts: answer their actual question directly, add one useful thing they did not ask, end with a concrete next step — usually an offer to see the place. Three sentences beat three paragraphs. Because visitor chat is tied to one property per thread, staying concrete is easy: the subject line is the address.

Step 4: move threads into the pipeline

A conversation that goes well should not stay a conversation. When a visitor agrees to a showing, book it; when a thread reveals a serious buyer, the contact record is one click away and the thread is already part of their history. Because each property keeps a single open thread, the inbox stays tidy on its own — your job is making sure every live thread ends in a booked step, not a trailing “let me know”. The inbox is a front door, not a filing cabinet.

Step 5: sweep to zero twice a day

The Conversations tab carries an unread badge — treat it like a phone that is ringing. Morning and evening, clear it: reply, book, or consciously close. Visitor accounts mean every thread belongs to a real, reachable person; none of them should age in an unread state.

What done looks like

Push alerts on every relevant seat, the unread badge at zero twice a day, and your median reply time inside the same standard you hold for new leads.

The mistake that costs the most

Mentally filing chat below “real” leads. A form fill is someone who was on your site once; an open thread is someone on your site now, mid-decision, asking you specifically. Rank your channels by intent and chat sits at the top — treat it accordingly.

Frequently asked questions

Do visitors need an account to message me?

Yes — messaging is for signed-in visitors, and that is a feature, not a hurdle. Every thread arrives attached to a known person with a behaviour history, instead of an anonymous chat bubble you cannot follow up with if they close the tab.

What happens if I cannot reply for a few hours?

The conversation survives: your reply is emailed to the visitor with a link back to the thread, so nothing depends on them keeping the tab open. But treat that as a safety net, not a pace. The visitor messaged from a listing they were actively reading — the value of your answer decays by the hour.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.