A sales operations lead manages Sales Accelerator for a 40-person team selling into three regions. Leads from the APAC region need a different outreach cadence than leads from EMEA because time-zone constraints change when calls and emails should happen. Reps currently work all leads through one shared sequence, causing APAC leads to receive calls scheduled at 2 a.m. local time. Which configuration change addresses this?

Creating separate segments with region-specific sequences assigned so APAC and EMEA leads follow different cadences is correct because it lets APAC and EMEA leads receive calls and emails scheduled at times that respect each region's business hours, which is exactly the constraint causing 2 a.m. contact attempts. Segmentation is the mechanism Sales Accelerator provides for tailoring cadence to a defined subset of leads rather than forcing every lead through one shared sequence. Increasing the lead score threshold so only higher-scoring leads enter the sequence, reducing overall queue volume, is incorrect because raising the score threshold changes which leads enter the queue, not when scheduled activities occur within it, so APAC leads that still qualify would keep receiving overnight contact attempts. Reassigning all APAC leads manually to a single top-performing rep who works from an APAC time zone is incorrect because manually reassigning every APAC lead to one rep does not scale past a handful of accounts and ties a structural scheduling problem to a single person's availability rather than fixing the underlying sequence configuration. Turning off AI-generated next-best-action for the sequence so reps schedule contact times manually for every lead is incorrect because turning off next-best-action removes AI-driven prioritization guidance entirely, forcing reps to schedule every contact manually, which sacrifices the efficiency benefit of Sales Accelerator without directly solving the timezone mismatch that caused the complaint in the first place.