MyCase Consultation Rescheduling: Change the Appointment Without Losing the Intake

By Michael Brunman, Co-Founder & CEO of Clerx, Former Litigator

The direct answer

MyCase consultation rescheduling is the process of changing an existing consultation while keeping the appointment, intake context, notifications, and any fee policy consistent. It is different from booking a new consultation. A receptionist must identify the original appointment and use only the change actions the firm has authorized and verified.

The Clerx and MyCase integration supports intake and consultation workflows. MyCase’s official integration documentation describes contacts, notes, calendar bookings, and optional LawPay collection. It does not independently establish that an AI receptionist can edit or cancel every existing appointment. Demonstrate those actions before enabling them.

A small firm can still operate a good change process when staff must approve the final calendar edit. The important point is to describe the request accurately and assign the work.

Identify the appointment before offering another time

Ask for the caller’s name and the appointment they want changed. Confirm the relevant date, attorney, and appointment type through the approved verification process. A phone-number match can be useful context but should not be the only identity decision.

Do not disclose another person’s appointment while trying to locate the right record. Shared family numbers and assistants calling for someone else require a defined route to staff.

The caller-routing guide helps separate a returning prospect from a new inquiry. A rescheduling caller should not have to complete initial screening again merely because they have not yet become a client.

If the appointment cannot be located, capture a change request with the caller’s reported details. Avoid inventing a calendar confirmation to keep the conversation moving.

Distinguish a request from a completed change

The firm should use plain status language. “I have sent your request to the team” and “your appointment has moved to Thursday” describe different outcomes.

Direct changes require verified access to the original event, permission to modify it, a valid replacement slot, and a reliable result. A workflow that only creates new events cannot safely be described as a rescheduling tool.

The intake and practice-management guide explains why software roles matter. Receiving the conversation, changing a calendar record, and communicating the result are separate responsibilities.

Where the system cannot complete the edit, collect acceptable alternatives and tell the caller what happens next. The original appointment should follow the firm’s policy until staff resolve the request.

Protect the original booking context

A new time should not erase why the person booked, what screening was completed, or what staff still need to review. Keep the change request attached to the existing inquiry through the supported process.

The attorney should be able to see the original consultation type, reported matter, changed date, and unresolved questions. If the caller adds a new issue, label it as additional information rather than silently replacing the original reason.

Use the intake question framework to keep the conversation short. Ask what is needed to identify the booking and implement the requested change. Repeating a long questionnaire adds friction without proving that the appointment was updated correctly.

Apply the approved fee policy

A caller may have paid for the original consultation. Changing the time does not automatically establish a refund, new charge, credit, or forfeiture.

The firm should supply the policy for changes inside and outside its notice window, attorney changes, appointment-type changes, and exceptions requiring review. The receptionist should explain approved terms and route uncertain financial questions to staff.

Clerx’s LawPay integration is relevant where the MyCase firm uses that supported payment route. It does not establish that appointment changes automatically trigger refunds or move funds between transactions.

Treat payment verification as a separate check. A caller’s report that payment was made is useful information, but staff should use the approved transaction record before asking them to pay again.

Verify the exact calendar operations

Ask the implementer to demonstrate what happens to the old event, new event, participants, meeting link, reminders, and staff notifications. Verify whether the original slot becomes available again and when.

The scheduling and payments overview provides product context. Your acceptance test should use the actual calendar and account settings rather than an unrelated demonstration calendar.

Include concurrent activity: someone on staff changes the event while the caller is speaking. Determine how the workflow avoids overwriting a newer decision. If the proposed system cannot detect that conflict, staff approval may be the appropriate operating route.

Record which changes can be completed during the interaction and which produce a request. That distinction should appear in the caller-facing wording.

Make every confirmation agree

A correct calendar change can still confuse someone if the old reminder remains active. Review phone wording, text, email, booking pages, and staff instructions together.

Clerx text messaging can support configured communications, but do not assume it cancels every reminder sent by another system. Identify who owns each message and how it learns that the appointment moved.

The consultation reminder guide covers attendance communication. For rescheduling, the narrower requirement is that the person can identify the current appointment and discard the obsolete details.

Include a time-zone check when the caller is traveling or the attorney offers remote consultations. State the date and zone explicitly rather than relying on “same time tomorrow.”

A worked immigration-firm example

Consider a fictional Massachusetts immigration firm already using MyCase. A prospective client paid for a video consultation and now needs to move it because a work shift changed. The caller asks for the same attorney but a later day.

The initial conversation should identify the existing consultation and request. If verified edit access is available, the workflow should offer appropriate slots and confirm the completed change only after the result is known. If only booking creation is supported, it should send a clear rescheduling request to staff.

