Clio-Connected Disability Intake: Separate Initial Claims, Appeals, and Existing Clients

By Michael Brunman, Co-Founder and CEO of Clerx

The direct answer

A Clio-connected disability intake workflow should distinguish new initial-claim inquiries, requests concerning a denial or appeal, and messages from existing clients. It should preserve the caller's own description, identify any reported notice or timing concern for prompt staff review, and send a useful record to the firm's configured Clio destination. It should not decide eligibility, calculate a filing deadline, or promise representation.

For a small disability practice, the problem is often an undifferentiated message queue. "Needs disability help" tells the team very little. A record that says the caller reports receiving a decision, is unsure of the date, and requests a callback gives staff a clearer review task.

The Clerx and Clio integration describes intake information, contacts, matters, summaries, and calendar connections. Confirm the specific record-creation policy and field mapping before relying on them. An integration relationship alone does not define your firm's disability screening process.

Ask what kind of disability request it is

Begin with a plain question: "Are you contacting us about applying for benefits, a decision you received, or a matter our office is already handling?" Include an "unsure" route. People should not need to understand administrative terminology to reach the right team.

Next identify the broad program or source of the issue, if known. Social Security disability benefits, a private long-term-disability policy, and an employment accommodation question are different requests. A firm that handles several of them needs distinct operational branches.

The disability and ERISA intake overview covers the broader practice opportunity. This workflow focuses on Social Security-related inquiries. Do not transfer SSA timing statements or process assumptions to private insurance or employment matters.

A caller who says "my disability was denied" may not know which program made the decision. Preserve the uncertainty and assign review rather than making the classification sound more certain than the source information.

Use the initial-claim branch sparingly

For a person asking about beginning an application, collect contact details, location, the general request, and the minimum firm-approved screening information. Ask only what the team needs to determine whether to arrange a consultation or further review.

Avoid asking the caller to recite a full medical history during the first exchange. The fact that someone is willing to share sensitive information does not mean the receptionist needs it. Direct document collection to the firm's approved secure process when appropriate.

The progressive intake-questions guide supports this sequence. Save detailed information gathering for the stage where the firm knows what it needs and who should have access.

Keep operational screening separate from legal and medical conclusions. The system should not tell a person that their condition qualifies, that a claim will succeed, or that a particular fact defeats eligibility. Those are not receptionist decisions.

Preserve notice information without calculating the deadline

An appeal-related inquiry deserves a route that makes timing visible. Ask whether the caller received a decision or notice, what they call it, and any date they can supply. Label those details as reported and unverified until staff review the document.

The Social Security Administration's appeals information describes time limits and circumstances where shorter periods can matter. That complexity is a reason to route notices promptly, not to build an improvised countdown into a general intake script.

Do not say, "You have plenty of time," or offer a calculated due date based on incomplete information. If the caller cannot identify the document, keep the inquiry moving to a designated reviewer. Record the inability to confirm a date instead of replacing it with today's date or an assumption.

A notification should preserve the original timing concern. For example: "Caller reports a recent denial letter; date not confirmed; requests review." Staff then determine urgency and the appropriate professional response.

Give existing clients their own path

Existing clients may call about a hearing, requested records, a status question, or a letter they do not understand. Sending them through a new-prospect questionnaire wastes time and may create a duplicate record.

Use the new-lead and existing-client routing framework to identify the right branch early. Verify identity before sharing information and follow the firm's limits on what can be provided through the intake channel.

Donna's inbound call workflow can gather the reason for the call and route a message according to approved rules. Do not assume that every Clio field is readable to the receptionist or that every case update can be disclosed automatically. Demonstrate the actual configured access.

If a client reports a new notice, preserve the report for the team even if the initial reason for calling was a routine update. The intake process should make consequential information visible without interpreting it.

Define what goes into Clio

Agree the destination for each branch: a contact or intake record, an approved matter-creation path, an interaction summary, a calendar event, or an exception requiring staff action. Use what the integration actually supports and assign remaining tasks explicitly.

A useful handoff includes who called, whether they report being an existing client, the broad benefit category, stage as stated, notice information if supplied, contact preference, requested next step, and review owner. Separate reported information from staff-verified information.

The practice-management versus intake distinction helps keep the scope clear. Clerx supports the front-door conversation; Clio organizes the firm's working records. Legal analysis and acceptance decisions remain with the lawyer.

Check how repeat calls are associated. The same person asking a second question should not automatically become a second new lead. A caregiver using a shared phone should not automatically be matched to a claimant's confidential record.

