> 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/integrations/superoffice/superoffice-journey-steps/so-create-sale.md).

# Create sale

<div align="left" data-with-frame="true"><img src="/files/yY9Ljp1lSDVWJv1Ob0PE" alt="Create sale step settings panel"></div>

## Settings

**Sales type:** Sets the type of sale. Choose from the available sales types in your connected SuperOffice account.

**Sales status:** Sets the current status of the sale in the sales cycle. Choose from the available statuses in your connected SuperOffice account.

**Sales value:** Sets an estimated value for the sale. The assigned SuperOffice user can update this later.

**Assign Sale:** Assign the sale to a specific SuperOffice user, or use the dynamic **Our contact** option. Our contact is the user assigned to the contact's company under the Our contact field on the SuperOffice company card.

**Sale description in SuperOffice:** A description for the sale. Type @ to insert personalized merge fields. The description also appears in the **Text** column of the Sales tab on Contacts and Companies in SuperOffice.

**Place Sale in a SuperOffice project:** Assign a project to add both the sale and the contact to a SuperOffice project of your choice.


---

# 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:

```
GET https://support.emarketeer.com/integrations/superoffice/superoffice-journey-steps/so-create-sale.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
