Key takeaways
- Map how an enquiry becomes a matter before buying any connector; most waste sits in the hand-offs.
- Give every field one system of record, and let other systems read from it rather than keep their own copy.
- Match callers on a normalised phone number, and decide what happens with duplicates before go-live.
- Joined-up systems help with what clients complain about most: poor communication and delay[1].
- Start with one integration, test it with real calls, then add the next.
The cost of typing the same thing twice
In many firms, a new client's name is typed four or five times: into the call log, the enquiry form, the conflict search, the client record, the matter and the first bill. Each retype costs time, introduces errors and delays the next step. A misspelt name can let a conflict slip through; a wrong phone number turns a call-back into a lost client.
Retyping is usually done by support staff whose time is valuable. ONS provisional data puts median gross hourly pay for UK legal secretaries at £14.95 in 2026, up 5.4% on the year[2]. Example: if three people each spend 30 minutes a day moving details between systems, that is over 350 hours a year, before counting the cost of fixing mistakes. Integration is less about technology and more about getting that time back for client work.
Map the data journey first
Before choosing a connector, draw how information moves today. Use a real enquiry from last month and follow it step by step:
First contact
A call, web form or email arrives. Note where the details are first recorded and by whom.
Enquiry record
The details become an enquiry or lead. Note which system holds it and which fields are captured.
Conflict check
The client and other party names are searched. Note whether they are retyped for the search.
Client and matter
An accepted enquiry becomes a client and a matter. Note every field that is entered again.
Engagement and ID
Client care letter, ID checks and money on account. Note which system sends and records each.
Ongoing contact
Calls and emails during the matter. Note whether they are logged against it and how.
Mark each place where the same data is typed again. Those marks are your integration shopping list, in priority order.
Integration patterns, from simple to deep
| Pattern | What it does | Effort | Watch out for |
|---|---|---|---|
| Click-to-dial | Call a number from the CRM or case management screen | Low | Calls still need logging |
| Screen pop | Shows the caller's record when the phone rings | Low to medium | Wrong matches on shared numbers |
| Automatic call logging | Records each call against the client or matter | Medium | Volume of trivial entries |
| Web form to CRM | Website enquiries create records directly | Low | Spam and duplicate records |
| Enquiry to matter | Accepted enquiry creates the client and matter with fields mapped | Medium to high | Field mapping and conflict check timing |
| Middleware or automation platform | Moves data between systems on triggers | Medium | Another system to secure and maintain |
| Scheduled export and import | Batch transfer, for example nightly | Low | Data is out of date in between |
Screen pop and call logging deliver quick wins: staff see who is calling and every call lands on the file. Enquiry-to-matter integration removes the most retyping but needs careful field mapping and a clear rule on when the conflict check happens. Middleware is flexible but becomes a system in its own right, with its own access keys and failure modes.
One system of record for each field
Integration fails most often because two systems both think they own the same data. Decide, field by field, where the master copy lives:
- Client contact details: usually the case management or practice management system once a client exists, and the CRM before that.
- Enquiry source and marketing consent: the CRM.
- Matter details, key dates and fee earner: case management.
- Call recordings and transcripts: the phone or call-handling system, linked from the matter rather than copied into it.
- Billing and ledger data: the accounts system only.
Other systems should read from the master or receive one-way updates. Two-way sync of the same field sounds convenient and causes the most confusing errors.
Matching callers to records
Screen pop and automatic logging depend on recognising the caller. Store phone numbers in one consistent international format in every system, so a number entered as a local mobile and the same number shown by the phone system as +44 match. Decide what happens when one number matches several records, such as a couple with a joint landline or a company switchboard: show a choice, never guess. And treat withheld numbers as unknown rather than matching them to the last caller.
Why clients notice the difference
Joined-up systems are not just an efficiency project. Poor communication (24%) and delay or failure to progress (22%) were the most common complaint types brought to the Legal Ombudsman in 2025/26, and poor communication was also the largest upheld type, at 25%[1]. When call history, notes and key dates sit on the same screen, the person answering can tell a client what is happening without promising a call back.
- Complaints brought
- Complaints upheld
Source: Legal Ombudsman, 2026[1]
Show the data
| Item | Complaints brought | Complaints upheld |
|---|---|---|
| Poor communication | 24% | 25% |
| Delay or failure to progress | 22% | 19% |
Clients describe the opposite experience vividly. In research for the Consumer Panel, some described follow-up emails that went unanswered for weeks and not knowing who to contact[3]. 17% of consumers would have preferred more contact with a legal professional, rising to 24% of those served by telephone[4], and the phone remains the most common way people talk to their main adviser on a contentious issue, at 28%[5].
Where AI call handling fits
An automated call assistant adds another source of data: structured enquiry notes, recordings and transcripts. Treat it like any other system. Decide which fields it creates, where its notes land and who is told. Ava, for example, hands each call over as a note with a summary, recording and transcript and notifies the right person; a direct connection to practice management systems is Planned and needs a separate access and feasibility review. Until a direct connection exists, a consistent note format makes manual transfer quick and accurate.
Security and data protection
- Give each integration its own account or key with the least access it needs, never a partner's login.
- Record who set up each integration, what it can read and write, and how to switch it off.
- Check that any middleware supplier is covered by a processor contract and stores as little as possible.
- Turn on logging, and review failed or unusual transfers weekly at first.
- Remove access when an integration is retired or a supplier changes.
Testing an integration before you rely on it
An integration that silently drops one record in fifty is worse than none, because staff stop checking. Before switching off the old manual step, run both side by side and check:
- Every test call, form and enquiry arrives in the target system, with no duplicates.
- Each mapped field lands in the right place, including names with apostrophes, hyphens and accents.
- Dates and times are correct, including around the clock change.
- Records created out of hours appear in the right queue the next morning.
- Someone is alerted when a transfer fails, rather than the failure showing only in a log nobody reads.
Keep a short test script and rerun it whenever either system is upgraded, because supplier updates are the most common reason a working integration stops working.
When not to integrate
Not every hand-off is worth automating. If a step happens a few times a month, needs judgement each time or involves a system the firm is about to replace, a clear manual procedure is often better than a connector that must be secured and maintained. The same applies to anything touching client account money: keep payments and ledger entries inside the accounts system, with its own controls, rather than letting another system write to it.
Rolling it out
Start with the integration that removes the most retyping for the least risk, often screen pop and call logging or web forms into the CRM. Test with real calls and enquiries for two weeks, compare records against the source, then add the next. Example: a fictional firm connected its phone system to its case management first, so every call logged automatically against the matter, then mapped accepted enquiries into new matters three months later. Retyping fell, and receptionists could see at a glance whether a caller's fee earner had been in touch that week. For budgeting this work, see technology budget planning for law firms, and for the provider who maintains it, see managed IT support for law firms.
Frequently asked questions
What should a law firm integrate first?
Usually the step with the most retyping and least risk, such as showing the caller's record when the phone rings and logging calls automatically against the matter, or sending website enquiries straight into the CRM.
Should our CRM and case management sync both ways?
Avoid two-way sync of the same field. Give each field one system of record and let other systems read from it or receive one-way updates.
How do we match callers to client records?
Store numbers in one consistent international format in every system, show a choice when one number matches several records and treat withheld numbers as unknown.
Is middleware safe to use for client data?
It can be, with its own limited-access accounts, a processor contract, minimal data storage and regular review of logs and failed transfers.
References
Legal Ombudsman (2026). Legal Ombudsman 2025/26 annual complaints data and insight (opens in a new tab) ↑
Office for National Statistics (2026). Earnings and hours worked, occupation by four-digit SOC: ASHE Table 14 (2026 provisional) (opens in a new tab) ↑
Legal Services Consumer Panel (2025). Service Delivery Research Report (M·E·L Research for the LSCP) (opens in a new tab) ↑
Legal Services Consumer Panel (2026). How consumers are using legal services (Tracker Survey 2026) (opens in a new tab) ↑
Legal Services Board (2024). Legal Needs Survey 2023: Summary report (opens in a new tab) ↑