Playbook: Voice sales executive

A salesperson is driving and can't type an order or a visit report

The problem

The best moment to record what happened at a customer is the minute after leaving. That is exactly the moment the salesperson is in a car with both hands on the wheel. By the evening, half the detail is gone.

What you end up with

An agent they talk to. They say what happened; it asks the one or two questions it needs, writes the visit up properly, and — if they dictated an order — creates it and reads back the total for confirmation before saving.

What it needs

• Access level: Power User or above to create the agent.
• Instance: connected, for customers, prices and orders.
• Speech: microphone access in the browser. See Speech Setup.
• Phone number: optional — an agent can also answer on a real phone line, see Phone Numbers.

Build it step by step

1. Open the Agent Builder:

   Create an agent called "Sales Voice". It is used hands-free by salespeople after a customer visit. It should accept a spoken summary, identify the customer, write a clean visit report, and store it.

2. Add the order path:

   If the salesperson dictates an order, find the products they name, use that customer's prices, then read back the products, quantities and total and wait for a spoken confirmation before creating the order.

3. Tune it for speaking rather than reading:

   Keep every answer under three sentences. Never read out long lists — ask a narrowing question instead. Always confirm names and quantities you were unsure about.

4. Set the reasoning level to a fast one so the conversation doesn't lag.

5. Share it with the sales team and tell them to tap the microphone in chat, or dial the agent's number if you assigned one.

Try it

Speak a realistic sentence with a mumble in it: "visited Petrov today, they want twenty of the six-millimetre and maybe some of the eight." A good agent asks which eight-millimetre item and how many — it doesn't invent an answer.

Variations

• Phone line — give it a number and let people call it, including from a car's handsfree.
• Report only — no ordering, just a well-written visit report filed against the customer.
• Daily debrief — combine with a schedule so it phones or messages at 18:00 asking how the day went.
• Multilingual — it can work in whichever language the salesperson speaks.

Where it can go wrong

• Product names in speech. Codes and dimensions are misheard constantly. Tell the agent to always confirm the product it matched.
• Silent order creation. Never let it create a document without a spoken confirmation.
• Long answers. A voice agent that reads a table out loud is unusable. Cap the answer length in the instructions.
• Noise. In a moving car, expect retries. Short exchanges survive; long ones don't.