Context
What it is for
The Context is what the agent knows about the business before talking to anyone: its name, what the company does, who it sells to, the tone it speaks in, which topics it can talk about and how it sells. The AI agents do not run until the base variables are complete.
How to get there
Settings → Context · app.growtek.io/en/settings/context
The screen in detail
- Agent context: the main form, with Save changes.
- Download / Import: export the context to a Markdown file or load it from one.
- Agent tools: what the agent can do based on the enabled modules (Product sales, Service sales, Project sales, Appointment scheduling, PQRS / Tickets). It is read-only.
- If something required is missing: the The agent context is incomplete notice.
The fields
Identity and scope
| Field | What to enter |
|---|---|
| Agent name | How it introduces itself (for example, Sofía). |
| Company name | |
| Company description | What it does, its main products and services. |
| Target audience | Who it sells to: type of customer, sector, needs. |
| Brand voice | The tone: friendly, professional, formal… |
| Allowed topics | The topics it can talk about, separated by commas. |
| Default deflection message | What it replies when the query falls outside the allowed topics. |
Disambiguation
- Disambiguation policy: the priority order among the enabled verticals (Product Sale, Service Sale, Project Sale, Call Scheduling, Sale Closing), with Move up and Move down. The verticals are enabled by a Growtek administrator; here you only order them.
- Disambiguation criteria (optional): how to decide when the customer is ambiguous, in the business's own words.
Sales
- Sale processing (optional): how to close a sale (payment link, payment methods, whether it asks for a receipt). The platform does not process payments: the agent only passes on what you indicate.
- Agent commercial role: Informational only, Setter (qualify & book), Closer (close the sale) or Setter + Closer. Depending on the role, Qualification & booking process, Closing process, Persuasion & negotiation techniques and Completion criteria appear.
Customer types
If the business serves different audiences (for example reseller and end consumer), turn off Applies to any customer type and define each type with:
- Name, How to recognize them and How to handle them (replaces the general process while it talks with that type).
- Out of their scope: what the agent cannot do with that type (Catalog prices, Product, service or project catalog, Cart and payment, Close the sale, Schedule a call). Handing off to a person and filing a case are always available.
- Usual level of need: which products it shows first (No preference, Basic (affordable first), Intermediate, Advanced (high-end first)).
Knowledge base
- Message when it's not in the knowledge base.
- Allow web search (off by default).
- Knowledge base threshold: from 0 to 1; empty = Automatic.
Cart checkout
If the business sells a closed catalog over chat, Build orders over chat lets the agent build the order with the catalog prices, collect payment and file a sales ticket. You configure Payment method (Transfer to a key or account, Payment on the business website or Cash on delivery), Currency, Shipping fee, Free shipping from, Payment key or account, Account holder, Payment URL and Note when collecting. The amounts are calculated by the system, not by the agent.
What you can do
Complete the context
- Fill in Agent name, Company name, Company description, Target audience and Brand voice.
- Define the Allowed topics and the Default deflection message.
- Order the Disambiguation policy and, if you want, fill in the optional fields.
- Click Save changes.
How to verify: the The agent context is incomplete notice disappears and the Agent context item on the checklist is marked as done.
Export or import the context
- Download downloads the context as Markdown, with the changes you have on screen.
- Import loads a Markdown file over the form. It does not save: review it and click Save changes. Sections it does not recognize are ignored.
Required permissions
| Action | Permission |
|---|---|
| View the context | workspace.viewSettings |
| Edit it | agentSettings.manageContexto |
Without agentSettings.manageContexto the fields are read-only.
FAQ
The agent doesn't reply at all. Check that the context is complete: without the base variables, the agents do not run.
It says there are no enabled verticals. A Growtek administrator has to enable at least one; request it through support.