professional-services-intake
Deposition scheduling calls: capture constraints without interpreting the notice
A practical intake workflow for court reporting firms that keeps scheduling useful without turning reception into legal review.
# Deposition scheduling calls: capture constraints without interpreting the notice
*October 2, 2026*
A deposition request can sound complete long before it is ready to schedule. A legal assistant may have a date and witness name but no duration. A videographer may call about a matter that is not yet in the reporting firm's system. A witness may ask to move an appointment without being the person authorized to change it. Reception has to make the call useful while leaving notice, authority, and case decisions with the people who own them.
That makes deposition intake different from ordinary appointment booking. The receptionist is not filling an open slot on a public calendar. The receptionist is assembling a scheduling request for review. The record should tell the coordinator what is wanted, when it is wanted, which services may be involved, and which details still need confirmation.
Start by identifying the request, not testing its validity
Ask what the caller needs the reporting firm to do. Common answers include holding a date, checking availability, changing a start time, adding remote attendance, requesting a videographer, or asking about transcript delivery. Record the answer in the caller's words when wording matters.
Do not decide whether a notice is sufficient or whether a caller has authority to alter a deposition. Those questions belong to the authorized scheduling coordinator and, where appropriate, the legal professionals handling the matter. Reception can say that it will forward the request for review and confirmation. It should not say that a deposition "has been moved" merely because someone asked for a different time.
The distinction should appear in the system status. "Requested" and "confirmed" are not synonyms. A request may also be incomplete, under review, declined, or awaiting documents. Clear labels prevent an internal note from becoming an accidental promise.
Build the scheduling record around the event
The fastest way to create confusion is to begin with a long free-form note. Use a small set of fields that follow the event itself:
- requesting firm and caller role;
- case reference used by the caller;
- witness name as provided;
- proposed date, start time, and stated timezone;
- expected duration;
- remote, in-person, or hybrid format;
- venue or remote-platform request;
- court reporter, videography, interpretation, exhibit, or other service requested;
- accessibility request, without collecting unrelated personal detail;
- delivery contact and secure callback information.
Unknown is a valid value. Guessing is not. If the caller does not know the duration, mark it unknown and let the coordinator resolve it. If the timezone is omitted, ask directly instead of assuming it from the caller's phone number or the firm's office address.
Read back names, dates, and times. A single wrong digit can send the coordinator down the wrong path, while a misspelled witness name may make an existing matter look new. The readback should be brief: "I have the requested start as 10:30 a.m. Eastern on October 14. Is that correct?"
Treat changes as new decisions
A reschedule call should preserve the original event details and record the requested change separately. Overwriting the old time removes useful history and makes it hard to determine what was actually confirmed.
Suppose an assistant calls at 4:45 p.m. and asks to move a next-morning remote deposition by two hours. The receptionist finds a matching matter but sees no permission rule that allows reception to edit it. A sound intake record includes the current event reference, the proposed new time and timezone, the caller's role, the reason stated by the caller, and the deadline for a response. The coordinator then decides whether to contact other parties, confirm resources, or request documentation.
The receptionist should close with process language: "I have recorded the requested change for the scheduling team. The event remains subject to their confirmation." That sentence is less satisfying than an instant yes, but it is accurate.
Separate service questions from legal questions
Callers often mix scheduling with questions the call team cannot answer. "Can the witness appear remotely?" may be a request for a remote platform, a question about a case agreement, or a legal question. Reception can clarify which service the caller wants from the reporting firm. It cannot decide whether remote appearance is permitted.
Use a boundary statement that still moves the call forward: "I can record the remote-service request and have the coordinator review it. I cannot determine whether remote appearance is authorized for the matter."
The same rule applies to subpoenas, notice periods, objections, and attendance requirements. The U.S. Courts Federal Rules of Civil Procedure resources are an authoritative reference for the firm's policy owner. They are not a live-call script, and a receptionist should not browse them to interpret a caller's situation.
Protect case information during the call
A case name is not automatic permission to disclose everything in the scheduling record. The firm's verification policy should state which details reception may confirm, which caller roles require additional verification, and when to route the call without confirming that a matter exists.
Keep ordinary notes free of passwords, access codes, private document links, payment card information, or identity documents. If the firm needs a notice, exhibit, or authorization, send the caller to the approved secure channel. Record that a document was requested or received, not its sensitive contents.
Remote meeting details deserve the same care. A platform link or passcode should follow the firm's approved distribution process. It should not be copied into a general callback note simply because a caller asks for it.
Design the handoff for the coordinator's next five minutes
A good record reduces the coordinator's first round of follow-up. Put unresolved items where they can be seen. If the duration is unknown, the venue conflicts with the remote request, or videography has not been confirmed, mark each point as open. Do not bury those facts at the end of a narrative.
Assign the request to a named role or monitored queue. Include a review deadline tied to the requested event, not a vague "urgent" flag. A request for tomorrow morning needs a different acknowledgment window from an inquiry about next quarter.
The receiving coordinator should accept, return, or reclassify the request. A sent email is not proof of acceptance. If the request remains unacknowledged, the workflow should expose that state and route it to the approved backup.
Test with calls that do not fit neatly
Training should include more than a perfect call from a known law firm. Use scenarios such as a witness asking to cancel, two callers proposing different times, a request that lacks a timezone, a same-day videography addition, an interpreter request, and a caller who refuses to provide a case reference.
Score the resulting record, not the receptionist's polish. Could the coordinator identify the event? Were the proposed date and timezone read back? Did the receptionist preserve the original booking? Were open questions visible? Did the closing statement describe the status honestly?
When several people make the same mistake, inspect the form before blaming the call team. A single "appointment time" field invites overwriting. Separate current, requested, and confirmed values make the intended behavior much easier.
What complete intake looks like
The call is complete when the request is understandable, the event can be matched or created without guesswork, unresolved details are marked, and an authorized coordinator owns the next decision. The caller should know whether the request was merely recorded or actually confirmed.
For a court reporting firm, that is the useful middle ground. Reception does not interpret the notice or decide who may change the event. It gives the scheduling team a clean, time-aware record so the people with authority can respond without reconstructing the call.
Need help mapping deposition requests, verification steps, and coordinator handoffs into a consistent phone workflow? Contact Virtual Assistant Call Center to discuss your intake process.