A consultant configures a new Sales Accelerator work queue for the outbound SDR team and assigns an active sequence to it. One SDR reports that the queue never appears in their Sales Accelerator workspace, while every other SDR on the team sees it normally. The sequence is active and the queue is active. What should the consultant check first?
Select an answer to reveal the explanation.
Short Explanation
A Sales Accelerator queue behaves like a private group chat. Belonging to the same department does not get you added automatically, someone has to invite you by name. If one rep on a team cannot see a queue that everyone else can, the first thing to check is whether that person was actually added as a member of the queue itself, separate from just being on the team. It is easy to get pulled toward flashier explanations: a missing add-on license, a mismatched clock setting, or some rule about which records get pulled into the sequence in the first place. But none of those control whether the queue shows up in someone's workspace at all, that is purely a membership question, and membership has to be granted person by person, not inherited from the team roster.
Full Explanation
The correct answer is C. A Sales Accelerator work queue only appears in a seller's workspace if that seller has been explicitly added as a queue member; simply belonging to the same team or business unit as other members is not enough. Since the sequence and queue are both confirmed active, the most direct explanation for one SDR being unable to see the queue while teammates can is that the membership assignment was never made for that individual. Option A is incorrect because Copilot for Sales licensing governs generative features like email drafting and summaries, not access to work queues, which are controlled through queue membership and security roles. Option B is incorrect because Dynamics 365 Sales does not hide or reveal queues based on a user's local time zone; time zone settings affect how dates and times display, not visibility of workspace objects. Option D is incorrect because enrollment trigger conditions determine which records get added into a sequence in the first place, not whether a seller can see a queue that already exists; a seller could have zero enrolled records and still see an empty queue as long as they are a member.