CRM and client intake for law firms
An enquiry should not depend on someone remembering which inbox it reached or who last spoke to the prospective client. A reliable intake process makes responsibility visible and helps the firm move an appropriate request towards the right next step.
Discuss an intake and CRM review
Webvelopment scopes CRM and intake workflows around the firm’s people, services and professional procedures. The work connects capture, contact, administrative screening, consultations and approved handover without treating automation as a replacement for a practitioner.
Where intake breaks down
A person calls while the relevant staff member is unavailable. A website enquiry arrives after hours and is forgotten. A consultation is booked without clear fee expectations. A record is marked qualified, but no one agrees what that label means. These are different problems, and each needs a defined response.
A CRM can help only when the underlying process is clear. Moving an inconsistent spreadsheet into a more expensive platform does not resolve unclear ownership or missing professional review.
Design the stages before choosing the software
A useful intake journey distinguishes receipt, assignment, contact attempts, established contact, administrative screening, consultation progression, attendance and the firm’s acceptance decision. It also records the branches that matter: duplicates, unavailable capacity, unsuitable requests, stop-contact instructions and no-shows.
The names can fit the firm’s language, but the definitions must remain consistent. A booked consultation is not the same as an attended one. A payment is not an automatic acceptance of a matter. A single person may have more than one enquiry, so deduplication should not erase distinct requests.
Keep professional decisions with the firm
Intake staff can explain the approved process, confirm contact details and route an enquiry. They should not be expected to determine legal merits or clear a conflict through a marketing score.
The firm’s professional workflow should determine when additional identifying information is required, who reviews it and when more detail may be collected. The system should record the authorised decision and next step, not make that decision on its own.
What the scope can include
Capture and routing
Connect approved web, phone, email and messaging routes to a central workflow. Preserve source information and original timestamps. Assign a responsible person, a fallback and a visible queue for exceptions.
Contact and follow-up
Set realistic response targets from actual staffing and coverage. Separate an automated acknowledgement from a human attempt. Record communication preferences and stop requests. Keep follow-up purposeful rather than simply increasing the number of messages.
Consultation workflows
Connect scheduling, clear expectations, approved fee arrangements, confirmation, rescheduling and attendance. Use neutral reminder content and an appropriate no-show process. Payment and professional acceptance remain separate controls.
Handover and reporting
Pass the necessary approved information into the next system or team. Track pending decisions and incomplete handovers. Give managers visibility into ageing, ownership and conversion definitions without exposing unnecessary case information.
A stage model you can report on
The stages below are a starting point. Names can change to suit the firm; meanings can’t change once reporting starts:
- Received: the enquiry exists, with its source and original timestamp.
- Assigned: a named person owns it, with a fallback.
- Contact attempted: a human tried to reach the person. An automated acknowledgement doesn’t count.
- Contact established: a conversation actually took place.
- Administrative screening: service, area and capacity checked against the firm’s rules.
- Professional review: a practitioner looks at it, where the firm requires that.
- Consultation booked: a time, attendee, fee expectation and rescheduling route are agreed.
- Attended: the consultation happened.
- Acceptance decision: the firm decides, through its own procedure.
- Matter handover: approved information passes to practice management.
Duplicate, out of scope, no capacity, stop-contact and no-show are explicit branches, not silent dead ends. One person can have several enquiries and matters, so contacts, enquiries and matters stay separate records. Deduplicating a phone number must never merge two people’s disputes.
Respect the person’s communication context
Some legal enquiries are sensitive even before a matter exists. The firm should establish whether the preferred phone number, email or messaging route is safe to use. A reminder visible on a lock screen should not disclose more than necessary.
Requested-service communication and unrelated marketing are different purposes. A consultation enquiry should not silently enrol someone in an ongoing newsletter or reactivation sequence. The firm approves notices and communication rules before automation is enabled.
Start with the system you have
The current CRM or practice-management software may already support the required stages and permissions. Configuration, training or a narrow integration can be more appropriate than replacement.
Where a new tool is needed, evaluate workflow fit, access control, export, support and integration behaviour. Product names are not a substitute for a tested journey. The proposal should say what will be configured and how it will be accepted.
What should be tested
Walk through ordinary and difficult cases with synthetic data: an after-hours enquiry, an unavailable owner, a duplicate, a new request from an existing person, a potential conflict, a rescheduled appointment and a failed integration. Show where each appears and who resolves it.
Training should cover definitions, communication boundaries and escalation, not only where to click. A workflow is complete when the people operating it understand what happens next and can identify an exception.
The scenarios we sign off
Acceptance is a list of situations the workflow must handle, tested with synthetic records before anyone relies on it:
| Scenario | What should happen |
|---|---|
| Enquiry arrives after hours | An honest acknowledgement and the next coverage window, with no false promise of an immediate call |
| Owner unavailable | A named fallback or a visible queue, not silent abandonment |
| Potential conflict | A restricted review task, with no automatic clearance and no wider disclosure |
| Existing contact, new matter | A new enquiry linked to the person, not merged into the old one |
| Stop request | Relevant contact suppressed and the request recorded |
| Payment received, review pending | Payment recorded; the matter stays unaccepted until the firm decides |
| Consultation rescheduled | One consultation journey, not a new lead in the report |
| Integration failure | A monitored retry or exception, with the original timestamp preserved |
Training covers the definitions, tone, boundaries and escalation, including how to handle unsuitable or pro bono requests respectfully. Quality isn’t pressure to convert every person who calls.
We run our own business on a CRM we built
Clienthub, the system that runs our own billing, client relationships and project management, has been built in-house and refined for 13 years. We know what it takes to make a CRM that people actually use every day, and how quickly a system nobody trusts gets replaced by a spreadsheet.
We’ve also built integrations with Zoho, Salesforce, Leadtrekker and Basecloud, among others, so connecting a web form, a phone system or a calendar to the firm’s chosen platform is familiar ground. See our API integrations service for more.
Questions about intake
A few useful answers before you decide.
Does this include people answering our calls?
Can the system automatically accept clients?
How do we know the changes are helping?
Make the next step reliable
For an early sense of scope, try the integrations estimator or the automation estimator.
Discuss your intake workflow, read the consultation-conversion guide or return to the law-firm solution.
Keep the right things connected.
Digital growth and technology for law firms
Connect legal-practice marketing, websites, client intake, CRM, automation and commercial reporting around a clearer route from enquiry to accepted work.
Law-Firm Client Intake: A Better Route from Enquiry to Consultation
A practical operating model for enquiries, consultations and professional handovers, with clear responsibility at every stage.
Law-Firm CRM and Practice Management: Configure, Integrate or Build?
A procurement and implementation framework for connecting intake to the practice without replacing professional control.
API integrations with the systems South African businesses run on
We connect websites, CRMs, dealer systems, credit bureaus, vehicle finance, payments and AI, from Autotrader and Evolve to TransUnion, WesBank and OpenAI.
Start a conversation
Tell us what you are working towards. We’ll help you find a practical next step.