All articles

After the call, who does what?

Jonathan Ferrell
After the call, who does what?

A customer says they can send photos tonight and asks whether someone can come out on Friday. The call ends. A summary appears in the inbox: “Customer requested a service visit.”

The summary is accurate enough, but it leaves the useful work unfinished. Someone needs to request the photos, check availability, and tell the customer what happens next.

This is a hypothetical service call, but it is a useful test for a call workflow. Can the person picking it up tell what was requested, what was promised, and what still needs a decision?

Make the next step visible

Ask an agent to prepare a short follow-up record alongside the transcript:

  • Customer request: a service visit on Friday, if available.
  • Commitment made: check the schedule and call back; no appointment confirmed.
  • Next action: request the photos and check the service calendar.
  • Owner: the person responsible for scheduling, once assigned.
  • Due: only a deadline that was actually agreed.
  • Evidence: the relevant words or timestamp from the call.

Keep requests separate from commitments. “Friday would work for me” is a preference. “You’re booked for Friday” is a confirmation. An agent that blurs those two can create work the business never agreed to do.

Missing information should remain visible. If nobody set a callback time, say so. If the caller’s address is unclear, flag it for confirmation. A neatly filled form is less useful than an honest one.

Put it where the work happens

The record belongs with the job, ticket, or customer account. A second document in a separate folder may leave the team searching in two places.

Tools can help extract the information. For example, Retell’s post-call extraction supports custom fields from a conversation. Those fields still need a destination and someone responsible for acting on them. Extracting a requested date does not book an appointment.

An agent might draft the follow-up message or prepare an internal task. Decide which actions it may take and which need someone to check them. A change to a quoted price or a promise about availability deserves a different review from a request for photos.

Test the handoff

Take a few recent calls and prepare the follow-up records before connecting any automatic sending or booking. Ask the person who handles the work to review them against the recordings or transcripts.

Look for missed promises, invented deadlines, and assignments made to the wrong person. Adjust the instructions around those errors, then try another set of calls.

Finally, check the outcome. Was the task assigned? Did the reply go out? Was the appointment confirmed? A generated action plan tells you what should happen. The customer is waiting for it to happen.