Clio vs PracticePanther Client Intake Join, 2026

Clio and PracticePanther are practice-management systems. They are not interchangeable with Zapier, and they are not interchangeable with US Tech Automations. The job on this page is web-form to matter: freeze the required fields, keep the conflict check human, create the contact, create the matter, store the source form, and refuse to auto-send an engagement letter. List prices, API quotas, and named intake modules for both vendors are UNKNOWN until a vendor page that actually opened can be quoted.

Lawyers are classified under SOC 23-1011 according to the U.S. Bureau of Labor Statistics. That code does not tell you which practice-management SKU to buy. It does tell you why a skipped conflict check is not an intake optimization. A composite firm that pastes web-form leads into a matter at 5 p.m. is doing intake. A composite firm that lets a script open a matter before a human searches names is building a malpractice file.

Key Takeaways

• Clio and PracticePanther are PMS products. The join is form to matter. Orchestration is a different layer.

• Clio list price: UNKNOWN. PracticePanther list price: UNKNOWN. Clio API quota: UNKNOWN. PracticePanther API quota: UNKNOWN. Do not fill those cells from memory.

• Conflict checks stay human. Automation that skips conflicts is a malpractice story, not a blog.

• Do not auto-send an engagement letter. Store the source form. Notify the assigned attorney. Queue duplicate names.

• Growth $372/mo annual and 150 API calls per flow per day are dated orchestration facts as of September 1, 2026. A Clio write plus a calendar write plus a document write is 3 calls, not 1.

• Zapier instant-trigger traffic is capped at 20,000 requests per 5 minutes per user. Count that separately from PMS quotas you have not opened.

• Pilot: 1 practice area, 15 leads, human conflicts, a matter with a source-form link. Kill the pilot if a letter auto-sends. Keep trust accounting out.

Practice management is not the integration layer

A practice-management system stores contacts, matters, time, and documents. An integration layer writes those records from a web form without a person re-keying every field. Mixing the two produces a shopping question that cannot be answered: which PMS has "intake automation," as if a checkbox replaced conflicts, engagement letters, and API math.

Current-client conflicts sit in Model Rule 1.7 according to the American Bar Association. A script can assemble a name list. A script cannot decide whether a former client, a related entity, or a positional conflict blocks the matter. Step 2 of the join is a human search and a human decision. If your firm wants that step gone, stop reading. This page will not help you.

Legal matter intake automation covers the wider intake category. Calendar conflict checks across attorneys covers scheduling conflicts, which are not Rule 1.7 conflicts. Keep those pages in their lanes. This page is Clio versus PracticePanther on form-to-matter writes, with UNKNOWN commercial cells left UNKNOWN.

Dated facts you can use on September 1, 2026

Orchestration facts you may date today: Growth $372/mo annual and 150 API calls per flow per day as of September 1, 2026. Instant-trigger traffic is capped at 20,000 requests per 5 minutes per user according to Zapier. Those numbers are not Clio quotas and not PracticePanther quotas.

Clio published 0 list-price dollars on the pages this article could open according to Clio (checked September 1, 2026). PracticePanther published 0 list-price dollars on the pages this article could open according to PracticePanther (checked September 1, 2026). Feature names, SKU ladders, Grow-versus-Manage splits, and intake-form modules stay UNKNOWN. If a later fetch opens a pricing table, quote that table with a date. Until then, the comparison still works: both products are PMS, both can receive a matter write, and neither is allowed to skip conflicts.

Do not treat a Zapier task count as a PMS API quota. Do not treat 150 orchestration calls as a Clio limit. Count each write. A matter create is one call. A calendar create is a second call. A document push is a third call. Three writes against a 150-call daily cap is 3, not 1. Limit math that belongs in a dedicated API-cap article stays there. This page only warns you not to undercount.

Trust-account setup is a different job. Firms that need that map should use Clio trust-account setup and keep it out of the 15-lead intake pilot. Billing ROI is another lane: law-firm billing automation. Review-request routing is a third: legal review-request automation. Intake that silently opens a trust deposit is a failed pilot.

How we evaluated Clio versus PracticePanther for intake

Evaluation used 5 tests that do not require a list price: is the product a PMS, can a matter exist as a record, must conflicts stay human, may an engagement letter auto-send, and did a public SKU dollar appear on September 1, 2026. Products that fail the conflict test fail the page, regardless of forms.

Neither product wins a price row. Neither product wins an API-quota row. The reader who needed those rows should open the vendor pages and paste the dated cells into the TCO sheet below. A blog that fills them from training data is the failure mode this comparison exists to prevent.

Nine intake steps that stay honest

Nine steps write a matter without pretending a PMS is an ethics engine. Step 2 is non-negotiable.

1. Freeze required matter fields. Practice area, opening date, source, assigned attorney, adverse-party fields your conflicts team actually searches, and any custom field your reports require. If a field is optional in the PMS and required in your conflicts search, it is required here.

