Choose a property management CRM by tracing a person, their enquiry and the relevant property through the next communication. Keep prospective tenants, current tenants and other contacts distinguishable, with clear responsibility for follow-up. Use the worksheet below to connect identity, property context and communication history before migrating records or relying on a shared inbox.
Which relationship does the contact record represent?
Begin with the people involved in a representative property enquiry. Identify the prospective tenant, any joint applicant, the current tenant where relevant and the colleague handling the request. Keep their roles separate from the spelling of a name or the telephone number supplied during a call.
Capsule describes centralising tenant information, communication history and preferences. Documentation. Property CRM lists landlords, tenants and multiple-party contacts among its supported contact types. Documentation. Use those documented descriptions to prepare the relationship questions for the proposed CRM. Ask how a person can be connected to more than one property or enquiry and how the current relationship remains visible when an earlier one ends.
Define the reference used for the property and the enquiry. A general note on a contact can be hard to interpret when the same person discusses several properties. Give the operator a clear place to record the subject of the communication and the next action expected.
How should an enquiry move towards a tenancy conversation?
Property CRM lists automatic property-and-enquiry matching and shortlisting. Documentation. Ask the demonstrator to show the actual criteria and record relationship in the proposed configuration. Keep the suggested match distinct from a decision that a person has accepted a property or entered a tenancy. The business still needs an understandable record of the conversation and its outcome.
Capsule describes customising fields for a property-management workflow. Documentation. Write the required fields from the team’s actual work. Include the property reference, enquiry state, responsible colleague and unresolved question. Have staff explain how each field helps them decide the next step rather than importing every column from an old spreadsheet.
Property CRM describes access to appointments, viewings and dated tasks from its landing page. Documentation. Property CRM lists communicated, recorded and date-stamped offers. Documentation. Review the displayed work and its communication record together. Ask which item is a proposed appointment, which records a conversation and which establishes an offer’s recorded state. Keep the intended next action and its owner visible to the colleague taking over.
An original person-property communication worksheet
Use this practical checklist for a representative enquiry and an existing tenant request. Fill it with the actual record references used by the proposed system. It is an original handover aid for relationship history and follow-up.
| Relationship boundary | Information to retain | Question before handover |
|---|---|---|
| Person identity | Stable contact reference and relevant contact details | Is this the intended person? |
| Relationship role | Applicant, current tenant or other relevant role | Which relationship applies to this conversation? |
| Property context | Property and enquiry or tenancy reference | What exactly is being discussed? |
| Communication | Date, channel and concise outcome | Can another colleague understand what was said? |
| Next action | Task, owner and expected follow-up | Who should act next? |
| Changed details | New information and its source | Which record now represents the current position? |
| Exception | Duplicate contact or unclear association | Who resolves it without guessing? |
Keep an explicit route for suspected duplicate contacts. Ask the reviewer to compare two similar names and determine which evidence establishes the intended person before merging or updating records. Preserve the relevant source reference so a later correction can be understood.
For a joint enquiry, define what each participant may receive and who supplied each contact detail. Have the responsible business owner establish the appropriate information-sharing arrangements. The proposed CRM workflow should implement those decisions rather than treating a shared property reference as permission to share every conversation.
Can the communication history support the next visit or call?
Capsule describes calling, texting or emailing from a tenant profile. Documentation. Capsule describes an activity log of tenant interactions. Documentation. Use a fictional enquiry to examine the actual record produced after a contact attempt. Ask another colleague to locate the latest outcome and identify the next task. Keep a failed contact attempt distinguishable from a conversation that resolved the question.
Capsule describes mobile dashboard, calendar and task-list tools. Documentation. Assign responsibility for reviewing outstanding work. A visible task is useful only when the operating process says who acts on it and how a colleague recognises completion. Request a demonstration using both an ordinary follow-up and one requiring another person’s decision.
Capsule says mobile-app changes synchronise when the connection returns. Documentation. Include a connection interruption in the proposed mobile evaluation if staff need that capability. Record the intended update and inspect the eventual shared record through the actual configuration. Ask how a colleague recognises an unresolved difference between two updates.
Hypothetical example: a joint applicant changes a contact detail
Imagine a joint enquiry concerns one property, and one applicant asks to use a different telephone number. Another colleague later follows up using an earlier note. This hypothetical case tests whether the person, enquiry and current contact details remain connected clearly.
Put both people and the enquiry reference on the worksheet. Identify which person’s detail changed, who supplied the correction and which follow-up task is outstanding. Ask the demonstrator to apply the intended update and have a second colleague prepare the next contact from the record.
Then introduce an enquiry for another property by one of the same people. Review whether the communication subject remains unambiguous. Keep the distinction between changing a person’s contact detail and changing the outcome of one enquiry visible in the working record.
Record the observations when the rehearsal is performed and assign any unclear association to an owner. A useful CRM handover should let the next colleague understand the relationship without reconstructing it from several informal messages.
What should remain outside the communication brief?
Keep tenancy accounting, maintenance operations and owner reporting in their appropriate workstreams. This article’s worksheet focuses on people, enquiries and communication history. Link the relevant operational record where the conversation needs context, while giving each decision a clear owner.
Use choosing a CRM for the broader selection process. Discuss the public enquiry journey through web development and get started with the contact roles, property references and follow-up exceptions you need the proposed workflow to support.
Before migration, ask the next operator to reconstruct one enquiry from the proposed record alone. Record which property reference, person relationship or follow-up instruction they need clarified, then use those observations to improve the field mapping.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.