Select one signal entry point and produce an evidence-backed review action
before activation.
A signal is evidence that something changed at an account or with a contact. It
is not proof of budget, intent, or permission to contact someone. When Deepline
has a supported Monitor for that event source, the Monitor should receive
and store the event. A Play then qualifies the row and produces a
reviewable decision. Use a scheduled or agent-run Play only when no Monitor
endpoint exists for the source.This page owns the shared execution pattern. The linked pages own the evidence
and decision boundary for each specific trigger.
If a supported source pushes the event, deploy the narrowest matching
Monitor. Otherwise define a bounded account or contact list and run a
scheduled or agent-run Play against it.
2
Collect and retain evidence
Save the source URL or record ID, observed date, and the field that matched
the account or contact. Keep uncertain matches visible rather than turning
them into facts.
3
Qualify the signal
Apply the trigger-specific checks in the linked guide, then check ICP fit,
account status, ownership, suppression rules, and duplicate activity.
4
Choose one next action
Write a reviewable draft, route the evidence to an account owner, update a
CRM review file, or take no action. Record the reason for that choice.
One account can generate several signals. Do not turn each event into a new
touch. Combine related evidence into one reviewed decision, and stop
signal-triggered outreach when the account is already in an active sales
motion. This page is the source of the shared qualification and contact-safety
policy.Do not automatically send a message, overwrite a CRM field, or reassign an
account because a signal matched. Preserve the source, proposed action, and
review state so the owner can verify the decision.For an active deal that needs a ranked human-review queue, use Deal risk
review. That guide applies this shared policy to
pipeline evidence. It does not define a second outreach policy.
/deepline-gtm Review target-accounts.csv for [signal]. Run a representative pilot.For every candidate, return the evidence URL, observed date, account match,qualification result, owner or suppression check, and one proposed next action.Do not send messages or write to the CRM.
Use a Monitor when a supported external source pushes an
event into Deepline. Current Monitor types are Deepline Native company and
contact radars. Use a scheduled Play or an agent-run file workflow when you
need to look for a source on a timer. A Monitor records the event. A Play
contains the code that qualifies it and takes any approved action. Inspect the
Monitor contract reference before
choosing a type.
Keep source event, accepted evidence, business decision, and destination action separate. Choose a Monitor only for supported feeds.Ask your agent to explain a failed check before repeating work or expanding the scope.