2. Conflict check stays human. The join may assemble names from the form. A person runs the search, reads the hits, and records a yes, no, or escalate. No matter is created on a "probably clear" flag.

3. Create the contact. One contact record, not a duplicate of last month's intake with a new email. Duplicate names go to the exception queue in step 9, not into a second contact.

4. Create the matter. Only after step 2 is recorded. The matter number, practice area, and assigned attorney come from the frozen field list, not from a default user named Admin.

5. Store the source form. PDF, URL, or native form record. If the matter cannot show where the lead came from, the pilot failed even if the matter exists.

6. Do not auto-send an engagement letter. Letters go out after a human confirms scope, rate, and conflicts. A script that emails a letter on matter-create is a kill switch, not a feature.

7. Notify the assigned attorney. A queue, a task, or an email. Notification is not approval to start work. Notification is a clock start for the human who still owns the file.

8. Count API calls against the 150-call daily cap. Matter write, calendar write, and document write are three calls. If the flow also writes a task and a note, that is five. Stop adding "just one more" object until you have counted.

9. Exception queue for duplicate names, failed conflicts, missing required fields, and any lead that wants a trust deposit on day one. Exceptions are not silently dropped.

US Tech Automations can connect the web-form submit to contact-create and matter-create after the human conflict flag is stored, queue duplicate names, and refuse the engagement-letter send. Firms that already have a native form-to-matter path inside the PMS should reverify that path before adding a second writer. Two writers will duplicate matters.

Feature matrix: form to matter

Cells that were not opened stay UNKNOWN. Yes and No below are policy rules for this join, not vendor marketing claims.

Pricing and API quotas that stay UNKNOWN

A TCO sheet with UNKNOWN cells is still a TCO sheet. Filling Clio or PracticePanther from a third-party roundup is not allowed.

Contact each vendor for the current SKU. Contact the vendor developer portal, once it opens without a challenge page, for the API quota. Until those pages open, the only dated call math on this page is 150 orchestration calls per flow per day and Zapier's 20,000-per-5-minutes instant-trigger cap.

Offices of lawyers sit in NAICS 541110 according to the U.S. Census Bureau. That code does not set a PMS price. Confidentiality of information sits in Model Rule 1.6 according to the American Bar Association. Storing the source form inside the PMS is the default. Emailing the raw form to a shared inbox is how intake leaks.

Dated numeric controls you can copy

Copy dated caps and pilot counts. Do not copy invented conversion rates.

Why the 150-call cap matters on this page

A firm that asked only about API limits does not need a second PMS comparison. A firm that still pastes forms into matters does. The two questions collide when the join writes more objects than the daily cap. Fifteen leads with three writes each is 45 calls if nothing retries. Fifteen leads with five writes and one retry each is more than 45. The cap is 150 per flow per day. Burst traffic on Zapier is a different ceiling: 20,000 requests in 5 minutes per user.

Do not re-explain Zapier task billing here. Do not treat a Zapier task as a Clio API call. Do not treat an orchestration call as a PracticePanther quota. Keep three ledgers if you use three systems. When the 150-call ledger is the one you actually run, count objects before you add a welcome packet, a questionnaire, and a calendar hold "for free."

Retry storms are how a quiet morning becomes a capped afternoon. If the PMS returns an error, wait, log, and retry with a limit. Infinite retry on a duplicate-name error will create 150 failed calls and zero matters. The exception queue exists so those leads still get a human.

US Tech Automations can count those writes against the 150-call daily cap and can stop the flow when the matter write, calendar write, and document write would exceed the remaining budget. Stopping is better than a partial matter with no source form.

Limitations

Without open vendor docs, this page will not claim Clio Grow versus Clio Manage differences. It will not claim PracticePanther intake forms exist at a named SKU. It will not invent seats, storage, or e-signature add-ons. Feature cells stay UNKNOWN.

Clio and PracticePanther are not "the same, so pick the cheaper one." Cheaper is UNKNOWN. Same is false: they are two PMS products with two unknown commercial envelopes. The join is the same shape on both: form, human conflict, contact, matter, source, no letter, notify, count, exception.

Do not use this page to replace legal matter intake automation if you have not picked a PMS. Do not use this page to skip Clio trust-account setup if the lead arrived with a retainer check. Do not use calendar-conflict automation as a substitute for Rule 1.7.

A native PMS form that already creates a contact and a matter after a human conflict flag is enough. Adding a second writer duplicates files. US Tech Automations is the wrong buy when the PMS already completes steps 3 through 5 with a stored source form and a blocked letter send.

Shared inboxes, spreadsheet trackers, and "we will open the matter tomorrow" are not a PMS. They are why this join exists. They are also why step 2 has to stay slow. Speed-to-matter without conflicts is not a KPI this page will celebrate.

What the source form must prove later

Malpractice carriers and opposing counsel both ask how the file opened. The source form is the answer. Store the original fields, the timestamp, the URL or campaign tag, and the name the human searched. If marketing later edits the live form, the stored copy on the matter must not change. A form that is only a live URL will drift.

