Script library: by scenario

    Trigger event cold call script

    For calls driven by a new role, funding, hiring, expansion or another public change, with an opener for each. Every line is ready to use: replace each {{placeholder}}, read it aloud a few times, then make it sound like you.

    Make your own version

    Quick answer

    How do you use trigger events in cold calling? A trigger event cold call names the specific event, such as a new role, a funding round, a hiring push or an expansion, explains in one sentence why that event usually creates the problem you solve, and asks whether that's happening for them. The trigger gives the call a reason today rather than any day.

    Who this script is for

    • SDRs who research accounts on LinkedIn, news and job boards before calling.
    • Teams using trigger alerts to prioritise call lists.
    • Anyone whose cold calls lack a specific reason to call this week.

    Triggers turn a cold call into a timely one. A new leader is reviewing what they've inherited; a funded company has money and a growth target; a company hiring ten salespeople needs them productive quickly. Each creates a predictable set of problems, and if your product solves one, the trigger is your reason to call.

    The script has one rule: the trigger must be real and recent, and the link between the trigger and the problem must be plausible. 'I saw you raised money, want to buy software?' is not a trigger call. 'Teams that raise a round usually double the sales team, and onboarding becomes the bottleneck' is.

    The full annotated script

    Six parts, in the order buyers expect them. The note under each part explains why it is written that way.

    1. 1. Opener

      Hi {{first_name}}, it's {{your_name}} from {{your_company}}. I saw {{trigger}}, congratulations.

      I'm calling because of that, actually. Have you got 30 seconds?

      Why it works: Congratulate genuinely, then admit the trigger is the reason for the call. It's honest and it's interesting.

    2. 2. Reason for the call

      When {{company_type}} go through {{trigger_type}}, {{predictable_problem}} usually becomes a problem within a few months.

      I wanted to see whether that's on your radar, or whether you're ahead of it.

      Why it works: Trigger, then predictable consequence. The 'or you're ahead of it' gives them a dignified way out.

    3. 3. Discovery questions

      What's the main focus for the next six months after {{trigger_type}}?

      How are you planning to handle {{predictable_problem}}?

      What's already in place, and what will need to change?

      Who's leading that?

      Why it works: After a trigger, plans are often being made right now. The last question finds the owner if it isn't your contact.

    4. 4. Value

      That's the stage where we usually come in. {{similar_company}} went through {{trigger_type}} last year, and the result was {{result}}.

      Why it works: A peer who went through the same trigger is the most relevant proof you can give.

    5. 5. The ask

      Would it be worth 20 minutes before your plans are locked in? I can do {{day_time_1}} or {{day_time_2}}.

      Why it works: Urgency comes from the trigger, not from pressure. 'Before your plans are locked in' is true and useful.

    6. 6. Close and confirm

      Great. I'll send an invite with a short note on what we saw at {{similar_company}}.

      Anyone else leading this I should include?

      Why it works: Trigger-driven projects often have a new owner. Include them.

    Two alternate openers

    Swap one of these in for the opener above when the situation fits.

    New role

    Hi {{first_name}}, {{your_name}} from {{your_company}}. Congratulations on the new role at {{prospect_company}}. Most people in the first 90 days are working out what to keep and what to change. I'm calling to see if {{topic}} is on that list.

    When to use it: Use within the first three months of a new leader starting. Wait at least two weeks so they've settled in.

    Hiring push

    Hi {{first_name}}, it's {{your_name}} at {{your_company}}. I noticed you've got {{role_count}} {{hiring_role}} roles advertised. When teams grow that fast, {{predictable_problem}} is usually what gives first. How are you planning for it?

    When to use it: Use when job ads show a team growing quickly.

    Gatekeeper line

    For when reception or an assistant answers. Be honest about who you are and ask for help.

    More gatekeeper scripts

    Hi, it's {{your_name}} from {{your_company}}. I'm calling about {{trigger}}, and I'm trying to reach whoever's leading {{topic}} as part of it. Is that {{first_name}}?

    Five likely objections and how to respond

    Acknowledge, ask one question, then offer a smaller step or let them go.

    All objection responses

    "How did you know about that?"

    It was {{trigger_source}}. I research the companies I call so I'm not wasting anyone's time. Is it something you're focused on?

    Why: Name the public source plainly. It shows preparation, not surveillance.

    "We've got it covered."

    Great, that's ahead of most. Out of interest, what's the plan? I'm always curious how teams handle it.

    Why: Curiosity sometimes reveals the plan isn't as complete as claimed.

    "It's too early to think about that."

    That's fair. When do you expect it to come up? I'll check in then, rather than bother you now.

    Why: Capture timing. Triggers create a window, and you've just learned when it opens.

    "Everyone's calling me since the announcement."

    I can imagine. I'll be quick and specific: {{predictable_problem}}. If it's not relevant, tell me and I'll go.

    Why: Acknowledge the noise and earn attention with specificity.

    "I'm still settling in."

    Of course. Would it help if I called back in a month, once you've had a chance to look around?

    Why: New leaders need time. A scheduled callback after 30 days often lands well.

    Trigger openers by event

    One opener for each common trigger. The reason and discovery sections above apply to all of them.

    Funding round

    Within four to eight weeks of an announced raise

    Hi {{first_name}}, {{your_name}} from {{your_company}}. Congratulations on the raise. Most teams use a round to grow {{function}} quickly, and {{predictable_problem}} is usually the first thing to slow it down. Is that part of the plan?

    Expansion or new site

    After a new site, region or market

    Hi {{first_name}}, it's {{your_name}} at {{your_company}}. I saw you've opened in {{new_location}}. When businesses add a site, {{predictable_problem}} tends to follow. How's it going so far?

    Acquisition or merger

    After a deal is announced

    Hi {{first_name}}, {{your_name}} from {{your_company}}. I saw the news about {{acquired_company}}. Bringing two teams together usually means deciding which {{system_or_process}} to keep. Has that come up yet?

    Voicemail

    Under 30 seconds. Skip voicemail on the first attempt and pair it with an email the same day.

    12 more voicemail scripts

    Hi {{first_name}}, it's {{your_name}} from {{your_company}}. I saw {{trigger}}, congratulations. When {{company_type}} go through that, {{predictable_problem}} usually comes up, and I wanted to ask how you're planning for it. I'll email you. My number is {{phone}}.

    Follow-up email

    Send it the same day as the call or voicemail. It identifies you and includes a working unsubscribe.

    Subject: After {{trigger_type}}

    Hi {{first_name}}, Congratulations on {{trigger}}. I tried you by phone. When {{company_type}} go through {{trigger_type}}, {{predictable_problem}} tends to come up within a few months. {{similar_company}} went through the same thing last year, and the result was {{result}}. If it's on your radar, would 20 minutes on {{day_time_1}} be useful before plans are locked in? {{your_name}} {{your_title}}, {{your_company}} {{phone}} Reply "unsubscribe" and I won't email again.

    Do and don't

    Do

    • Use triggers that are real, public and recent.
    • Link the trigger to a plausible problem in one sentence.
    • Name the public source if asked.
    • Use a peer who went through the same trigger as proof.

    Don't

    • Don't call a new leader in their first week.
    • Don't use private information or rumours as a trigger.
    • Don't overstate the link between trigger and problem.
    • Don't use the trigger as a gimmick and then pitch generically.

    What to expect

    Nousu has not published trigger-specific conversion figures. Compare trigger-led calls with your untriggered calls on the same list using the all-dials averages as a reference.

    Australian cold calling statistics
    MeasurePublished figure or what to track
    Dials that reach a live person14%
    Dials that become a conversation with a decision maker6%
    Decision-maker conversations that book a meeting22%
    Meetings per 100 dials1.3 meetings per 100 dials, against 0.3 for offshore teams

    These are Nousu's all-dials averages from 218,000+ dials into Australian businesses, November 2024 to April 2026. Nousu has not published a separate figure for this segment, so treat them as a reference point, not a target.

    To see how many dials your own meeting target needs, use the meetings per dial calculator.

    Common mistakes

    • Using stale triggers from six months ago.
    • Congratulating, then pitching with no link to the event.
    • Calling only the person in the news when someone else owns the problem.
    • Not logging the trigger in the CRM for the next caller.

    Compliance basics

    General information only, not legal advice.

    Australian cold calling laws
    • Australia: give your name, your employer, who you're calling for and the purpose at the start of the call, call only from 9am to 8pm on weekdays and 9am to 5pm on Saturdays (never Sundays or national public holidays) unless the person agreed to another time, and end the call and remove the number when asked.
    • Business-only numbers can't be on the Do Not Call Register, but personal mobiles can, so wash any list that may contain them. Follow-up emails need consent (inferred consent can apply in B2B when the message is relevant to the person's role), accurate sender details and a working unsubscribe actioned within 5 working days.
    • New Zealand and Singapore have their own rules for follow-up messages and, in Singapore, for marketing calls to numbers on the Do Not Call Registry. See the compliance summary on the script library page.

    Make a version for your company

    This script is a starting point. The free cold call script generator builds a version around your offer, buyer and market, with your own objection responses, voicemails and follow-up emails. It runs in your browser and nothing you type is stored or sent.

    FAQ

    Trigger event script questions

    Practical answers from the team that makes the calls.

    Still have questions?

    Book a 30-minute call

    A public change at a company, such as a new leader, funding, hiring, expansion or acquisition, that makes a particular problem more likely and gives you a timely reason to call.

    For funding and expansion, within four to eight weeks. For new leaders, after their first couple of weeks and within the first three months.

    LinkedIn job changes, company news, job boards and announcements. Our LinkedIn Sales Navigator playbook covers setting up alerts.

    Not if it's public and relevant. Name the source if asked, and connect it clearly to a problem you can help with.

    Don't use it. A weak link between trigger and problem is worse than no trigger, because it sounds like a gimmick.

    Yes. A trigger works with a referral, a peer pattern or a follow-up after email. The trigger gives timing; the rest of the script does the work.

    Want Australian callers to run this script for you?

    Book a 30-minute call. We'll map your market and buyers and show you what a phone-first campaign would book.

    Starting at $7,000 a month. Exact fee quoted after a 30-minute call.