Should consent and quiet hours live in a policy document—or in the workflow itself?

Picture a scene most brokerages would rather avoid: a prospect's phone lights up at 9:40 on a Sunday night. On the other end is an agent who did not realize it was that late—they squeezed the call in between showings and lost track. The prospect is not furious. They are just done. A relationship that took months to build takes a hit because the rule ('no outreach during quiet hours') existed in the office manual but not at the moment it mattered.

Documents inform. Design protects.

Policy documents have a real role—training, accountability, culture. But they work through recall, and recall fails under pressure: busy days, new agents, time zones, momentum after a good conversation. The alternative is to move the rule to where the action happens. The controls that matter most look something like this:

• Consent status attached to each contact and checked before outreach is drafted—not looked up from a spreadsheet mid-call.
• Quiet hours applied to timing, so a scheduled follow-up waits for morning instead of arriving during someone's dinner.
• Do-not-contact preferences visible and respected across channels, not left to each agent's memory.
• A record of what was sent, when, and under what consent—kept as part of doing the work, not assembled afterwards.

Which hours count as quiet, which consent applies to which channel, and how long records are kept are decisions for each brokerage and its counsel. Software can hold those settings and apply them consistently; it should not decide them for you.

This is relationship protection too

These are not only regulatory mechanics. A person who hears from you exactly when they asked not to, or at an hour reserved for family, learns something about how you treat attention. The same guardrails that keep an operation defensible also signal respect—and respect matters a great deal when your business runs on referrals. We are careful about the framing: these controls support a brokerage's obligations; they are not a substitute for them, a distinction we draw out in why compliance support is not a compliance guarantee.

The best safeguard is one that makes the careless option hard and never asks anyone to be the hero who remembers.

How we are approaching it

Revybr puts consent status, contact restrictions and visible holds inside the workflow rather than in an afterthought. Those controls apply the settings your brokerage chooses; they do not decide them, and they do not make anyone compliant on their own. Automation should move inside lines everyone can see—including the ones we discuss in what data portability should mean in a brokerage platform.