“Aline CRM already reports by source.”
On enquiries, tours and stages, which it sees. The monthly fee is in the billing system and nothing joins the two.
For Aline CRM (formerly Enquire)
Export enquiries from Aline CRM, match them against move-in revenue, and rank sources over the length of the decision rather than the quarter.
No API key Nothing to install in Aline CRM (formerly Enquire)Nothing to install No card requiredNo card
Aline CRM — sold as Enquire until the product moved under the Aline name — holds the enquiry side for the senior living operators that run it: the source, the campaign, the tour, the stage — while the revenue arrives as monthly fees in the billing system. CloseRev joins them on the enquirer's phone or email and reports move-in revenue by source over a window long enough for the decision to have happened. Revenue with no traceable enquiry is reported as Direct / Unknown.
Last checked against Aline CRM (formerly Enquire)'s own documentation on September 25, 2026.
The gap
Occupancy is reviewed monthly against enquiries that will not convert for a year.
What was sold, to whom, and for how much.
The click, the keyword, the call, and what each one cost.
The file
Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.
The adult child or advisor as often as the resident. Whoever the community actually talks to is the key.
Where the enquiry came from, including placement agencies and hospital discharge planners.
Both. The interval is the defining number of this category and it is measured in seasons.
Which building, and independent, assisted or memory care. Their economics differ substantially.
Step by step
Written for somebody with Aline CRM (formerly Enquire) open in the next tab. Report names vary by edition, so each step says what to look for.
One row per enquiry with a contact detail, the source and when it arrived.
From the billing system: resident contact detail, monthly fee, move-in date.
A senior living decision is made slowly, often in stages, and frequently restarts after a health event.
They are most of the file and all of the cost, and they differ enormously by source.
The join runs on the phone and the email, normalised, grouped by when the enquiry arrived.
What comes back
Revenue by channel, the count of sales behind each figure, and an honest bucket for the ones nobody could trace. Sample figures, from the worked example on the Senior Living page — not from a Aline CRM (formerly Enquire) account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 3 | $385,000 | |
| Referral agencies | 3 | $311,000 | |
| Meta Ads | 1 | $103,500 | |
| Community events | 1 | $74,000 | |
| Direct / Unknown | 5 | $606,500 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
An adult daughter calls, tours three communities, talks to her brother, and a parent moves in eleven months later.
That means the contact detail on the enquiry and the contact detail on the resident record are frequently different people, and a naive match loses most of the file.
Exporting the enquirer's details onto the resident record — or keeping the family contact on both — is what makes this measurable at all.
Where both are present the report matches on either, and reports which key joined, so a low match rate is visible as a data problem rather than as a channel producing nothing.
This is the single most common reason senior living attribution fails, and it is a field on a form rather than a technology problem.
A move-in is not a sale of a fixed amount: it is a monthly fee for a stay that may run months or years, at a care level that usually rises.
Ranking sources on the first month understates every one of them equally and tells you nothing about which produced residents who stayed.
Summing by resident across the window gives the honest figure, and keeping the care level lets a rise in acuity be read as revenue rather than as noise.
It also makes length of stay comparable by source, which is a real and uncomfortable finding: sources that fill beds fastest do not always fill them longest.
Nothing here predicts a stay. It reports what residents from each source actually billed.
Referral and placement services produce a substantial share of move-ins and charge a fee that is often a month's rent or more.
Because that fee is deducted rather than invoiced by a marketing platform, it sits outside the marketing budget and is rarely compared with what a paid campaign costs per move-in.
Putting it beside revenue per move-in makes the comparison real, and the answer depends entirely on length of stay: a large fee on a three-year resident is cheap and on a four-month one is not.
That calculation is the whole placement-agency decision and almost nobody runs it, because the two numbers live in different systems.
The report puts them in one place and leaves the conclusion to the operator.
Tours booked is available weekly, so it is what gets reported, and it correlates with move-ins far more weakly than anyone expects.
A source producing willing tourers and few move-ins scores well on it indefinitely, and nothing inside the funnel contradicts that.
Revenue per enquiry over eighteen months reorders the list, usually vindicating a slower source that the tour metric had buried.
Both numbers are shown side by side, because the gap between them is itself the finding and is often about the community rather than the channel.
Fair questions
On enquiries, tours and stages, which it sees. The monthly fee is in the billing system and nothing joins the two.
The decision takes that long. Grouping by enquiry date lets you act on mature cohorts while the recent ones fill in.
They are an acquisition channel with a fee, and comparing that fee with a campaign's cost per move-in is the decision nobody runs.
No. It reads exported files, so your enquiries, notes and resident records stay where they are.
Yes. Enquire's own domain now redirects to Aline, and the product is sold as Aline CRM. Exports from either version carry the same enquiry, source and date fields this page describes.
The enquiry side. Move-in revenue from the billing system is the other half.
Enquiries with a contact detail, source and date, plus move-in revenue with fees and dates.
Only if the family contact is not carried onto the resident record. Keeping it on both is what makes this measurable.
Eighteen months at minimum. The decision is made slowly and often restarts after a health event.
Yes. They are most of the file and all of the cost.
Yes, on revenue per move-in against their fee, and the answer turns on length of stay.
Yes, where the export carries one. A portfolio average describes none of the buildings.
Yes. A rise in acuity is revenue, and reading it as noise understates the sources that produce longer stays.
Any move-in with no traceable enquiry. Its size is stated rather than distributed.
A contact detail, a source and a date on one side; a contact detail, a fee and a date on the other. No care records, no assessments, no medical information, no family notes. Encrypted in transit and at rest and deleted with the import.
Revenue per move-in by source grouped by when the enquiry arrived, tours shown beside it, length of stay where the window allows, and everything unmatched kept visible.
By trade
What the report looks like once the export is in, written for each one.
Other systems
Running more than one system, or comparing? The method is the same and the columns are not.
Aline CRM (formerly Enquire) and the other product names and logos on this page belong to their owners and are shown to identify the software a file comes from. CloseRev is not affiliated with or endorsed by them, and connects to none of them: it reads a file you export.
Start today
Nothing to install in Aline CRM (formerly Enquire), no API key, and no need to have been tracking anything until now. Last year works as well as this month.