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
A single sequence built around one reference clock will happily generate the same due times for everyone, no matter what time zone they're actually sitting in, which is exactly how a rep ends up with a call task due before sunrise. Changing the step type just removes the due time altogether rather than putting it somewhere sensible, so that trades one problem for another. Cloning the sequence per time zone works for a moment, but every future edit now has to be repeated across however many copies exist, which is a maintenance headache waiting to happen. Padding the wait time between steps shifts the whole schedule by the same amount for everybody, it doesn't account for the fact that different reps need different offsets. What actually solves this is teaching the system each rep's own working hours and time zone, so it calculates due times relative to their day, not a single shared one.
Full Explanation
The correct answer is B. Sales Accelerator can calculate due dates and times for sequence steps based on working hours and time zone settings defined per rep or team, so configuring those settings lets each rep's call tasks land inside their own business day instead of a single reference schedule that ignores where they sit. Option A is incorrect because changing the step type from Call to Task 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. Option C 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. Option D is incorrect because increasing wait time between steps shifts every rep's schedule uniformly rather than aligning tasks to each rep's actual working hours, it would not reliably move a 2 a.m. task into that rep's business day.