Was contact established?
Record a supported contactability outcome, such as reached, no response after documented attempts, or invalid contact details. Do not add personal contact details to this ledger.
For senior living operators
Verified July 29, 2026 · Reviewed against A Place for Mom's current service page and terms
The narrow job: your community may have a direct inquiry on file before a later referral-network notice, or a paid referral that proves unreachable or outside the service area. Put the supported records in one chronology before anyone argues about attribution, lead quality, or billing.
A Place for Mom's current service page says participating senior living communities pay it when a referred family moves in. Its current terms also say certain disclosures to participating organizations may continue for normal business practices, including billing matters, until those matters are closed.
Those public pages do not expose the private contract governing a particular provider or say that one timestamp controls every attribution question. The practical first step is therefore a bounded chronology supported by the operator's own records. That chronology is not proof of legal attribution.
When the issue is lead quality
Record a supported contactability outcome, such as reached, no response after documented attempts, or invalid contact details. Do not add personal contact details to this ledger.
Record whether the referral was inside the stated service area, outside it, or otherwise not a documented service fit.
Track reported, acknowledged, credited, not credited, or closed as distinct statuses. Do not turn a request into an assumed outcome.
An unreachable or out-of-area A Place for Mom lead can support an internal review record. It does not by itself prove invalidity, require a billing adjustment, or establish that a referral fee is not owed.
Six useful fields
Internal alias, community, earliest timestamp, direct channel, and the internal source that supports it.
Referral network, notice timestamp, and the subject line or CRM reference that identifies the notice.
Keep family names, phone numbers, email addresses, medical details, financial information, government identifiers, passwords, and identity documents out of this narrow ledger.
Not another CRM
This is for the awkward exception your CRM or spreadsheet leaves scattered: a direct touch and a later referral notice that need to be reviewed together. It does not replace your system of record.
One professional location. One-time purchase. Instant browser access. No phone number required at checkout.
GeezerKeeper cannot determine that. An earlier timestamp is a chronology fact, not a contract ruling. Review the applicable agreement, internal records, and qualified advice before acting.
Use an internal record ID, the community, supported direct-touch and network-notice timestamps, the contactability outcome, the service-area or fit outcome, and a non-sensitive note identifying the supporting record.
No conclusion is automatic. Record the supported outcome and the network's actual response, then review the applicable agreement, alerts, internal records, policies, and qualified advice.
No. The chronology stays in that browser until the purchaser exports or clears it. Use internal aliases and exclude sensitive information.