Software that connects sales and lettings in a UK branch
See what your branch needs to share across sales, lettings and property management so client details, documents and unfinished work survive each handover.
Most UK estate agencies do not run as neatly as their software categories suggest.
A branch might have sales, lettings, property management, a valuer, admin support, and a manager trying to keep the day moving. Clients do not respect those internal lines. A landlord may also be a vendor. A buyer may become a tenant while they keep searching.
When choosing software for a UK branch, check how it handles clients and properties shared by sales and lettings. Both teams need access to the relevant files, instructions, and promised updates.
When it does not, the real operation moves into private notes, shared drives, WhatsApp messages, spreadsheets, and memory.
Check what happens when work crosses between teams
Sales and lettings move at different speeds.
Sales work moves through valuation, instruction, listing preparation, viewings, offers, memorandum of sale, conveyancing updates, and completion. Lettings moves through landlord onboarding, compliance checks, marketing, viewings, applications, referencing, tenancy setup, inspections, renewals, repairs, and rent-related administration.
The trouble starts when the same branch has to move context between those two streams of work.
A landlord calls the sales team because they are considering selling one managed property. A vendor asks the lettings desk whether they should rent instead of reducing the price. A tenant viewing a flat also wants to register as a buyer. A property manager knows the access restrictions, but the sales negotiator books the viewing. An administrator has the certificate or authority document, but the person updating the listing cannot find it.
These situations come up regularly, and branch software needs to accommodate them. If the system separates sales, lettings, property management, files, and tasks too sharply, staff have to rebuild the missing context by hand.
Where mixed-branch work usually breaks
The breakpoints often look small inside the office. They become serious when the client feels them.
| Breakpoint | What the client experiences | What the branch actually needs |
|---|---|---|
| Vendor is also a landlord | Repeated questions from different people | One relationship record with role-specific visibility |
| Sales property becomes a letting option | Slow relaunch or missing details | Property history, media, compliance notes, and owner instructions in one place |
| Lettings applicant becomes a buyer | The client has to explain themselves again | Requirements, budget, timeline, and contact preference carried forward |
| Viewing feedback crosses teams | Vendor or landlord gets a patchy update | Feedback tied to the viewing, property, applicant, and owner |
| Compliance documents are scattered | Listing or tenancy work stalls | Files attached to the relevant property, contact, and task |
| Manager covers absence | The next action is unclear | Owned tasks with due dates and enough context to act |
Applicant contact history alone won’t cover this work. Staff also need previous viewings, landlord requirements, documents, tenancy dates, and relevant conversations with the sales team.
Keep the evidence behind decisions and instructions
UK agency work is carrying more documentation than it used to.
The government’s consultation on material information in property listings makes the direction clear: relevant property information should be available early and presented plainly. It also recognises the practical problem agents face when gathering, checking, and publishing that information.
For lettings in England, the first phase of Renters’ Rights Act changes took effect on 1 May 2026. That puts more weight on operational readiness. Propertymark’s guidance on practical steps for letting agents points agents toward updated systems, payment procedures, portfolio data, written information requirements, and clear internal processes.
Then there is service quality. The Property Ombudsman’s Codes of Practice are not software requirements, but they are a useful reminder that complaints often turn on communication, records, procedures, and whether a consumer can see that the agent acted properly.
The system needs to preserve evidence of what was known, who was told, what was promised, what was still missing, and which team owned the next step.
The shared-record test for UK estate agency software
Test whether sales and lettings staff can use the same records while each seeing only the information their role requires.
The shared-record test has five parts:
- Can one person or company hold multiple roles, such as vendor, landlord, buyer, tenant, guarantor, or referrer, without duplicate records?
- Can a property keep its history across valuation, instruction, listing, letting, management, sale, and archived phases?
- Can tasks move with the relevant contact, property, viewing, document, offer, tenancy, or management event?
- Can files attach to the work they support, rather than disappearing into a generic folder?
- Can managers and covering staff see enough to keep work moving while sensitive notes, commission details, tenant information, and internal comments stay controlled?
That last point matters. Shared context does not mean everyone sees everything.
In AvaroAI, collaboration is built around role-aware access rather than a completely open branch notebook. Sales, lettings, admin, and management staff need a shared operating picture, but not the same depth of information. A sales negotiator may need access windows and a pending certificate status without every property management note or sensitive tenancy detail.
Set access permissions around what each role needs to do. If the system controls access by hiding whole areas from one another, staff recreate the missing bridge elsewhere. If it exposes everything, branches create risk and noise. Neither is good branch discipline.
Tasks should carry the branch context with them
Generic reminders are too weak for mixed sales and lettings work.
“Call landlord” is not enough.
Call about what? The rent review? The sales valuation? The expired gas certificate? The buyer who wants a second viewing? The tenant’s notice? The managed property that might be sold?
Useful task design needs context that a colleague can act on. The task should show who owns the next action, which contact, property, viewing, document, tenancy, offer, or listing it belongs to, what someone is expecting, and what stalls if it is missed.
AvaroAI’s task and event handling is designed around linked work rather than floating to-do items. A landlord document chase can sit with the landlord, the property, the listing, and the person responsible for getting it resolved. A viewing feedback task can sit with the applicant, the appointment, and the vendor or landlord update. A compliance handoff can be visible to the person who owns it without turning into a mystery note in a spreadsheet.
Branch staff deal with interruptions all day. Someone covers a colleague’s phone. A manager checks what is stuck. An admin chases a missing file. The task is only useful if it carries enough context for the next person to act without reconstructing the whole story.
Files need to travel with the property relationship
Property work creates evidence.
Photos, floorplans, authority documents, AML evidence, landlord instructions, tenant information, certificates, management agreements, viewing notes, signed forms, and approval trails all matter at different moments.
The weak version of file management is a shared drive with folders named by address and documents named by whatever the uploader happened to type. That breaks when the office gets busy, someone leaves, or the same property moves between sales and lettings.
File and photo management should follow the relationship between contact, property, event, and task.
If a landlord decides to sell, the sales team should not have to ask lettings to forward “the latest bits”. They should be able to see which documents exist, which are relevant, which are outdated, and which task or property stage they belong to.
Try it with a client who uses both teams
Choose a client and property that have involved both sales and lettings, then check the following:
A client should be able to have several roles without being duplicated. A property record should survive changes in strategy, whether sale to let or let to sale. Sales and lettings teams should see shared context without exposing irrelevant sensitive detail. Viewings, offers, applications, tenancy events, and management work should create linked tasks. Files should attach to the property, contact, event, or task they support.
Managers should be able to see stuck work by owner, property, and deadline. Compliance-related evidence should be findable without searching inboxes. Covering staff should continue the work from the system, not from private explanations.
That standard is more useful than a feature grid because it describes the job the software has to do.
Sales and lettings have different processes, but neither team should lose access to relevant information when a client or property moves between them.
Good systems respect the differences between sales, lettings, property management, admin, and branch management. They keep the relationship, property, task, and file history connected enough that the next person can act with confidence.
During a software demo, ask someone from each team to pick up the same file and explain what they would do next.
Related reading
Disclaimer: This page may contain AI-assisted content. The information is provided solely as a general guide and may not be correct, complete, or current, including, but not limited to, our full or applicable service offerings. While we strive for accuracy, no guarantee is made regarding correctness or completeness, and no expectation should be made as such.
