Resources / Consultation requests

Ask for a timezone before interpreting a time preference

Prevent staff from receiving an ambiguous callback or consultation window.

01

The operational decision

Prevent staff from receiving an ambiguous callback or consultation window. 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.

02

Prepare the workflow

Request the timezone as part of the approved scheduling preference and display it alongside the time in the handoff.

03

Example wording for approval

“Which timezone should the example team use for your preferred afternoon window? The request remains unconfirmed until the firm completes its scheduling process.”

04

Worked example

A fictional visitor requests 10:00 without specifying whether they mean the firm's timezone or their own. Ask the approved timezone question before interpreting the preference. Display the supplied zone beside the request in the staff summary. If the workflow converts it, retain enough context to verify the same instant. The acceptance case should cross a calendar-day boundary so an incorrect date becomes visible instead of remaining hidden in an apparently reasonable one-hour difference.

05

Handoff record

Record these task-specific fields: preferred window, timezone, date reference, request status.

06

Acceptance check

Use a caller in a different timezone from the office. Confirm the handoff preserves both the stated preference and its timezone without silent conversion errors.

Legal intake capacity calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot