> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/broadcast/broadcast-what-it-is-and-how-to-use-it-in-sprinthub.md).

# Broadcast: What it is and how to use it in SprintHub

The **Broadcast** is a SprintHub feature that allows automatic communication between different areas of the system, triggering events and executing actions without the need for manual intervention.

Simply put, it works like a **signal sent from an action**, which can be captured by a specific trigger to start a new automation, creating smart and dynamic flows.

This feature is widely used to integrate processes between modules such as **CRM, Support, Automation, Funnels, and Chatbots**, making operations faster and more automated.

### How does Broadcast work?

Broadcast works in two stages:

#### 1. Broadcast emission

First, an action within SprintHub generates a signal (broadcast).

This signal can be emitted by different events, such as:

* Change of stage in the funnel;
* Change in support status;
* Record update;
* Execution of an automation;
* Actions performed in CRM, Support, or Chatbots.

#### 2. Broadcast capture

After being emitted, a **trigger** can “listen” to this signal and execute an action automatically.

For example:

➡️ A contact is moved to a specific stage in the CRM;\
➡️ A broadcast is emitted;\
➡️ The support system identifies this event;\
➡️ The service window is automatically moved to another department or queue.

### When to use Broadcast?

Broadcast is ideal for scenarios where you want to **automate processes between different parts of the system**, avoiding manual actions and reducing operational errors.

Usage examples:

✅ Automatically move support tickets in the support system;\
✅ Change support owners;\
✅ Trigger automations after changes in CRM;\
✅ Synchronize actions between Chatbot and Support;\
✅ Automatically update funnel stages;\
✅ Create smart integrations between modules.

### Practical example in SprintHub

Imagine the following scenario:

A lead advances to the stage **“Payment Approved”** in the CRM.

When this movement occurs:

1. The CRM emits a Broadcast;
2. A trigger captures this event;
3. The support case is automatically directed to the **Onboarding**;
4. department. An automation can be started to send welcome messages.

All of this happens automatically, without the team needing to move anything manually.

### Broadcast benefits

🚀 **Process automation** — reduces repetitive tasks;\
⚡ **Operational agility** — actions happen in real time;\
🔄 **Integration between modules** — CRM, Support, and automations work together;\
🎯 **Fewer manual errors** — reduces oversights and rework;\
📈 **Greater productivity** — teams focus on support, not operational processes.

### Conclusion

Broadcast is an essential feature for anyone who wants to create smarter processes within SprintHub. With it, you can connect different areas of the system and automate actions in a practical way, ensuring greater efficiency, organization, and speed in contact service and management.

In the next articles, you will see practical examples of configuration and use of Broadcast in different scenarios within SprintHub.

***


---

# 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.sprinthub.com/en/strategies/broadcast/broadcast-what-it-is-and-how-to-use-it-in-sprinthub.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.