> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Define your use case

Every Nexor onboarding starts with a short consulting conversation. Before touching any setting, the team asks a fixed set of questions and writes the answers down. Those answers become the agent's goal, variables, pipeline, and rules. Do the same exercise here, on your own, before building anything.

## The questions

Answer each one in a sentence or two. If you cannot answer one yet, note it as open. Do not skip it.

| Question                                                                                | Why it matters                                                                        | Where the answer lands                           |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------ |
| What do you want to achieve?                                                            | Defines the single outcome the agent works toward in every conversation.              | The agent's **Goal**.                            |
| Where do your leads live, or where do they come from?                                   | Decides how leads enter Nexor: manual, CSV, a CRM, forms, or the API.                 | Lead import and integrations.                    |
| Which channels do you want to use?                                                      | Decides what you connect and which channel opens the conversation.                    | **Channels** and the first-contact channel.      |
| What information must the agent collect?                                                | Becomes the fields the agent extracts from each conversation.                         | **Variables**, marked required or optional.      |
| How do you qualify a lead?                                                              | Becomes the rules that move a lead forward, and the data required before it advances. | **Pipeline** stages and their gates.             |
| What is the final state: book, collect payment, deliver information, or something else? | Confirms the goal and the stage that counts as won.                                   | **Goal** and the winning stage of the pipeline.  |
| What must the agent never do, and when should a person step in?                         | Sets the limits and the escalation triggers.                                          | **Business rules**: agent limits and escalation. |

<Tip>
  Answer as the person who sells or supports today would. The best agent configurations describe what a good seller already does, not an idealized process nobody follows.
</Tip>

## Worksheet

Copy this block, fill it in, and keep it open while you build. You will paste parts of it into NexorGPT and into the agent's settings.

```text theme={null}
Goal (one sentence, an observable outcome):
Leads come from:
Channels (first contact + replies):
Information to collect (mark required / optional):
  - 
  - 
Qualification criteria (what makes a lead a good fit):
Final state (won):
Lost or discard conditions:
Agent must never:
Hand off to a person when:
Company facts the agent needs (files, website, catalog):
```

## Example

Stark Industries sells industrial equipment and wants to book demos with qualified buyers.

```text theme={null}
Goal: Book a demo with buyers who have budget and a real project this quarter.
Leads come from: A web form connected to HubSpot, plus a monthly CSV from events.
Channels: WhatsApp first, email for follow-ups, calls only for leads who ask.
Information to collect:
  - Company size (required)
  - Project timeline (required)
  - Current equipment (optional)
  - Budget range (required)
Qualification criteria: Budget above the entry tier and a timeline within 90 days.
Final state (won): Demo scheduled.
Lost or discard conditions: No budget, no project, or asks to be removed.
Agent must never: Quote final prices, promise delivery dates, or discuss competitors.
Hand off to a person when: The lead asks for one, complains, or requests a custom integration.
Company facts: Product spec PDFs, pricing tiers page, and the public website.
```

## When the answers point to more than one agent

If your answers describe several different intentions, such as "qualify and book" for new leads and "collect an overdue payment" for existing customers, do not force them into one agent with one very long prompt. Plan one agent per intention and connect them with transfers. See [Connected agents](/docs/en/guides/getting-started/connected-agents).

<Note>
  Nexor supports eight goals: book a meeting, send a payment link, lead qualification, provide information, customer support, document collection, generate a quote, and a custom goal you describe yourself. If your "final state" fits none of the first seven, the custom goal is the right choice. See [Agent settings](/docs/en/guides/agents/settings#goal).
</Note>

## Next

Take the worksheet to [Anatomy of an agent](/docs/en/guides/getting-started/anatomy-of-an-agent) to see where every answer goes, or jump straight to [Build with NexorGPT](/docs/en/guides/getting-started/build-with-nexorgpt) to create the agent from it.