The operational decision
Make a submitted preference distinguishable from a booked meeting. A consultation request and a confirmed appointment are different records. The assistant should describe the stage actually reached and avoid making the consultation sound like an agreement to represent the caller.
Prepare the workflow
Use a visible requested status until staff or a tested calendar action confirms an appointment; keep the confirmation source in the record.
Example wording for approval
“Your example consultation request is awaiting review. The preferred time is not reserved, and this request does not confirm that the firm will represent you.”
Worked example
A fictional visitor selects Tuesday afternoon on a preference form that has no live calendar connection. The confirmation should say request received for review, not Tuesday appointment confirmed. The staff queue needs the preferred window and an unconfirmed status. Test a later page refresh and any acknowledgment email too, because one channel may still use old booking language. A consistent request state prevents the visitor from treating a chosen preference as a reserved meeting or an accepted legal matter.
Handoff record
Record these task-specific fields: request identifier, preferred time, confirmation source, status.
Acceptance check
Submit a fictional request and inspect the confirmation screen. It should not display Appointment booked or an equivalent unverified commitment.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