The problem a shared thread solves
Communication about a single job typically ends up split across a salesperson's phone, an office inbox, a crew lead's texts and one call nobody wrote down. When the customer says 'you told me Tuesday', there is no way to check, so the business either concedes or argues from memory.
A shared thread makes the record checkable. It changes the conversation from competing recollections into reading what was actually sent.
Internal notes are not messages
Every serious system needs a place to write things the customer must never read: concerns about access, pricing decisions, behaviour on site. Those belong on the record, flagged as internal, and structurally separated from the customer-visible thread.
The separation must be enforced where the data is served, not by relying on staff to pick the right box every time.
What a good update looks like
- Says what changed, not just that something changed.
- Names the new date, not 'we will be in touch'.
- Arrives before the customer notices the problem themselves.
- Comes from an identified person, not an anonymous system voice.
A portal does not make you communicative
Publishing a thread the customer can read is passive. The businesses that get referrals still push updates out — a text when the crew is dispatched, a call when a date slips. The portal is where those updates persist, not the reason they exist.