> 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/topics/relate/email/email-marketing-ways-to-send.md).

# Email Marketing - Ways to Send

There are different ways to send your marketing emails within SprintHub. Below, we will explain three of them in detail so you can choose the one that best fits your strategy.

{% embed url="<https://youtu.be/VwkRRXvFZkk>" %}

### Via the Service Page - Email Marketing

The first way is by going directly to the Email Marketing page.

If you haven't created your marketing email yet, we recommend following the step-by-step guide in this article: [Email Marketing](/en/topics/relate/email.md).

After creating the email, click Edit. On this screen, you will see that it is possible to select a segment.\
With the segment defined, just click on the name of the created marketing email. At the top, you will find two buttons:

* Send: will show the number of leads within the selected segment that will receive the email.
* Send test: allows you to test the delivery before performing the full send.

{% hint style="success" %}
Tip: if you want to send a test, create a test segment with one of your leads. This way, the send will be done realistically and you will be able to verify whether the content, layout, and settings are correct before sending it to the full audience.
{% endhint %}

### Via the Automation Flow

Another way to send it is through Automation Flows.

If you haven't created your flow yet, check out this article:  [Automation Flows](/en/topics/relate/automation-flows.md).

You can start the flow in two ways:

* Through automations; or
* By defining a segment (the leads in the segment will start the flow as soon as it is published).

Inside the builder, you will find several blocks such as:

* Action
* Condition
* Trigger
* Switcher
* Time limiter

For a simple marketing email send, just use the action block, select “Send email to lead,” and choose the desired marketing email.

### Via the Message Queue

The third way is through the Message Queue.

If you still don't know how to create a queue, see this article: [Message Queue](/en/topics/relate/message-queue.md).

In the queue, you can define the segment that will receive the send.\
By clicking on the name of the created queue, you can choose the type of send:

* Email
* WhatsApp
* WhatsApp Template

Since the focus here is email marketing, select the Email option and then choose the marketing email you want to send.

After configuring the send, you can:

* Drag the created card to “In queue,” and the email will be sent.

### Conclusion

These are the three main ways to send marketing emails on the platform. Each method has its advantages; you can choose the one that is most convenient for your workflow, whether through direct sending, automations, or scheduled queues.

<br>


---

# 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/topics/relate/email/email-marketing-ways-to-send.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.