Build saved segments and use safe CRM search
Find exact customer groups with validated saved segments or constrained plain-language search that never executes generated SQL.
Saved segments and natural-language CRM search use the same versioned filter language. The selected live view shows the total returned with its current results. Other smart-view badges remain unavailable until Cleanr can bind all view counts to one frozen snapshot. Saved-segment counts come from the readiness-gated projection and are hidden when that projection cannot be verified.
Interpret a plain-language request
On web, open Customers → CRM workspace → Segments & search. On mobile, open Customer CRM → Search. Try a supported request such as:
customers with overdue invoices and no upcoming cleanrecurring customers missing an emailproperty managers with at least 3 propertiesmove-out customers this quarter
Cleanr shows the interpretation as filter chips. Remove a chip to correct the request before acting. An or phrase creates an OR group; otherwise v1 uses AND. Unsupported or ambiguous requests ask for manual correction.
Names, phone numbers, email addresses, and street addresses belong in ordinary customer search. CRM search does not retain the raw request and refuses values that could identify a customer.
Save a segment
After reviewing the chips and result count, enter a unique segment name and choose Save. Business segments are visible to authorized owners. Use the arrow controls as an accessible alternative to drag-and-drop reordering. You can duplicate or delete a segment with confirmation.
Segment definitions contain validated fields and operators—not SQL. Cleanr v1 supports bounded AND/OR groups, null semantics, business-timezone relative dates, relationship roles, and property counts. Unsupported future fields fail closed until their schema version is migrated.
Use safe bulk actions
Select up to 200 displayed relationships to add a non-sensitive tag or create follow-ups. The release-preview UI keeps bulk archive and bulk outbound communication disabled until their fresh server preview can enumerate every included and excluded record, bind the result to a short-lived confirmation, and reject stale evidence. Product QA never sends external messages.
Export CRM data
Export CRM data is intentionally unavailable in this release preview. It will remain disabled until the server can bind a selected or saved-segment scope to a consistent snapshot, stream it with bounded keyset pagination, audit each signed-download issuance, and purge abandoned files on schedule. The page does not fall back to the older live-table, whole-business export.
When this gate is enabled in a later rollout, the allowlist must exclude access secrets, payment credentials, provider identifiers, and message bodies and must protect every free-text CSV cell from formula execution.
Natural-language output is treated as untrusted even when an approved provider is available. The current implementation is deterministic and sends no CRM rows or customer values to an external AI provider.
Was this guide helpful?
Feedback sends only this guide's path and your selected answer—never free text or account information.
Manage households, organizations, contacts, and properties
Keep a simple customer fast while supporting households, commercial accounts, shared contacts, payers, and multiple cleaning locations.
Set up services, packages, pricing, and checklists
Build the shared Cleanr catalog, set default prices, and add repeatable checklist steps for Staff.