The team should receive the original date, preferred alternatives, payment-related question, and contact preference. It should not receive a second sales lead with a fresh payment request and no reference to the first booking.

Now suppose the caller wants a different consultation type as well as a new time. Staff may need to review the fee and duration before changing anything. That is a different branch from moving the same appointment.

MyCase is the firm’s existing platform in this example. Immigration practices may instead use 8am DocketWise, MyCase, or both. The platform choice should not be assumed from practice area.

Test failure without leaving two appointments

Use a fictional appointment and test an unavailable slot, unknown caller, interrupted calendar write, repeated request, and cancellation after a change. Inspect the resulting records.

The go-live testing guide supports this acceptance process. Verify that the same request cannot accidentally create several active appointments when retried.

Do not resolve uncertainty by deleting records without review. Staff should establish what actually happened and preserve the change history. A manual queue can be sufficient if it has an owner and the caller receives accurate expectations.

Measure completed changes and repair work

Count change requests, completed changes, unresolved requests, duplicate events, contradictory confirmations, and staff time needed to repair the process. Compare the same definitions before and after implementation.

The weekly intake quality guide can support sampling, but deliberately include changed appointments. A random sample dominated by new bookings may miss the relevant failure.

The goal is a dependable appointment history with less repeated work. Any improvement in attendance or conversion should be measured separately, rather than attributed to rescheduling automation without evidence.

Write the change request staff actually need

A rescheduling request should state the current appointment, requested alternatives, whether the caller can keep the original time if necessary, and any question about fees or meeting format. Avoid vague notes such as “please call about appointment” when the conversation already established those details.

Keep reported information distinct from verified calendar data. If the caller thinks the meeting is Tuesday but staff cannot locate it, preserve that uncertainty. A record that guesses the original date can lead the next person to edit an unrelated appointment.

The request should name the next owner and the contact route the caller agreed to use. If the firm can only confirm changes during staffed hours, explain that accurately. Do not use a generic confirmation message merely because it is the easiest available template.

Review changes that alter the service

Moving the same consultation to another day differs from switching attorneys, changing from video to in-person, or requesting a longer meeting. Those changes may affect preparation, price, location, or availability.

Build a short exception list with the firm. For each exception, decide whether direct change is allowed or whether staff review is required. The receptionist can remain helpful by collecting the request and alternatives without promising a result it cannot verify.

Test a caller who makes two requests in one conversation: a new time and a different service. Inspect whether the final record preserves both. If the system changes the time but overlooks the service question, the calendar may look complete while the real request remains unfinished.

After staff resolve the exception, confirm the current appointment details through the approved channel. Keep the original request and the resolution linked through the supported record process so the attorney can understand why the booking changed.

Keep a short appointment-change log

During the pilot, retain the original appointment reference, requested change, observed result, and person who approved any exception. The log can point to the existing records rather than duplicate the full inquiry.

Review requests that were resolved outside the usual process. If the attorney agrees to a change directly, the intake team still needs the current appointment status so it does not follow up on an obsolete request.

This is especially useful when two people share administrative work. One person may speak to the caller while another controls the calendar. A small record of the decision prevents them from making inconsistent edits.

Use the log to identify recurring uncertainty, such as unclear fee rules or appointment types that callers often confuse. Those findings can improve the policy without assuming that every problem requires another automation feature.

Frequently asked questions

Can Clerx reschedule MyCase consultations automatically?

Verify the edit and cancellation actions in your configuration. Published booking support alone does not prove that every existing appointment can be modified.

Should a reschedule create a new lead?

Usually the change should remain associated with the existing inquiry. The firm should approve the record policy and test returning callers.

What happens to the original appointment?

Follow the approved calendar process. Do not promise that it was removed until the edit or cancellation is confirmed.

Does changing a time refund a consultation fee?

That depends on the firm’s policy and payment workflow. An appointment change does not by itself establish a refund or credit.

What if someone calls for a family member?

Use the approved identity and authorization checks. Avoid disclosing appointment information based only on possession of a shared phone.

Can staff approve changes manually?

Yes. A clear request, responsible owner, and accurate caller expectation can be preferable when direct editing is not verified.

Should old reminders stop?

Review every reminder source. Confirm that obsolete messages are suppressed or corrected through the relevant system’s supported process.

What should the demonstration prove?

One completed change, one request needing review, an accurate payment explanation, consistent confirmations, and no unintended duplicate appointment.

Book a demo with Clerx today.

About the author

Michael Brunman is Co-Founder & CEO of Clerx, helping law firms improve client intake and communication. A former litigator, software engineer, and McKinsey consultant with an MBA from Harvard Business School, he brings legal, technical, and business experience to the challenges of running a law firm.