Lawcus can connect intake forms, lead stages, workflows, contacts, matters, tasks, email, documents, and invoices. That range is useful only when the firm defines what each transition means. If a card moves from Prospect to Follow-up but nobody owns the next decision, the software has recorded motion rather than progress. A sound Lawcus intake workflow starts with the firm's real acceptance process and then assigns a record, owner, deadline, and proof to every step.
The highest-risk shortcut is converting a promising inquiry before the firm has completed its required review. A submitted form can trigger a Lawcus workflow, and Lawcus supports a Convert to Matter action, but technical capability is not the same as authorization to open a case. Conflict analysis, engagement approval, jurisdiction, urgency, capacity, fee terms, and signed documentation may require people with defined authority. Automation should prepare those decisions and route exceptions, not silently make them.
This guide builds a maintainable intake path for law firms using Lawcus. It covers pipeline design, form mapping, guarded automation, lead-to-matter conversion, and ongoing measurement. For the surrounding technology environment, use ALLMSP's [Lawcus resource center](https://www.allmsp.com/category/software-support/software-support-lawcus/), [Law Firm IT Services](https://www.allmsp.com/category/law-firm-it-services/), and broader [Software Support](https://www.allmsp.com/category/software-support/) guidance alongside the firm's own professional-responsibility procedures.
Key decisions at a glance
- Design Lawcus stages around decisions and ownership, not around vague labels that allow a lead to remain untouched.
- Use the correct intake-form question types and deliberately map custom fields so submitted information reaches the intended lead, contact, or matter record.
- Keep conflict review, engagement acceptance, scope approval, and other professional judgments as explicit human gates even when surrounding steps are automated.
- Test every workflow with controlled records, negative cases, and Lawcus workflow history before enabling it for live prospects.
- Treat lead conversion as a verified handoff: confirm the contact, matter, pipeline, team, tasks, calendar commitments, documents, and client communication after conversion.
Translate the Firm's Acceptance Decisions Into Lawcus Stages
Begin with a whiteboard version of the current intake process before changing Lawcus. Mark where an inquiry enters, which facts are required for triage, who performs the conflict review, how consultations are scheduled, when the fee arrangement is approved, what counts as engagement, and who may decline a lead. For each decision, record a responsible role, an expected response time, the evidence that closes the step, and the path for urgent or incomplete inquiries. This exercise exposes policy gaps that a new form or workflow would otherwise automate.
Lawcus provides an Intake pipeline and allows its lead stages to be added, renamed, reordered, and removed. Use that flexibility to create stages with unambiguous exit conditions, such as New Inquiry, Triage in Progress, Conflict Review, Consultation Scheduled, Engagement Pending, Hired, and Did Not Hire. The exact names should reflect the firm, but every stage needs an owner and an aging threshold. Avoid mixing status, task, and outcome in one label; 'Waiting' does not say who is waiting, for what, or until when.
Matter pipelines serve a different purpose from the intake pipeline. Define a small number of matter pipelines by repeatable delivery model or practice need, not one pipeline for every attorney. Lawcus notes that a newly created pipeline is not automatically assigned to existing matters, so record the assignment rule and test it at conversion. Keep a controlled dictionary for stage names and prohibit casual edits that would invalidate workflow triggers, reports, or operating instructions.
- List every intake entry point, including web forms, phone calls, referrals, email, scheduler bookings, and manually entered leads.
- Give each lead stage a definition, owner, response target, required fields, and authorized next outcomes.
- Separate lead qualification stages from matter-delivery stages so intake reporting does not become case-status reporting.
- Create exception paths for urgent deadlines, incomplete identity information, duplicate contacts, adverse-party uncertainty, and out-of-scope inquiries.
Build Intake Forms That Create Usable Records
Lawcus intake forms can collect client information, related-contact information, and lead information. Select the question type according to the record the firm expects to create or update; the Lawcus help center specifically warns that incorrect question types can prevent a form from mapping or creating a lead. Decide which fields are essential for triage, which may be requested later, and which should never be collected through an early public form. Data minimization reduces rework and limits unnecessary exposure of sensitive facts.
Create controlled custom fields for information that drives assignment, routing, documents, or reporting. Examples might include practice area, venue, adverse-party names, referral source, deadline indicator, preferred language, and consultation type, but the firm's legal and privacy leaders should approve the actual set. Use stable field names and documented choices instead of free text wherever consistent reporting matters. Before launch, submit test answers containing blanks, multiple related contacts, punctuation, long descriptions, and known duplicate contacts to confirm where each value lands.
Separate client-facing questions from internal determinations. A prospect may identify people involved in a dispute, but that response is input to a conflict process rather than proof that the firm cleared a conflict. Likewise, a prospect-selected practice area does not establish scope. Write plain-language form instructions, explain how urgent deadlines should be communicated, provide an accessible alternative, and review the resulting lead record before relying on any automation that consumes its fields.
- Inventory every intake question and identify its destination field, business purpose, data owner, retention need, and sensitivity.
- Use Lead Information when the submission should create or populate a lead, and verify the behavior with a controlled test record.
- Map related parties consistently so the firm can search and review names without treating the form itself as a completed conflict check.
- Test mobile completion, confirmation messages, duplicate handling, optional fields, resubmission behavior, and internal response visibility before publishing a link.
Automate Repetition While Preserving Approval Gates
Lawcus workflows begin with documented triggers such as Lead Created, Lead Moved to Stage, Intake Form Submitted, eSign Document Signed, or User Activated. Actions can add tasks and events, send communications, generate intake links, create documents, invite a client, or convert a lead into a matter. Build the smallest workflow that produces one accountable outcome, then chain additional steps only after its inputs and failures are understood. A single enormous workflow is difficult to test, explain, and safely change.
Place a visible approval checkpoint before any action that depends on professional judgment. For example, an intake submission can create a triage task and notify the assigned reviewer; a cleared review plus an approved engagement stage can then permit document or conversion steps. Use filters and logic conditions to branch by practice area or urgency, and use time delays only when the delay remains appropriate if facts change. Do not let an unattended timer send a representation-suggesting message after a lead was declined or circumstances materially changed.
Test with a purpose-built lead and matter, which Lawcus recommends for automation testing. Exercise the intended route, a missing-field route, an excluded practice area, a duplicate person, a declined lead, and a workflow paused midway. Inspect workflow History and the recent task events, confirm each message recipient and merge value, and document how staff will recognize and recover an unsuccessful action. Activation should require a named owner, approval date, version note, and rollback instruction.
- Name workflows with process, trigger, audience, and version so administrators can distinguish similar automations.
- Use filters for eligibility and reserve stage changes for decisions that staff can explain and evidence.
- Test recipient lists, merge fields, task assignees, due dates, time zones, document outputs, and duplicate-trigger behavior.
- Review workflow history after launch and route failed or unexpected events to a monitored owner instead of assuming every action completed.
Verify Conversion and Run Intake as an Operating System
When a Lawcus lead is converted, the platform creates or uses the contact, creates a matter, assigns a matter number, and opens the matter details. Treat that moment as a handoff checklist rather than the finish line. Confirm client identity, related contacts, matter description, responsible members, practice area, pipeline and stage, billing preference, custom fields, and any restricted-access requirement. If automation performed the conversion, a person should still validate the resulting record before substantive work begins.
The opening checklist should also confirm tasks, deadlines, calendar events, engagement documents, invoice or trust steps where applicable, file locations, and the first approved client communication. Assign an owner to reconcile anything that did not map from the lead. If a prospect does not hire the firm, use a controlled reason taxonomy and notes appropriate to the firm's policy; consistent outcomes make the intake pipeline useful without inviting unnecessary narrative or sensitive detail.
Review intake performance as a service, not a one-time configuration. Track unassigned inquiries, stage aging, forms with mapping errors, declined-reason quality, workflow failures, conversion exceptions, duplicate contacts, and matters opened without the required checklist. Sample records monthly and review pipeline design quarterly or after practice, staffing, form, or fee changes. Teams that need help connecting process and technology can use [ALLMSP Cybersecurity](https://www.allmsp.com/category/cybersecurity/) for related control guidance or [contact ALLMSP](https://www.allmsp.com/contact-us/) for a scoped Lawcus support discussion.
- Require a post-conversion check covering identity, matter number, team, pipeline, stage, billing, custom fields, restrictions, and related parties.
- Reconcile opening tasks, dates, documents, messages, and financial setup against the approved engagement and matter-opening policy.
- Measure stage aging, orphaned leads, unsuccessful workflows, unmapped fields, duplicate records, and conversion reversals.
- Preserve a change log for forms, fields, stages, pipelines, and workflows, including owner, reason, test evidence, and effective date.
Vendor documentation and ALLMSP resources
- Lawcus: How to Add a Client Intake Form
- Lawcus: Add, Edit, Delete, and Convert Leads
- Lawcus: Manage Lead Stages
- Lawcus: Add and Manage Matter Pipelines
- Lawcus: Understand Automation and Create a Workflow
- Lawcus: Automate Lead Conversion to Matter
- Lawcus: Check Workflow History
- ALLMSP Lawcus
- ALLMSP Law Firm IT Services
- ALLMSP Software Support
- ALLMSP Cybersecurity
- Contact ALLMSP
Frequently Asked Questions
What should a Lawcus intake workflow accomplish?
It should turn every inquiry into an owned, time-bound decision with the required information and a documented outcome. The workflow should make triage, conflict-review input, consultation, engagement, decline, conversion, and matter opening visible without allowing automation to replace authorized professional judgment.
Which Lawcus intake-form question type creates a lead?
Lawcus says to use the Lead Information question type when the form should create or populate a lead. Test the exact form with a controlled submission because custom fields, related contacts, optional answers, and duplicate records can affect the result the team sees.
Can Lawcus automatically convert an intake submission into a matter?
Yes. Lawcus documents an Intake Form Submitted trigger and a Convert to Matter workflow action. A firm should place eligibility and human approval gates before conversion whenever conflict review, scope, engagement, jurisdiction, capacity, or financial approval is still unresolved.
How should a firm name lead stages in Lawcus?
Use names tied to a real decision or completed state, such as Triage in Progress, Conflict Review, Consultation Scheduled, or Engagement Pending. Define the owner, required evidence, response target, and permitted next outcomes for each stage so the label communicates action rather than vague waiting.
Are Lawcus lead stages and matter pipelines the same?
No. The intake pipeline tracks a prospect toward a hire or decline outcome, while matter pipelines track delivery after opening. Keep the two models distinct and verify which matter pipeline and stage are assigned during conversion.
Should adverse-party names on an intake form be treated as a conflict clearance?
No. Those names are inputs to the firm's conflict process. The firm must apply its approved search, analysis, documentation, and escalation procedure before treating a potential engagement as cleared.
How can a firm test a Lawcus workflow safely?
Use designated test leads and matters, non-client addresses, and representative branches. Exercise missing data, duplicates, exclusions, declines, pauses, and retries; inspect workflow History; verify recipients and generated records; then document the owner, approval, version, and rollback method.
What should be checked after a Lawcus lead converts to a matter?
Confirm the contact, related parties, matter number, description, members, pipeline, stage, billing preference, custom fields, access restrictions, tasks, dates, documents, and first client communication. Assign any mapping discrepancy to a named person before substantive work begins.
How often should Lawcus intake workflows be reviewed?
Review failures and aging frequently, sample records monthly, and perform a structured design review at least quarterly. Reassess sooner after a practice-area change, new form, staffing change, fee-model change, integration update, or material incident.
Which intake metrics are useful in Lawcus?
Useful measures include unassigned inquiries, time in stage, incomplete forms, mapping errors, workflow failures, duplicate contacts, decline-reason quality, conversion reversals, and matters opened without required checks. Interpret conversion rates alongside lead quality and professional obligations rather than optimizing for volume alone.
