Sales acceptance rate

Lead counts flatter events; acceptance rates audit them. Marketing can report four hundred scans, but if sales accepts forty and quietly deletes the rest, the event produced forty leads and a reporting problem. Tracking acceptance formally — each handed-off lead marked accepted or rejected, with a reason — turns the post-show argument between sales and marketing into data: rejection reasons cluster, and the clusters tell you what to fix (wrong audience means reconsider the show; "no context" means fix capture notes; "not a buyer" means fix qualification at the stand). Commercially, the metric protects both sides — sales stops being blamed for ignoring lists it was right to ignore, and marketing learns which shows produce leads worth defending budget for. The common mistake is not defining acceptance at all, so leads drift into a CRM limbo that's neither worked nor rejected and the funnel's biggest leak stays invisible. One honest nuance: a very high acceptance rate isn't automatically good — it can mean sales rubber-stamps everything to avoid the argument, or that the bar was set so low the metric stopped meaning anything. Pair it with what happens next: accepted leads that never get a first call are rejections wearing a polite label.