Read the three columns
A call step completes when you attempt a call on or after it’s due. A text step needs a text. Calling early, repeatedly dialing the same day, or calling when a text is due doesn’t automatically complete more steps. Failed or disconnected-number attempts don’t complete a step.
Promise a callback
Click Next follow-up on the row or in the lead panel. Choose a preset, or Pick date… for a day and optional time. Check the displayed date before saving. Watch: set a callback · 25 seconds Using example data: open Next follow-up, choose Pick date…, select a day, and click Set. Check the saved promise before moving on. Dates and times use the workspace’s calendar and time zone. They aren’t automatically converted to each driver’s location. If a driver asks for “3 PM my time,” confirm their time zone and choose the corresponding workspace time. Presets such as 2 days count working days. A promise appears in Today on its due day. Overdue turns red after that day has passed; it isn’t a minute-by-minute lateness alarm. A qualifying call attempt or sent text at or after the promised time can clear the promise. The call doesn’t have to be answered. An earlier attempt can leave it standing. Check Next follow-up afterward, especially if you sent a text but still owe the driver a call.Follow the plan
A list usually carries its own copy of the team’s workflow. If an Owner or Admin handed it out with Workflow starts: Not yet, it has no steps until they apply the workflow; until then only replies and promised callbacks reach Today. A plan might say call, wait two working days, call again, then text. Your list’s steps are the ones to follow, even if a different list has another sequence. Waits start from the preceding completed step. If you do a step late, later steps move later too; Vocal doesn’t silently skip them. A late plan step doesn’t turn red like a missed promise. Some plans use waits in hours instead of working days. An hour-based wait is elapsed time and can reach a weekend or day off. Read the due date and time before contacting the driver. An Owner or Admin edits the team’s Workflow and can apply changes to selected existing lists. Don’t assume a workflow edit has changed every list you already hold.What the labels mean
Why did the plan stop?
A connected conversation, or responding to a waiting reply, stops the plan. It doesn’t resume by itself a few days later. You can set a promise or choose Restart plan when another sequence is appropriate. A stopping status, Stop following up, a dead number, do-not-call, or text opt-out can also stop work. A team’s status names and stopping rules can differ. See Access and stopping contact.Skip, restart, or stop
- Skip this step moves to the next step and counts its wait from now. It doesn’t place a call or send a text.
- Restart plan begins again at the first step. It resets progress for this run; earlier activity remains in history.
- Stop following up removes the next planned action without deleting the lead or its history.
- Resume following up, when available, isn’t the same as restarting at step one. Check the next action it shows.