How to Write a Phone Brief for an AI Assistant

Quick answer

A phone brief should give the assistant the objective, verified contact, essential facts, permitted questions, authority limits, and what to do if the call cannot reach its goal. Put critical instructions in the brief itself instead of assuming the assistant will infer them from a long conversation history.

Phone calls unfold quickly. A clear brief reduces avoidable clarification while preserving the owner's control over commitments.

Define one primary goal

Choose the result you want: confirm an appointment, ask a vendor a specific question, collect available times, or request a callback. If several goals depend on each other, state the order and stop point.

Provide the verified organization and number. Include the department or person if relevant. Do not ask an assistant to try guessed contact details after a failed call unless you authorize a separate lookup and verify the result.

Explain how the assistant should introduce itself and whom it represents. The introduction should be truthful and appropriate to the task. Include any information the contact needs to locate the appointment or record, limited to what is necessary.

Put essential facts beside the questions

List the exact details needed for the call: appointment date, reference number, requested service, preferred windows, and the question you need answered. Mark facts that are unknown so the assistant asks rather than invents.

Keep a distinction between background and instructions. Background explains the context; instructions tell the assistant what it may say or decide. A story about why you prefer Friday does not automatically authorize accepting any Friday price or time.

If the call involves a sensitive or expert issue, keep the assistant's role to logistics or information collection and route interpretation to the appropriate person.

An illustrative equipment-service call

A studio owner wants to confirm whether an equipment-service appointment can be moved from Tuesday to Thursday. The owner supplies the appointment reference, preferred windows, and a rule that any added fee needs approval.

The assistant can ask about Thursday availability and collect the fee information. If the provider offers Friday instead, that is outside the brief. The assistant should report the alternative rather than choose it simply to finish the call.

If the provider cannot find the appointment, the assistant should verify the supplied details and request the approved callback path. It should not disclose unrelated private information in an attempt to make the lookup succeed.

A phone brief template

Goal: Ask the verified service provider whether appointment reference ABC-123 can move from the specified Tuesday date to Thursday afternoon. Introduce yourself truthfully as my assistant. Use the supplied name and contact details only as needed to locate the booking. Ask for available times and any change fee. Do not accept a fee, cancel the existing appointment, or choose another date without approval. If no Thursday slot exists, collect alternatives. Report the exact result, quoted terms, and next decision.

This is an illustrative prompt with a fictional reference. Replace every placeholder with verified details and confirm your assistant supports the intended call workflow.

Plan for ordinary call obstacles

Say what to do with voicemail, hold time, transfers, unclear answers, and an unavailable decision-maker. For voicemail, supply approved wording and the callback details. For a failed connection, choose whether to retry once or report immediately.

Do not give unlimited retry authority. A clear maximum prevents repeated calls that add pressure without advancing the task. If the provider asks to be contacted later, preserve the agreed timing.

If the assistant cannot establish whether an action succeeded, report uncertainty. A dropped call after an apparent agreement may require verification before any repeat request, especially when a duplicate booking could result.

Ask for a result you can inspect

The report should include whom the assistant reached, the relevant answer, any appointment or confirmation details, terms stated by the provider, and the next action. Separate a proposed option from a confirmed change.

Keep the original appointment active until the authorized change is verified. A conversation about availability does not necessarily mean the booking was modified.

For recurring call tasks, save the brief structure while updating dates, contacts, and scope. Reuse the process rather than old factual details.

FAQ

How long should a phone brief be?

Include the essential facts and decisions in a concise brief. Link supporting background only if the assistant can reliably use it for the call.

Can I authorize the assistant to negotiate?

Only with explicit limits and a supported workflow. Define acceptable choices, amounts, and when a human decision is required.

How can I try this with Righthand?

Explore voice AI, appointment booking, and task delegation, then confirm the call action and review boundary for a single task.