Anatomy of an agent

An agent is a set of blocks that together decide what it pursues, what it says, what it collects, and how it moves each lead forward. This page tours the blocks in the order the Nexor team presents them in onboarding, and says what each one is for. For the full field-by-field reference, see Agent settings. Open any agent and go to its settings. Each block below appears as its own section.

​

Goal

The goal is the result the agent works toward in every conversation. Choose it first, because it changes the tools the agent gets, the suggested pipeline stages, and which configuration sections appear. The presets cover booking a meeting, sending a payment link, qualifying leads, providing information, customer support, collecting documents, and generating a quote. If your outcome is different, such as debt collection, win-back, post-sale follow-up, or a survey, pick Custom and describe the outcome in one or two sentences.

​

Variables

Variables are the pieces of information the agent collects from each lead. As the conversation goes on, the agent extracts each value from what the lead says and stores it on the lead. The distinction that matters most is required versus optional: Take the “information to collect” list from your worksheet and create one variable per item, marking the required ones.

​

Identity

The identity block sets the name the agent uses, the role it plays, the company it represents, the language and regional variant, the time zone, and the voice for calls. It takes a minute and shapes every introduction the agent makes.

​

Business rules

The business rules are the agent’s prompt. This is where you describe what the business does, what the agent must never do, how it handles objections, when it escalates to a person, what a good conversation looks like, and when it should stop pursuing a lead. You do not need to fill every section before testing. Start with the business context, train the agent, test it, and refine the other sections from what you see. After every edit, click Train your agent so the change takes effect. See Prompt best practices for what goes in each section.

​

Knowledge base

The knowledge base is what the agent knows about your company beyond the prompt: files, website pages, and catalogs. Without it, the agent can only talk about what you wrote in the rules. With it, it answers questions about products, policies, and processes from your actual material. Connect the sources listed in your worksheet, then enable them on the agent. Only enabled sources are used. See the Knowledge base guide.

​

Pipeline

The pipeline is the set of stages each lead moves through, from new to won or lost. As the agent talks to a lead, it moves the lead between stages based on the transition instructions you write. Two things to keep in mind:

• It is not a CRM. The pipeline is a visualization of where each lead is in the agent’s process. Your CRM stays the system of record, and Nexor can sync to it.
• You define it. Nexor proposes stages that match the goal, and you can add, rename, and reorder stages to mirror how your team thinks about the process.

Each stage can require variables before a lead enters it. That is how the “how do you qualify” answer from your worksheet becomes enforceable.

​

Contact settings

The agent behaves like a persistent seller: it reaches out, waits, follows up, and eventually gives up. Two blocks control this. Both are flexible: multiple windows per day, different ranges per day, and per-stage overrides. Details in Operation and channels.

​

Channels

The channels block shows everything the agent can talk through and whether each one is connected: WhatsApp, email, phone, SMS, Instagram, and web chat. The first-contact channel decides where the first outbound message goes. You do not need every channel to start. Most teams connect WhatsApp first. See Operation and channels.

​

Tools

Tools let the agent do things outside the conversation: look up a customer in your CRM, check inventory, calculate a price, or create a record somewhere else. Every agent gets built-in tools for its goal. Custom tools are HTTP calls your team defines.

​

Next

You now know what each block does. Go to Build with NexorGPT to fill them in by chat, or open the agent’s settings and fill them in directly using the settings reference.