Cutting the Salesforce Ticket Queue with Clay Templates
2025Objective
Routine Salesforce updates went through a ticket process, with resolution time running up to 48 hours before an admin could act. Once picked up, the actual work, split across the BDR, RevOps, and the Salesforce admin, took an average of 1.5 hours. The goal was to remove both the queue delay and the inefficient handoff between teams.
About the build
Built a set of easy-to-use Clay templates covering the most common Salesforce operations. Each template was validated before being made available to the team, and all updates are logged automatically. Team members now run operations directly from Clay — no Salesforce access required, no ticket needed.
Operations enabled:
- Lead source changes on opportunities
- Campaign member inclusions and exclusions
- Record ownership changes (redistributing lead/account lists across BDRs)
Before and after
Key outcomes
Attribution and visibility
Because the three trained users each hold their own Salesforce login, an ownership change on a record traces directly back to who made it. Previously, updates went through a shared SF admin account, so tracing a change meant going back through ticket history to find who requested it. Not a time saving in itself, but it adds accountability and makes debugging record changes far faster.