Trigger-based messaging works when an event changes the prospect's situation and the message explains why that change gives them a reason to talk. The trigger opens the conversation. The rest of the message explains what changed, why it matters now, and how your help fits. A familiar event can be true and still give you no useful angle unless it changes the prospect's reason to act.
Find the event
Start with an event you can state plainly, then decide whether it gives the prospect a reason to reconsider the problem now.
Use a change, trend, current event, or upcoming moment as raw material. An upcoming event such as Black Friday can create urgency for a call.1 Keep an event only when it changes the message you would send to that account. If the same sentence could go to every prospect, the event has not done enough work.
Ask yourself what happened, who it affects, and what the prospect would do differently because of it. Move on when you can answer those questions without adding assumptions.
Test the trigger
Before a trigger reaches your copy, test whether you can explain why the event matters to this prospect now.
Look for a connection between the event and the reason you are contacting the person. A signal with no connection leaves the recipient to interpret it for you, creating a weak opening even when the signal is accurate.
Write the answer in one sentence: "This matters because..." Then ask whether it gives the prospect a problem, decision, or change worth discussing and a clear consequence for the account.
Turn the event into a reason to talk
After the trigger passes the relevance test, connect the event to its effect and then to the help you can offer. The message should make that path easy to follow.
Connect industry trends and current events to how the seller can help the prospect stay ahead.2 Name the change, explain what it may affect, and connect that effect to a useful conversation.
Ask what the event makes harder, more urgent, or newly possible for the prospect. That answer should guide the angle. If you cannot reach a clear consequence, remove the trigger and keep working on the problem.
Put the trigger into the message sequence
The trigger should give the outreach a reason to exist. Keep the wording close to the event, then make the next sentence explain why you are reaching out.
Building trigger events into messaging is one way to make automated messaging professional.3 Use the trigger where timing matters, then let the rest of the sequence develop the business context. Each follow up should add a reason to continue the conversation instead of repeating the event in new words.
Before sending, read the message without the event. If the copy still makes sense as a generic pitch, the trigger is sitting on top of the message instead of shaping it. Revise until the event changes the reason for contact.
Configure the event path
When the message is automated, the copy and event handling need to match. Set up the source and conditions before increasing volume.
On the Campaign set up page, select Customer event under Recipients.4 Select Event source to specify where the data originates, then configure the attribute conditions that activate the event trigger.5 Event sources are based on integrations in Customer Profiles.6 They can also integrate with Kinesis or S3.7 Select the Delivery mode and additional communication settings after the event rules are in place.8
Keep the conditions close to the message logic. If the message refers to a specific change, the trigger should identify that change clearly enough for the recipient and the sender to understand why the message was sent. You should be able to trace the event from its source to the intended delivery settings.
Send only the context the message needs
An automated message depends on the information that reaches the sending system. Pass enough context to explain the outreach and let the recipient respond to the actual event.
A Salesforce outbound message sends information to an external service as a SOAP message over HTTP(S) when specific criteria are met.9 After configuration, it sends a message to the designated endpoint whenever the triggering event occurs.10 The message includes the fields selected during creation.11 Select fields that support the reason for contact and the follow up you want to have.
Plan for the handoff itself. Outbound Messages require a public URL to receive notifications and bring security considerations with them.12 Notifications cannot be replayed, and they are not guaranteed to arrive in the order in which events occurred.13 Each notification includes an ID, which gives you a way to trace the handoff even though replay is unavailable.14 If a record changes before its message is sent, the message may contain only the latest data from the most recent change.15
Use those limits when you write the copy. Avoid wording that depends on a historical state you may not receive. Keep a record of the event and payload used for the message so a rep can understand what prompted the outreach.
Verify before you scale
Run the full path with a test event before adding more contacts. Watch the event source, condition, workflow, delivery step, endpoint, and received payload separately.
Each part should be observable before you add more contacts. A configured trigger can still fail to call the workflow, so a successful setup screen is not enough. Check that the recipient qualifies, the event condition matches, the workflow runs, and the message arrives with the fields the copy expects.
If the message arrives without the event context, fix the payload or the condition before changing the wording. If the event never reaches the workflow, fix the event path before changing the offer.
What not to do
Use these checks before a trigger enters an outbound sequence.
- Do not use a stale trigger such as "congrats on the funding". That kind of message can blend in with everyone else's outreach.16
- Do not use a trigger that is not based on time without tying it to the context for why you are reaching out.17
- Do not assume an enabled trigger fired because the configuration looks correct. In a reported test, the workflow was never called during outbound campaign calls.18 The setup used the outbound topic, targeted a workflow, was enabled, used version 1, and had no match criteria.19 The workflow existed, duplicated a working test workflow, and worked when tested with other triggers.20
- Do not design the handoff around ordered or replayable notifications.13