Reading one contact's record
One page assembles everything about a person: their score and its history, their timeline, every message, documents, valuations, relationships, and whether REHL can actually reach them right now. For a recent email or text that cleared REHL's compliance check, you can open it and see exactly what REHL tried to send.
What is on the page
- The score, its recent history as a chart, and the factors behind it (leads only).
- The timeline: what happened, in order.
- Messages, and the delivery receipts that show the strongest evidence REHL has for whether each one landed.
- Their signals, the things they did that moved the score.
- Documents, valuations, transaction history, interested addresses, and the people they are connected to.
- Ownership history: who has had this lead, and when it moved.
Opening a sent message
Every attempt REHL cleared to send, among the most recent 25 shown on the card, has a View control, on email or text alike, whether or not it actually arrived. Older sends fall off the card, with a note that they are not shown, and have no View of their own. It opens the message exactly as it was rendered and stored at that gate check, never a fresh re-render. On a generic email that failed and was later retried, what REHL actually sent on the successful retry can differ from this stored copy: the retry re-renders the unsubscribe link fresh, and it re-reads the brokerage's name and postal address at send time, so a brokerage detail changed between the failed attempt and the retry shows up in what went out, not in this immutable copy. An email opens with its own formatting intact; a text shows as plain text, since it never had any.
View shows what was rendered, not whether it landed. Whether the recipient actually got it is a separate fact, on the same row's own status label: Delivered when the provider has confirmed it, Sent when the provider accepted it but nothing has confirmed delivery yet, In flight while REHL is still waiting to hear back, or Bounced or Not sent when it did not go through. A refused touch, one the compliance gate declined, never gets a stored copy to open, whatever REHL rendered in the process of checking it.
Can REHL reach them right now
There is a card that answers this in plain words for each channel. It separates four different silences, which is the whole point: nothing was ever sent, something is scheduled, something was refused and here is the reason, or REHL genuinely cannot tell. An unopened email on a rail with no open tracking reads as not measured, never as not opened.
Quiet hours
If sending to this person right now would break quiet hours, a line appears saying so: which channel, what time it is where they are, the allowed window, and the exact time it reopens in their local clock. When REHL does not know where they are, it says it is assuming Eastern rather than presenting a guess as a fact.
When no channel is inside quiet hours, no line appears at all. The absence is the positive answer. A card that warned you every time is a card you would stop reading.
Quiet hours is a hold, not a fault. Nothing is broken and there is nothing for you to clear. The send goes out when the window opens.
The card says a text was refused. What now?
The reason is printed word for word from the compliance gate, not paraphrased. Most reasons tell you the remedy. In Florida, Washington and Oklahoma the contact has to reply to confirm before REHL will text them, and no amount of retrying changes that.
Why does this look like a lead page for some contacts and not others?
Because a Sphere-only person has no score, no stage and no pipeline. Promote them to a lead and the pipeline half of the record appears.
Need more help? Contact support.