A trigger-based opener earns attention by giving you a reason this account belongs on today's call list. Name an event, connect it to the work it may have created, and ask a question the prospect can use to confirm or reject your assumption. Timing gives the format its force: a relevant time-based trigger can create urgency at any point in the year.1 Keep the event close to the person's work with a role-specific trigger such as a recent hire, funding announcement, seasonal demand spike or regulatory change.2 A trigger-event opener can also use funding, a new hire, a product launch or a promotion.3
Build the opener in order
- Find
- Connect
- Ask
Use a short chain. Let the event lead to a possible pressure, then let the pressure lead to a question.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Find | what changed in the account's situation | "What changed recently?" |
| Connect | what pressure that change may have created | "What work did that create?" |
| Ask | whether the pressure is active for this person | "How are you handling that?" |
Keep the wording plain so the prospect can correct you. The trigger gives you a reason to call, and the question shows whether that reason belongs in the conversation.
Find a trigger worth calling on
Start with a change the prospect will recognize as a reason to hear you out. Choose it for its connection to the person's work, then check that its timing still makes the call relevant.
A role-specific trigger can be a recent hire, a funding announcement, a seasonal spike in demand or a regulatory change.2 A job posting can also be the opening reference: "Hey, I looked at your job posting."4 A caller can incorporate a prospect's new role, the company's fundraising or another buying trigger into the explanation for the call.5
Before dialing, write the event in plain language and finish this thought: "Because this happened, they may now be dealing with..." If you cannot finish it without guessing, keep looking. The event should help you form a useful question, not decorate the first sentence.
Turn the event into a call reason
An event gives you context. The next line should explain why it matters to the work you want to discuss.
State your name and company, give a clear reason for calling, then choose a permission-based or value-led continuation.6 Name the change as the reason for outreach, connect it to the need it created, and make one specific ask.7 Giving the reason early raised success rates by roughly 2.1x in Gong's data.8
A useful wording pattern is: "I noticed [Company] recently [Specific event, change, or initiative]. Teams at that stage often encounter [Relevant problem or operational pressure]."9 Keep the pressure plausible and open to correction. Give the prospect a place to agree, disagree or add detail.
Use these event lines as starting points:
- "Hey, noticed that you just got funding."10
- "Hey, I looked at your job posting."4
- "I noticed your team just rolled out a new mobile app last quarter."11
- "I just finished reading the press release about the new office that you guys opened on Main Street"12
Follow each line with the pressure and question. After a hiring trigger, ask what the new hiring plan has changed in the person's workload. After a product launch, ask which part of the rollout has taken the most effort. Keep the connection close enough that the prospect can answer from experience.
Ask a question that tests the trigger
The question shows whether your reason for calling is live. Use an open question that invites the prospect to describe what they have tried or how they handle the work.
Lead with the observed trigger and follow it with an open question about whether the prospect has tried the relevant action.13 One example is: "hey, I saw your white background ads, like have you ever tried designing them before?"
Adapt the structure to the event in front of you. Ask what changed after the funding, which work the new hire owns, or how the team is handling the launch. These questions keep the prospect talking about their situation and give you a way to replace your assumption if it misses.
If the prospect sounds rushed, use a permission question after the trigger: "Can I get 30 seconds to tell you why I called, then you can tell me whether or not it makes sense for us to speak?"14 After they answer, stop adding setup and follow the answer they gave you.
Listen and move
The next move
- If they confirm the pressure, ask about its scope
- If they correct you, use their version
- If event has no bearing, close cleanly
Treat the response as a test of the trigger. The next move depends on whether the prospect confirms the pressure, corrects your premise or shows no connection to it.
When they confirm the pressure, ask about its scope or current approach. When they correct you, use their version of the situation as the new starting point. When the event has no bearing on their work, close cleanly or ask who handles that area. Move forward only when the prospect has supplied a problem, a consequence or a current approach you can discuss.
Stay curious and leave room after the question. A trigger opener loses its usefulness when the caller keeps explaining after the prospect has started answering.
What not to do
- Use an event connected to the prospect's work, and choose a role-specific trigger.2
- Give the reason for calling before a generic introduction; giving the reason early raised success rates by roughly 2.1x in Gong's data.8
- Name the change, connect it to the need and make one specific ask instead of listing several changes and asks.7
- Use timing to decide whether the trigger gives the call a reason to happen now.1