Paid Consultations With Clio Payments: From First Inquiry to a Booked Appointment

By Michael Brunman, Co-Founder and CEO of Clerx

The direct answer

A law firm using Clio can collect consultation fees through Clio Payments. With the appropriate setup, Clio Scheduler lets prospective clients choose an available appointment and pay during booking. Clerx can support the intake conversation before that step: responding to inquiries, collecting approved information, applying the firm’s screening rules, and helping the person reach the agreed booking process. Home

The roles should be clear. Clio Scheduler handles the configured booking experience, Clio Payments processes payment, and Clerx supports intake and the configured Clio handoff. Confirm the exact links, actions, and records in your implementation before relying on automated behavior.

Clio’s Scheduler documentation explains its booking-and-payment capabilities. The Clerx and Clio integration describes connected intake information and consultation scheduling. These capabilities should be demonstrated together using your firm’s actual appointment rules.

Why booking tools still need an intake process

An appointment link works well when the person already knows what to book. Many inquiries begin earlier.

A prospective client may ask whether the firm handles their issue, which attorney to meet, what the consultation includes, or whether an existing-client question requires another appointment. Someone contacting the office at night may need a clear explanation before choosing a time.

The work is to connect that conversation with the appropriate next step. A small immigration firm may offer a paid initial consultation alongside a separate route for existing clients. An estate practice may need staff review before booking a meeting arranged by an adult child.

The distinction between practice-management and intake software helps assign responsibilities. Scheduling records an appointment. Intake establishes which approved path the person should follow.

Define the consultation before configuring the workflow

Write down the appointment type, duration, attorney, format, price, and booking conditions. Decide when direct booking is appropriate and which requests need staff review.

For a fictional immigration practice, the policy might be a 30-minute paid video consultation for suitable new inquiries. Existing clients and callers requesting a fee exception would follow separate routes.

The intake-question design guide can help keep screening short. Ask questions that affect routing or preparation. Do not collect a complete case history merely to explain a fee.

Give the implementer one approved policy. If the appointment description says 30 minutes while the receptionist offers an hour, the tools are working from different instructions.

Explain the fee and meeting terms clearly

The prospective client should understand the consultation before reaching the payment screen.

Explain its duration, format, fee, and general purpose. Use the firm’s approved wording for cancellation, rescheduling, and any credit toward future work.

An illustrative explanation might be: “The initial consultation is a 30-minute video meeting with an attorney. The fee is $250. You can choose an available time and complete payment through our booking page.”

The price is fictional. The firm must supply its own terms and verify that the booking page presents them consistently.

If someone asks whether payment means the firm has accepted their case, use the attorney-approved response. The intake process should distinguish an initial consultation from an agreement for further representation.

Screen before offering the booking route

Collect the minimum information needed to identify the correct next step: contact details, broad inquiry, location where relevant, and whether the person is already a client.

A consultation fee does not remove the need for screening. A caller may have an issue outside the firm’s practice, need an unavailable service, or require review before scheduling.

Use the new-lead and existing-client routing framework to separate those paths early. The intake and conflict-review guide helps define where attorney review belongs.

Include an explicit outcome for uncertain cases: receive the request, explain that the team will review it, and assign an owner. The receptionist should not resolve uncertainty by making an unsupported promise.

Connect the inquiry to Clio’s booking experience

For a firm using Clio Scheduler, confirm the approved booking link and which appointment types it presents. Decide whether each intake branch leads to a particular appointment or to a staff-review step.

Test the entire route from the initial conversation. Does the person reach the intended appointment type? Do the displayed fee, duration, and meeting format match the explanation? Is the time zone clear?

Clio documents that appointments can appear in the Clio Manage calendar according to the configured sharing settings between Grow and Manage. Check those settings with the person responsible for the firm’s calendar. Home

This article concerns Clio Scheduler. Clerx Scheduler is a separate product, and its published MyCase workflow should not be treated as evidence of an identical Clio implementation.

Keep payment inside the approved Clio Payments process

Clio Payments is Clio’s integrated payment solution. Its getting-started guidance explains activation and account setup. Confirm that the firm’s payment configuration is ready before offering paid appointments. Clio's Help Center

The firm should approve the fee and payment destination. Staff should know where to verify the transaction and how to handle an incomplete or disputed payment.

