> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/lead-management-workflow/cold-outbound-email-campaigns.md).

# Cold outbound email campaigns

1. #### Prepare your email campaign
2. #### Plan your qualification Workflow
3. #### Implement workflow in LeadBoxer
4. #### Deploy your campaign

***

## Detailed step-by-step guide to setup your cold outbound email campaign workflow

### Preparations outside of LeadBoxer

1. Define Goal of campaign (example: get more sales calls)
2. Define Target Audience (industry, size, location);
   1. Find target companies (generate a list of companies to contact / target)
   2. Find persons (from the list of companies, generate a list of the correct person(s), based on title /role)
   3. Find emails ( generate a list of contact email addresses)
3. Design the campaign (emails, copy, interval, landing pages, CTA)
4. Build the campaign in email platform

### Preparations for LeadBoxer (needed to build workflow in Leadboxer)

1. Define the stages your leads go through in order to become Opportunities 
2. Create a list of key events that can be measured and map these to each stage. Another way of thinking of stages is column names on a pipeline which read from left to right. For example:
   1. Discovery: Recipients engage with your landing page and browse your site (blog, fact-sheet, pdf download)
   2. Interest: Recipients show buyer intent (sign up, create account, book a demo, join a webinar)
   3. Intent: Recipients convert to opportunities (schedule call with Sales)
3. Define the End Action (handover) for qualified opportunities. How do you want to hand the opportunity over to sales? Options are:
   1. Send daily or weekly overview notifications (email, CSV) to sales person or team
   2. Assign an individual lead to a sales colleague and send a notification
   3. Sync to CRM
4. <mark style="color:blue;">Define cleanup workflow, when do you want qualified leads to disappear from the board. (Coming Soon)</mark>&#x20;

### Setting up the workflow in LeadBoxer (this work is done in Leadboxer)

5. Create a new LeadBoard and add the stages (columns) from Step 1&#x20;
6. Add workflow automations, to:&#x20;
   1. map the behavioural events you defined in Step 2 to the corresponding stages you defined in Step 1
   2. add tags for easy visual recognition (optional)
   3. Define the End Action
   4. <mark style="color:blue;">Define cleanup workflow (Coming Soon)</mark>&#x20;
7. Create Segments for each important stage using the LeadBoard stage filter

### Launch Campaign

1. Important: add LeadBoxer tracking and click-thru technology
2. Start sending emails<br>

### Expected Results

1. Recipients begin opening emails. The automation will insert these in the first stage of the LeadBoard&#x20;
2. Recipients who click on the CTA inside the email and land on your website will automatically be moved to the second stage
3. Once identified on the website, their behaviour is tracked (including future visits) and when they perform a defined key event the automation will move them to the next stage. Depending on your designed workflow, this process repeats until Leads are qualified.
4. Once Leads are qualified (aka opportunities) the End Action is triggered
5. <mark style="color:blue;">After end action, the cleanup process takes place (coming soon)</mark>
6. Create or auto receive Reports from the defined Segments to monitor ongoing campaigns and report to all stakeholders

\
\ <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://help.leadboxer.com/leadboxer/lead-management-workflow/cold-outbound-email-campaigns.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.