> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Company news and public engagement

> Qualify public company events and discussions before proposing an account action.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/signal-company-news.md)

> [!NOTE]
>
> Turn one dated company event into a supported research question or review
> action.

Use this page when a public company event or discussion might change an account
decision. It owns the event-specific evidence and messaging boundary. The
shared collection, owner, suppression, and activation steps live in [signal
playbooks](https://deepline.com/docs/plays/signal-playbooks.md).

## Keep the evidence attached

For every candidate, keep the source URL, observed date, account match,
affected function, and a proposed action. A headline or public post without a
relevant account problem is a research lead, not an outreach trigger.

## Qualify the event

| Public event | What to verify before routing |
| - | - |
| M\&A or restructuring | The source, date, affected function, and whether the account is already in an active motion. |
| New executive | The current role, scope, and whether the event relates to a problem you solve. |
| Regulatory event | The actual requirement or exposure, not an assumed compliance project. |
| Product launch or expansion | The event, affected team, and a relevant operational problem. |
| Public topic discussion | The person’s public statement and account fit. do not infer intent from a like or view. |

Route existing customers and active opportunities to their account or deal
owner. Send uncertain matches to review instead of inferring a role, urgency,
or budget.

## Public-engagement boundary

Reference the topic, never the fact that you watched someone engage with it.

| Use in a reviewed draft | Do not use |
| - | - |
| A public idea the person wrote about | A claim that you tracked a like, view, or timestamp |
| A source-backed problem connected to your offer | An assumed buying motive from social activity |
| One useful point about the topic | Separate touches for every event on the same account |

## Prepare the review file

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Review target-accounts.csv for recent public company events and
public discussions about [topic]. For each candidate, return the source URL,
observed date, event type, affected function, account fit, owner or suppression
check, and one proposed action. Keep uncertain matches for review.
```

If several events occur at one account, combine the verified context into one
reviewed decision. Follow the [signal-combination
policy](https://deepline.com/docs/plays/signal-deal-risk.md) rather than creating separate touches.

***

**Related:** [Champion Tracking](https://deepline.com/docs/plays/signal-champion-tracking.md) | [Hiring Signals](https://deepline.com/docs/plays/signal-hiring.md) | [Fundraising Signals](https://deepline.com/docs/plays/signal-fundraising.md) | [Competitive Intelligence](https://deepline.com/docs/plays/signal-competitive-intel.md)

## Verify this task

Check company identity, source date, event meaning, and whether the proposed action follows from the evidence.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.