A limited property phone pilot makes errors easier to identify and recover. Choose a small building set with documented policies and staff who can inspect every resulting request.
Define the pilot's purpose: capture maintenance reports, route leasing enquiries, collect viewing preferences, or execute a narrow supported booking flow. Do not combine all portfolio workflows merely because the platform can expose them.
Set the action and data boundaries first
Specify permitted reads, writes, disclosures, escalation routes, and staff-owned decisions. Configure each building's identity, contacts, hours, and exceptions independently. Keep a rollback route and a way to suspend consequential actions while preserving approved intake.
Use fictional controlled calls before the approved live pilot. Isolate test messages and contractor dispatch so a rehearsal cannot create real attendance or expose resident information.
Rehearse a fictional two-building launch
A manager pilots routine intake at two well-documented buildings. Viewing requests remain preferences for staff review, and maintenance attendance stays with dispatch. One building has a different after-hours contact.
Test callers using building nicknames, shared numbers, and mixed purposes. Reviewers inspect tickets, staff queues, and exact caller commitments. A successful call at the first building does not establish correct routing at the second.
| Pilot scenario | Acceptance evidence |
|---|---|
| Ambiguous building | Correct clarification or review state |
| Maintenance report | Correct unit and owned request |
| Viewing preference | No implied reservation or access |
| Staff unavailable | Approved fallback |
| Wrong-client identifier | Access blocked safely |
| Rollback | One active handler, preserved pending work |
Expand based on operational readiness
Track wrong-property incidents, unsupported disclosures, false confirmations, duplicate actions, request age, and exception workload. Staff should be able to recover common failures without waiting for a developer.
A short pilot cannot prove broad revenue or efficiency gains without an appropriate measurement method. It can show whether the workflow's boundaries and recovery work. Document observed defects and limitations separately from targets.
A narrow launch delays automation elsewhere but limits variation. A portfolio-wide launch exposes many policy differences at once and can overwhelm reviewers. Expand when affected scenarios pass and the next buildings have maintained configuration and owners.
Review property fictional tests for a reusable acceptance pack.
Questions about property pilots
How many buildings should launch first?
Choose a scope the operational team can actively review. Building count matters less than policy variation and support capacity.
Should all actions be automated during the pilot?
No. Retain human decisions where data, authority, or recovery is not ready.
What should the expansion record include?
Supported scenarios, measured observations, unresolved limits, exception owners, tested rollback, and the configuration differences for the next stage.