Duplicate names are not always duplicates. Jane Smith in a family-law lead is not Jane Smith in a corporate-diligence lead until a human says so. The exception queue should show both records, both phone numbers, and both adverse parties. Merging contacts to "clean the database" before conflicts is how the wrong Jane gets a letter.

Assigned-attorney notification is not a marketing drip. If the attorney is out, the backup named on the freeze list gets the task. A notification that dies in a personal inbox is an unowned lead. Own the queue inside the PMS.

Engagement letters carry scope and fees. A template that auto-fills from a web form will get the practice area wrong the first week a lead ticks two boxes. Keep the letter in draft. A person sends it.

Legal review-request automation can sit after intake for document review. It is not an intake step. Law-firm billing automation can sit after the letter is signed. It is not an intake step. Calendar holds can sit after conflicts. They still count as API writes.

Pilot: 15 leads, one practice area

Pick one practice area. Family, immigration, PI, or corporate — one, not four. Take 15 real inbound leads or 15 composite test leads labeled as tests. Every lead gets a human conflict check. Success is a matter with a source-form link and no engagement letter in the sent folder. Kill the pilot if any letter auto-sends. Kill the pilot if any matter opens before the conflict flag. Keep trust accounting out of the 15.

Composite example: 15 employment-intake forms. Four are existing-client employees. Those four never become new matters; they escalate. Two are duplicate names with different emails. Those two sit in the exception queue. Nine are clear. Nine matters open with source forms stored. Zero letters send. The assigned attorney gets nine tasks. If your count is 15 matters, you skipped conflicts or skipped duplicates.

Do not use the pilot to migrate old matters. Do not use the pilot to sync a whole contact list. Do not use the pilot to test e-signature. Fifteen leads is enough to see whether step 2 still happens.

If the PMS native form already does this, the pilot is a reverify, not a rip-and-replace. Write down which event creates the matter. Write down where the source form lives. Write down what stops the letter. Then stop.

What the exception queue must contain

The exception queue is where this join stays honest. A Slack channel named "intake problems" is not a queue. Each exception row needs the form timestamp, the names the human must search, the assigned attorney on the freeze list, the reason code, and a link to the stored source form even when no matter exists yet. Reason codes are short: duplicate name, conflict hit, missing required field, trust-check arrived, letter-send blocked, API cap reached.

Conflict hits stay in the queue until a person records yes, no, or escalate. Duplicate names stay until a person merges, splits, or confirms they are two people. Missing required fields go back to the form, not into a matter with "TBD" in the adverse-party slot. Trust-check arrivals leave intake and go to the trust playbook. Letter-send blocked is a success state, not an error, if someone tried to auto-send. API cap reached means stop writing objects until the next day or until you cut the flow down to the three calls you actually need.

Do not let marketing "clear" the queue on Friday so the dashboard looks green. Clearing a conflict row without a search is the same failure as skipping step 2. The assigned attorney should be able to open the queue and see only their practice area, plus a conflicts officer view of everything.

Composite noise: 15 employment leads produced four existing-client employees, two duplicate-name rows, and nine clear matters. The queue still holds six rows until humans finish. If your dashboard says 15 matters and 0 exceptions, you skipped the queue. Rebuild it before you add a second practice area.

Call counting belongs on the same weekly review as the queue. Nine matters with three writes is 27 calls if nothing retried. Add a task and a note and you are at 45. Add one retry each and you are higher. The cap is 150 per flow per day. Publish the count next to the queue so nobody adds a welcome-packet write in the dark.

FAQs

Are Clio and PracticePanther interchangeable with Zapier?

No. They are practice-management systems. Zapier is an integration layer with a dated instant-trigger cap of 20,000 requests per 5 minutes per user. US Tech Automations is a separate orchestration layer with a dated 150-call daily cap. Do not shop them as one product.

What is the list price for Clio or PracticePanther?

UNKNOWN on this page as of September 1, 2026. Opened pages published 0 list-price dollars. Contact the vendor. Do not paste a roundup.

Can intake skip the conflict check if the form is short?

No. Model Rule 1.7 still applies. The join may assemble names. A human searches and decides. Automation that skips conflicts is a malpractice story, not a feature.

Why not auto-send the engagement letter?

Scope, rate, and conflicts are not form checkboxes. A letter that sends on matter-create will go to the wrong person, at the wrong rate, before the search is done. Kill the pilot if a letter auto-sends.

How do API calls add up on this join?

A Clio or PracticePanther write plus a calendar write plus a document write is 3 orchestration calls, not 1. Count retries. Stay under 150 calls per flow per day. PMS vendor quotas remain UNKNOWN until those docs open.

Does the 15-lead pilot include trust accounting?

No. Keep retainers and trust deposits on the trust-account playbook. An intake lead that arrives with a check is an exception, not a happy path.

Form-to-matter is a write with a human gate. Freeze the fields, keep conflicts in a person's hands, store the source, and count the calls. US Tech Automations can connect the submit trigger to contact and matter records after that gate, queue the source form, and skip the letter.