How to build a sales engagement to CRM sync

What matters here

• Do not log every automated send. Summarise the sequence and log the replies, opens on high intent, and anything a human did.
• Suppression is the reason to build this. An open opportunity, an active support escalation or a legal hold must stop a sequence.
• Define engagement once. If the CRM and the engagement tool disagree about what engaged means, every report built on either is wrong.
• Drive enrolment from CRM state, not an exported list. A list is stale the moment it is downloaded.
• Never let a sequence reach somebody who unsubscribed, regardless of which system holds the record.

Who this is for

You run revenue operations or sales operations. Reps work in the engagement tool, managers report from the CRM, and the two disagree about what happened and to whom.

How it works in practice

What happens between a rep enrolling somebody and the CRM reflecting it usefully.

1. 1

   Enrolment is driven from CRM state

   A saved view, not an exported list, so somebody who converted this morning is not sequenced this afternoon.

2. 2

   Suppression runs before every send

   Open opportunity, active escalation, legal hold, unsubscribed, already in another sequence. Checked at send time instead of at enrolment.

3. 3

   Activity is logged at a readable level

   The sequence as one record, plus replies, meetings and anything a human did individually.

4. 4

   Engagement is computed once

   One definition, applied in one place, written to both systems rather than calculated twice with different answers.

5. 5

   A reply pulls the person out of automation

   Immediately, and notifies the owner. Nothing is worse than a sequence continuing after somebody answered.

6. 6

   The CRM stays the reporting surface

   Managers report from one place, and it agrees with what the reps see.

Paste these into Claude Code or Codex with the Tray Headless plugin installed. Each stage runs on its own. The systems named in them are the worked example rather than a requirement, and every prompt says so.

Once per project, run /tray-workflows:set-workspace to pick the workspace these build in. Point it at a sandbox first.

1. 1

   Set up and find where suppression state actually lives

   The reasons not to send are scattered across several systems.

   Headless skills build-workflow

   Copy

   Use build-workflow. The systems in play are Salesforce and Outreach,
   or whatever we run in those seats.
   
   I need the Outreach prospect and sequence model including how enrolment
   and finishing work, and from Salesforce the Lead, Contact, Opportunity
   and Case objects plus any opt-out field.
   
   Specifically map where each of these lives: an open opportunity, an
   active support escalation, a legal or compliance hold, and an
   unsubscribe. Those four are the reasons not to send, and they are in
   different places.

2. 2

   Suppress at send time, not at enrolment

   Because state changes between enrolling somebody and emailing them.

   Headless skills build-workflow

   Copy

   Use build-workflow. Before every send, not once at enrolment, check:
   
     An open opportunity on the account owned by somebody else
     An active support escalation above a severity
     A legal or compliance hold on the account
     An unsubscribe, in either system, treated as authoritative
     The person already active in another sequence
     The account in a do-not-contact list
   
   Any hit pauses the sequence for that person and tells the enroller why.
   
   Do this at send time. A prospect enrolled on Monday whose account opened
   an escalation on Tuesday must not receive Wednesday’s email, and an
   enrolment-time check will not catch that.

   This is the step that prevents the incident everybody remembers: an automated nudge landing while an account is escalated or in negotiation.

3. 3

   Log at a level somebody will read

   A timeline of four thousand automated emails is a timeline nobody scrolls.

   Copy

   Log to the CRM selectively:
   
     The sequence enrolment as one activity record, with the sequence name
     and the enroller, updated as it progresses rather than appended to
     Every reply, logged individually with its content
     Every meeting booked
     Calls and manually sent one-to-one emails
     Sequence completion or exit, with the reason
   
   Do not log every automated send, every open and every click as separate
   activities. Roll those into counts on the sequence record.
   
   Then update Last Activity Date from meaningful interactions only. If an
   automated open refreshes it, every hygiene rule that depends on activity
   becomes meaningless, and pipeline hygiene is usually built on exactly
   that field.

4. 4

   Define engagement once

   Two definitions produce two dashboards and a standing argument.

   Headless skills tray-gotchas

   Copy

   Use tray-gotchas, then compute engagement in one place and write the
   result to both systems.
   
   A workable definition: a reply, a meeting booked, or a click on a
   high-intent link. Opens do not count, because open tracking is now
   unreliable enough that including it makes the metric noise.
   
   Write an engagement score and a last-engaged timestamp to both. Never let
   each system compute its own, because they will diverge within a week and
   every report built on either becomes indefensible.
   
   Also pull somebody out of automation the moment they reply, and notify
   the owner within minutes. A sequence that continues after a human
   answered is the fastest way to lose a deal you had.

5. 5

   Enrol from live CRM state

   An exported list is stale the moment it is downloaded.

   Copy

   Drive enrolment from a saved CRM view evaluated at run time, not from a
   list somebody exported.
   
   Re-evaluate membership before each send. Somebody who converted, became
   a customer or opened an opportunity since enrolment leaves the sequence
   automatically instead of continuing to receive prospecting email.
   
   Then report weekly: sends suppressed and by which rule, replies and
   meetings by sequence, sequences continuing after a reply, which should be
   zero, and any send that reached a suppressed account, which should also
   be zero.
   
   Those two zeros are the health of this integration. Everything else is
   volume.

6. 6

   Validate, then hand the rules over

   Because suppression rules are commercial policy.

   Copy

   Run the per-step schema checks and the whole-workflow audit before this
   touches production.
   
   Then open the same workflow in Tray Build so sales operations can add a
   suppression rule or change the engagement definition in the visual
   canvas. Those rules change after every incident, and the change should
   take an afternoon rather than a sprint.

What it connects to

The engagement tool sends, the CRM decides who may be sent to.

Named systems are the ones most teams run, not the only ones that work. Each is an authentication in your Tray workspace, referenced by name, so the workflow never holds a credential. Where we have a connector page, the name links to it.

Questions people ask

Related guides