A consultant configures a Sales Accelerator segment to route newly created leads from the West region into a follow-up sequence automatically. The segment is built from a saved list of leads that matched the region filter at the time the segment was created. Two weeks later, sales operations notices that leads created after the segment was set up never enter the sequence, even though they match the same region criteria. What is the most likely cause?

The most likely cause is that the segment was created as a static list snapshot rather than a live, query-based segment. Sales Accelerator segments can be built either as a static snapshot of records that matched a filter at one point in time or as a live, query-based segment that continuously re-evaluates which records qualify. A static segment behaves like a fixed list: once created, it does not pick up new leads that satisfy the same criteria afterward, which matches exactly what sales operations observed. The follow-up sequence being assigned to the work queue but never activated is not the cause, because an inactive sequence assignment would prevent any record, old or new, from entering the queue, whereas the scenario shows that the originally captured West region leads are working correctly. The idea that Sales Accelerator segments only refresh once a sequence reaches its final step for existing records is also incorrect, because segments do not wait for a sequence to finish before refreshing; refresh behavior depends entirely on whether the segment is static or live, not on sequence progress. The claim that West region leads were excluded because Sales Accelerator segments cannot reference a region or territory field is incorrect as well, because Sales Accelerator segments can absolutely filter on region or territory fields, which is exactly how the original West region list was produced. The consultant should rebuild the segment as a live, query-based segment so it continuously captures newly created leads that match the region criteria.