A consultant configures a Sales Accelerator sequence with steps that generate call tasks for reps across three time zones. After launch, several reps report that call tasks are due at 2 a.m. their local time because the sequence timing is calculated from a single reference schedule. What should the consultant configure so call tasks are generated within each rep's own working hours?
Select an answer to reveal the explanation.
Short Explanation
You need to teach Sales Accelerator each rep's working hours and time zone so due dates and times respect their schedule. A single reference clock is what's dropping call tasks at 2 a.m. for some reps.
Full Explanation
Configuring working hours and time zone per rep or team in Sales Accelerator settings is the right approach because Sales Accelerator can calculate due dates and times for sequence steps based on those settings, so each rep's call tasks land inside their own business day instead of a single reference schedule that ignores where they sit. Changing the sequence step type from Call to Task is incorrect because it removes the specific due time entirely rather than fixing it, and it also strips away the call-focused guidance the sequence was designed to give reps. Rebuilding the sequence separately for each time zone and manually assigning reps to the matching copy is incorrect because maintaining separate copies of the same sequence per time zone creates ongoing duplication and drift every time the sequence content changes, when a single sequence with per-rep working hours accomplishes the same goal without the maintenance burden. Increasing the wait time between sequence steps is incorrect because it shifts every rep's schedule uniformly rather than aligning tasks to each rep's actual working hours, and it would not reliably move a 2 a.m. task into that rep's business day.