Clio's own Clerx listing distinguishes two destinations. It describes communication entries and caller information in Clio Manage, with contacts matched by phone number or created for unknown callers. It separately describes new prospects reaching the Clio Grow Inbox with contact details and call notes. Confirm which product your firm uses and how the branch information will be retained. A Grow lead and a Manage communication entry are not interchangeable outputs.

Keep written channels accessible and purposeful

Some callers will prefer a short text or website conversation. Others will need phone assistance or help from a family member. Offer channels the firm can actually support without making access dependent on one format.

Clerx website chat and Clerx text messaging can collect approved intake details and support booking. Test whether the resulting record carries the same branch, uncertainty, and next action as a phone inquiry.

Use neutral notifications and confirm communication preferences. Avoid sending sensitive medical or benefits information to a number merely because it appeared on the first inquiry. If a helper is involved, keep the helper's role distinct from the prospective client's identity.

The SSA's representative information describes formal representation processes. A receptionist conversation or consultation booking should not imply that those steps have occurred.

Set a review target the team can maintain

The owner should decide which inquiries need prompt attention and what internal review target applies. A small firm may use a simple daily queue with a separate alert for reported notices. The important part is a named reviewer and an observable next step.

Use the intake ownership and escalation guide to document responsibility. Distinguish an internal operating target from a guaranteed client-facing response time. Do not publish a promise that depends on staff who are unavailable.

If a transfer is appropriate, test the unanswered case using the warm-transfer guide. The fallback should make the request visible and describe the next step accurately. An attempted transfer is not a completed handoff.

Test three branches and the uncertain case

Use fictional examples: a first-time applicant, a caller reporting a denial with an unclear date, an existing client asking about a letter, and a person who cannot identify whether the issue is Social Security or private insurance.

Inspect the resulting records rather than judging only the spoken call. Check whether the original wording survives, the branch is accurate, sensitive detail is limited, and a review owner exists. Use the receptionist go-live testing process to document results and corrections.

A useful pilot measures staff clarification work, misrouted inquiries, unowned requests, and completed next steps. It does not claim that a better intake system changes benefit eligibility or guarantees a favorable decision.

A worked uncertain-notice example

Imagine a prospective client who calls a two-attorney disability practice and says, "I got a letter saying no, but I do not have it with me." The caller does not know the program or the date. An intake process that requires a complete appeal category may encourage a misleading selection merely to advance the form.

A better record preserves the uncertainty. It identifies the person, contact route, description of the letter, and request for review. The next step is the firm's approved process for obtaining or examining the notice, with an owner assigned. The receptionist does not convert "recently" into a fabricated date.

If the caller also reports being an existing client, the team should resolve identity and route the message accordingly. Do not discard the notice concern just because the contact follows an existing-client path.

Use this fictional example in the demonstration and compare the spoken exchange with the Clio output. Ask whether a staff member reading only the summary would understand what remains unknown and what they must do next. That is the acceptance test. It should not require the employee to infer urgency from a generic label or listen to the full recording before identifying the work.

Frequently asked questions

Does Clio decide disability eligibility through this workflow?

No. This is an intake and record-handoff design. The lawyer evaluates legal issues and the relevant authority decides benefits. A software connection should not be represented as an automated eligibility determination.

Should every denial call receive the same response?

No. Preserve what the caller reports and route the notice for appropriate review. Program, stage, document type, and timing may differ. Avoid assuming that every use of the word "denial" means the same process.

Should the receptionist calculate appeal deadlines?

This workflow does not use the receptionist to calculate them. Capture the caller-reported information, flag uncertainty, and send the document through the firm's approved review process. Staff determine the appropriate action and timing.

What if the caller does not know whether they applied for SSI or SSDI?

Include an unsure branch and preserve the caller's description. Staff can clarify the program during review. The initial conversation should not force a confident classification simply to complete a required field.

Can an existing client use the same number?

Yes, with an early routing question and identity verification before disclosure. The workflow should preserve the message in the appropriate place and avoid making the client repeat a complete new-prospect screening.

Does intake create a matter automatically?

The public Clio integration describes contact and matter creation capabilities. Your firm should approve when each action occurs and test it. Not every inquiry should become an accepted matter or imply representation.

Can a family member help with the inquiry?

Intake can capture the helper's role and the person needing assistance. Do not assume that helping with a call establishes authority to receive confidential updates or act as the claimant's appointed representative.

What makes a useful demo for a disability practice?

Ask to see the four test scenarios and the downstream Clio records. Require visible uncertainty, clear branch selection, and a review owner. Those details show more than a generic demonstration of a new contact being created.

Book a demo with Clerx today.