> 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/convert/forms/forms-tutorial-videos/forms-how-to-create-opportunities-for-different-owners.md).

# Forms - How to Create Opportunities for Different Owners

At events, lead generation is a crucial step for sales success. When several salespeople fill out forms with new contacts, it is essential that these opportunities are recorded correctly and assigned to the person responsible for the submission, avoiding confusion and rework.

In this tutorial, you will learn how to set up an automation that ensures each created opportunity is automatically linked to the salesperson who filled out the form. To do this, we will use a UTM Tag, which will allow you to identify the source of the submission and correctly associate each lead with the person responsible. Check out the step-by-step guide and optimize your sales process!

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


---

# 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/convert/forms/forms-tutorial-videos/forms-how-to-create-opportunities-for-different-owners.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.