Where the firm needs a separate request, Clio also documents payment requests from Clio Grow. That workflow has its own account requirements. A separate request and payment during Scheduler booking are different routes; choose the one that fits the appointment. Clio's Help Center

Do not describe Clerx as natively processing Clio Payments or automatically confirming transactions unless those actions have been verified in the firm’s configuration. A published payment API establishes an available development route, not proof that a particular vendor has implemented it.

Preserve the intake record in the appropriate Clio destination

The attorney should receive enough context to prepare without reconstructing the conversation.

A useful record includes who contacted the firm, the broad inquiry, screening information, requested appointment, communication preference, and any unresolved question. Keep payment verification in the approved financial workflow.

Clio’s official Clerx listing describes communication entries and caller information in Clio Manage, alongside a prospect handoff into the Clio Grow Inbox. Confirm which product the firm uses and what information will be retained. Clio

Check a repeat inquiry as well as a new one. A person returning with a booking question should not automatically become another new prospect. Shared family numbers also need a review policy so one person’s inquiry is not attached to another person’s record.

Make phone, chat, and text agree

A person may ask about a consultation by phone, open the booking page later, and return by text with a question.

The fee, appointment description, and next step should remain consistent across those interactions. Review the wording in Clerx AI Receptionist, website chat, and text messaging for the channels included in your implementation.

Where the configured intake service directs people to a booking link, verify that the correct link is used. Do not assume every channel updates automatically when a calendar setting changes.

Review each working language too. A correct amount can still be misunderstood if the explanation is unclear about the meeting’s purpose or whether payment is required.

Give incomplete bookings an owner

Not everyone finishes the journey in one sitting. A person may close the page, encounter a payment problem, or need help choosing an appointment.

Decide how staff will identify incomplete work and what follow-up is appropriate. Define what the team can actually observe; do not assume an abandoned page creates an automatic alert.

The guide to preventing intake handoff leakage explains the ownership problem. For this workflow, someone should know what to do when the person has contacted the firm but has not reached a confirmed appointment.

Keep messages accurate. Sending a link is different from completing a booking. A caller saying they paid is different from a verified transaction. Staff should check the relevant records before asking for another payment or promising an appointment.

Test the ordinary journey and the exceptions

Use fictional examples before launch: a suitable new prospect, an existing client, someone requesting a fee exception, a returning caller, and a person who cannot complete payment.

Inspect the conversation, booking page, calendar, payment record, and staff handoff. A successful conversation does not establish that every connected step succeeded.

The receptionist go-live testing guide provides a structure for documenting expected and observed results.

Measure the work remaining for staff: clarification calls, booking corrections, payment checks, and unresolved inquiries. A connected workflow is useful when it produces a clear next step and a dependable record. Any claim about time saved or improved conversion should come from observed results.

Frequently asked questions

Does a Clio firm need LawPay for this workflow?

No. The workflow described here uses Clio Payments. Clio’s own scheduling tools support paid appointments when the required payment and account settings are enabled.

Can Clio Scheduler collect consultation fees?

Yes. Clio documents payment during appointment booking when Clio Payments is enabled and the applicable requirements are met. Confirm the setup for your account and appointment type.

What does Clerx add when Clio already has scheduling?

Clerx supports the conversation before booking: responding to inquiries, gathering approved information, applying routing rules, and preserving context through its configured Clio integration. The demonstration should show the exact handoff.

Does Clerx automatically generate Clio Payments links?

Do not assume that from general integration materials. Confirm whether the proposed implementation uses an existing approved link, generates a link, or requires staff action. These are different capabilities.

Can the receptionist confirm payment?

Only if the configured workflow can verify the relevant status. Otherwise, route the question to staff and use Clio’s payment record as the verification source.

What if an inquiry needs review before booking?

Collect the approved information and assign the request to the responsible staff member. Explain the review step clearly without offering an appointment the firm has not authorized.

Should every inquiry create a matter?

The firm should approve its record policy. A new inquiry, booked consultation, and accepted engagement are different stages. Confirm how the integration handles each.

What should the demonstration prove?

That a suitable prospect receives accurate consultation information, reaches the correct booking route, completes the required steps, and leaves useful context for staff. Include an incomplete-payment scenario and a repeat inquiry.

Book a demo with Clerx today.