SCRIPT MODE: - COLD OUTREACH SCRIPT TYPE: - cold email SCRIPT LENGTH: - Short PRIMARY MESSAGE OBJECTIVE: - get a reply PRIMARY SALES CHALLENGE: - weak buyer relevance SECONDARY CHALLENGE: - trust or proof gap ASSUMPTIONS: - The buyer is likely responsible for support efficiency or team performance. - The offer helps reduce repetitive manual support work. BUYER ANGLE: - what matters most to this buyer: response efficiency, team capacity, support quality - what pain, goal, or outcome should be emphasized: reducing repetitive support workload without making support quality worse - what should be avoided in tone or framing: hype, AI buzzwords, and big claims without proof CORE MESSAGE: - The offer helps support teams reduce repetitive manual work so they can respond faster and focus on higher-value cases. SHORT HOOK: - You may be spending team time on support work that should not stay manual. SALES SCRIPT: - opening: Hi [Name], quick note because you lead support at [Company]. - relevance line: A lot of support teams hit the same bottleneck: too much agent time goes into repetitive tickets, but most automation options create more friction than they remove. - value line: We help teams simplify that layer so common requests are handled more cleanly and agents can focus on the cases that actually need judgment. - differentiation line: The angle is operational clarity first, not flashy automation for its own sake. - objection softener: Not saying this is a fit yet, but it seemed relevant if response load or repeat-ticket volume is becoming expensive. - call to action: Worth a quick reply if this is even mildly on your radar? ALTERNATIVE VERSION: - Hi [Name], reaching out because support teams often end up hiring around repeatable ticket volume instead of fixing the workflow behind it. We work on that part specifically, so agents spend less time on routine cases and more time where judgment matters. Not assuming timing is right, but open to a quick exchange if this is a live issue for you? LIKELY OBJECTIONS: 1. We already have something in place. 2. This is not a priority right now. 3. I do not have enough reason to look at this yet. OBJECTION RESPONSES: 1. That is fair. The question is usually not whether something exists, but whether it is actually reducing repetitive workload in a meaningful way. 2. Understood. This tends to matter only when ticket volume, response time, or team load starts creating operational drag. 3. Fair point. The message is mainly to test relevance, not push a full evaluation too early. WHAT NOT TO SAY: - This will transform your support team overnight. - We help companies 10x support performance. - Just checking in on this. - Can I grab 30 minutes tomorrow? MOST IMPORTANT FIX: - Make the message more obviously tied to support workload and less centered on the seller. NEXT ACTION: - Personalize the relevance line with one real support signal from the buyer’s company before sending. FINAL IMPROVEMENT NOTE: - This script is stronger because it lowers pressure and earns relevance before asking for time. - Better input on the exact offer and support problem would improve specificity. CERTAINTY: - MEDIUM