It should be triggered when anyone tries entering a customer into the showroom, adding one by phone, when a customer is assigned to another salesperson or editing customer info. We're a busy store so we have so many notifications that they get lost in the list. Everyone should receive a notification, at least the original and new salesperson entering the info should get a notification.

Thanks for raising this, Nick Petrasz — totally hear you on wanting stronger guardrails here and more visible skate-related alerts. To make sure we’re solving the right problem, could you clarify a couple things: in your workflow, which specific actions should trigger a block or warning when someone tries to enter a customer that’s already tied to another salesperson (e.g., creating a new lead/customer, editing an existing record, or attaching a customer to a deal)? Also, how are you defining a “skated deal” in your process, and what are the most common ways it happens today? And on the notification side, besides being removed from a deal, which skate events should generate this dedicated alert, and who should receive each one (original salesperson, new salesperson, managers, etc.)?

Thanks for raising this, Anthony Dizenzo — totally hear you on needing a stronger safeguard around duplicates. Just so we’re tracking the right problem: when you say “skate alert,” what exact scenario are you trying to catch (for example, the same customer getting entered twice, ownership getting bypassed, leads being reassigned, etc.)? And when duplicates happen today, what’s the biggest impact you’re seeing (two reps reaching out, credit/ownership issues, reporting getting messy, customer experience, something else)? Lastly, in your ideal flow, if we detect a potential duplicate, should the system just warn, block until a manager approves, or allow it through but require a reason/approval step?