> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/account/alerts.md).

# Alerts

* [How Alerts Work](#how-alerts-work)
* [Use Cases](#use-cases)

High-intent moments *don’t last long.* Alerts help teams:

* Respond to hot leads and target accounts within minutes
* Eliminate delayed marketing → sales hand-offs
* Prioritize outreach based on real demo engagement
* Increase conversion rates and shorten sales cycles

### 👉 **How Alerts work**

Create alerts based on specific engagement triggers like demo views, CTA clicks, lead intent scoring, form submissions, demo hub engagement, account-level activity, and more.

Alerts can be delivered via **Slack,** **email or webhooks** - and are fully customizable, so sales and marketing teams get the exact signals they need, exactly when they need them.

Webhooks are now configured directly within Alerts — see [Webhooks](https://docs.storylane.io/~/revisions/wvJjZwaqg9YdnObIwOpF/integrations/integrations-and-data-flow/webhooks) to learn more about custom headers and setup.

Try the Interactive Demo Yourself 👇

{% @storylane/embed subdomain="app" linkValue="rqzcwygfaztz" url="<https://app.storylane.io/demo/rqzcwygfaztz>" %}

***

### **👉 Use Cases**

**For Sales teams:**\
Alerts can be routed to specific reps, SDRs, inboxes, or Slack channels, ensuring sellers are notified in real time and can act immediately when a prospect engages. The triggers that matter most for sales:

* **CTA Clicked** — a prospect clicking "Book a call" or similar is a strong hand-raise; route this straight to the rep's Slack DM
* **High Intent reached** — notify the account owner the moment a contact's engagement crosses into High intent
* **Account-level activity** — get notified when multiple contacts from the same target account engage with a demo, signaling a buying committee forming
* **Demo Completion** — alert reps when a prospect finishes a demo, so follow-up happens while it's still top of mind

**For Marketing teams:**\
Alerts notify sales the moment high-intent leads interact with a demo or form, enabling fast, seamless hand-offs and stronger alignment between marketing and revenue teams. The triggers that matter most for marketing:

* **Form Submissions** — know instantly when a new lead fills out a demo or Hub form
* **Hub Engagement** — track when a prospect opens or revisits a shared Buyer Hub, useful for measuring campaign follow-through
* **Intent tier changes** — get notified when a nurtured lead moves from Low/Medium to High intent, signaling it's ready for sales hand-off
* **Webhook delivery** — route engagement data into your CRM or marketing automation workflows automatically, instead of relying on manual exports

{% hint style="info" %}
Still have questions or need help? Feel free to contact us at ➜ <support@storylane.io>  🙂 Chat soon!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storylane.io/account/alerts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.