Portal update or call test
Jun 9, 2026
7 min read
A client portal can make an agency look organised. The vendor sees viewing activity without waiting for a call. A landlord can check where a repair stands. A buyer can see that their question has not disappeared into someone’s inbox.
“Viewing completed” might be technically true, but it doesn’t answer the vendor’s real question: did they like it, are they likely to offer, and what should we do next?
“Application pending” tells a landlord that something is happening, but not whether the applicant is waiting on documents, references, affordability checks, or a decision from the branch.
For newer agents, think of a client portal as a place for clean status. Keep emotional interpretation in the conversation around the update. The portal works when the client needs a factual note they can revisit. It falls short when they need judgement, reassurance, or a decision.
Start with the job the message has to do
Before choosing the channel, ask what the message is meant to achieve.
Some updates just remove uncertainty:
| Message job | Example | Portal-safe? |
|---|---|---|
| Confirm activity happened | “Viewing completed at 2:30pm.” | Yes, if no decision is needed |
| Record a next step | “References requested from applicant.” | Yes, if the next step is clear |
| Ask for a simple action | “Please upload proof of ID.” | Usually, with a clear deadline |
| Explain weak feedback | “Buyer liked the location but felt the kitchen needs too much work.” | Sometimes, but a call may be better |
| Prepare for bad news | “Offer withdrawn.” | No, call first |
| Ask for a decision | “Should we reduce the asking price?” | No, call or meeting first |
Some hard messages still need a written record. The rule is simple: use the portal when the client can read the update and know what happens next. Use a call when they may reasonably ask, “What does that mean for me?”
The portal-safe test
Use this 5-part test before publishing a client-facing update.
| Test | Portal update is fine when… | Use a call or direct message when… |
|---|---|---|
| Clarity | The wording cannot easily be misread | The client needs tone, context, or reassurance |
| Consequence | The update does not change a decision | The client must choose, approve, reject, or rethink |
| Sensitivity | It contains no private negotiation, personal, or complaint detail | It involves finance, motivation, conflict, or disappointment |
| Timing | The client can read it later without damage | A delay could create anxiety or lose momentum |
| Evidence | The update is factual and can sit in the record | The facts are still being checked or explained |
If 4 or 5 answers sit on the left, publish the update. If 2 or more sit on the right, speak to the client first.
Many real estate client communication tools make updates easy to publish. They don’t decide whether the update is suitable for a client to read alone.
The same applies to real estate follow up software. A reminder to send an update helps, but a sensitive decision shouldn’t be turned into a bland automatic note.
What different clients read into the same status
A vendor with a slow first week on the market sees “no feedback received” and may hear “the agency is not chasing.” A buyer waiting on an offer response sees “seller reviewing” and may hear “we are being played.”
A landlord waiting on a tenancy application sees “checks pending” and may hear “the applicant is weak.”
Zillow’s 2025 Consumer Housing Trends research shows that buyers vary in how they prefer to communicate with agents, with text, phone, email, and messaging all represented. Agencies should treat preference as live context, especially when the message becomes urgent or sensitive.
Record the client’s normal preference, but don’t follow it blindly. A client may prefer text for viewing times and still deserve a call when an offer falls through.
Keep internal notes separate from client-facing updates
The portal update should be the clean, client-safe version of the record. It shouldn’t contain every thought the branch has.
Keep these in internal notes:
- Buyer or tenant motivation that should not be broadly shared
- Seller, landlord, or applicant frustration
- Staff judgement about reliability, tone, or risk
- Legal, complaint, or compliance concerns that need careful handling
- Draft wording that still needs review
Keep these in the client-facing update:
- What happened
- What is waiting
- Who owns the next action
- When the client should expect the next update
- What, if anything, the client needs to do
That split matters because written records can protect or expose the agency. The Property Ombudsman has warned that poor record keeping can leave agents unable to answer complaints. A clean portal update helps only if it reflects what happened without tucking in gossip, guesswork, or sensitive detail.
For US teams, the NAR Code of Ethics stresses honest and truthful real estate communications. Different markets have different rules, but the operating habit travels well: make the record clear, and don’t make the client infer what you should have explained.
Use this decision rule before posting
Use this rule in a busy branch:
If the update creates a new question, call before posting.
That sounds simple, but it changes the wording.
| Weak portal update | Better portal update | Human follow-up |
|---|---|---|
| “Feedback received.” | “Buyer feedback received. Agent reviewing with vendor today.” | Call vendor before sharing negative detail |
| “Offer withdrawn.” | “Offer status updated. Agent will call you today.” | Call first, then record summary |
| “References delayed.” | “Reference request sent. Next check due Friday at 10am.” | Call landlord if move-in date is at risk |
| “Applicant not suitable.” | “Application review completed. Agent will discuss next steps.” | Call before declining or advising |
| “Price change recommended.” | Do not post this first | Call or meeting first, then written recap |
The portal should reduce chasing while difficult conversations stay with people.
AvaroAI treats tasks, contacts, and visibility as connected work rather than separate lists. A portal-safe update may still create an internal task, such as “call vendor by 4pm before posting viewing feedback.”
Contact preferences and custom fields help the team see whether this person usually wants a call, a text, or a written recap. Role-based access keeps sensitive internal notes away from client-facing updates while still giving managers enough visibility to step in.
The practical point: the update is one part of the job. The bigger job is to move the client, property, or tenancy to the next clear action without creating confusion.
Run a 10-minute portal update audit
Use this tomorrow on the last 10 client-facing updates your team posted.
- Pick 10 recent portal updates across sales, lettings, or property management.
- For each one, ask: could the client understand what happened and what happens next?
- Mark each update as
safe,needs clearer next step, orshould have had a call first. - Rewrite 3 weak updates using this pattern: what happened, who owns the next action, when the client hears again.
- Add one internal rule for the branch, such as “Offer withdrawals are called first” or “Negative viewing feedback gets a vendor call before portal wording.”
- Check whether each update created a task where one was needed.
The audit shouldn’t take long. If it becomes a debate about every possible edge case, the branch is probably missing a simple shared rule.
Client portals work best when they carry calm, factual progress. Calls work best when the client needs judgement, empathy, or a decision. Good agencies know which is which before the client has to ask.
Related reading
Disclaimer: This page may contain AI-assisted content. The information is provided solely as a general guide and may not be correct, complete, or current, including, but not limited to, our full or applicable service offerings. While we strive for accuracy, no guarantee is made regarding correctness or completeness, and no expectation should be made as such. Please contact us directly to confirm any details before utilizing our service.
