> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-change-lead-stage.md).

# Change Lead Stage

Journey step that moves the contact's lead to another stage on the Lead Board.

The Change Lead Stage step moves the contact's lead to another stage.

This is useful in lead nurturing Journeys, to move a lead from MQL to a more significant stage, such as SQL or Opportunity, when it's ready.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-faa6ab6969453e0cf9091699a16261b687c2a663%2Fjourney-step-change-lead-stage-settings.png?alt=media" alt="Change Stage dialog with a field to choose the lead stage"></div>

## Settings

* **Choose Lead Stage to place the lead** — select the stage the lead is moved to. The stages are:
  * MQL
  * SQL
  * Opportunity
  * Won
  * Lost

Click **Apply** to save the step.

The step only affects contacts on the Lead Board. If the contact is on several Lead Boards, the stage is changed on all of them. See [The lead board](https://support.emarketeer.com/guides/lead-board-scoring/the-lead-board.md).

## Use with SuperOffice sales

If you use SuperOffice, combine this step with the [Sale Sold](https://support.emarketeer.com/integrations/superoffice/superoffice-signals.md#sale-sold) and [Sale Lost](https://support.emarketeer.com/integrations/superoffice/superoffice-signals.md#sale-lost) signals. When a sale is closed in SuperOffice, a Journey started by the signal can move the lead to **Won** or **Lost** in eMarketeer automatically.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-change-lead-stage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
