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

> ## Agent Instructions
> Use the public API base URL: https://api.teamfollowup.ai/api.
> Authenticate public API requests with Authorization: Bearer YOUR_API_KEY.
> Use product-owned terms: agents, campaigns, projects (GoHighLevel sub-accounts), contacts, calls, outcomes, skills, cadences, phone numbers.
> Scope requests by locationId rather than projectName.
> Read the guide linked from each API reference group before recommending an endpoint.

# Variables and context

> Use real contact, business and call context without inventing placeholder values.

Variables let one script use the right information for each call. Their names
are a contract: typing a plausible name between double braces does not create
a data source.

## Three sources of context

| Source | Typical meaning | What to check |
| - | - | - |
| Contact fields | A lead's name, answers or preferences | The field exists in the selected CRM location and has a value for that contact. |
| Business custom values | Facts shared by a location | The value belongs to that location and is connected to the agent. |
| Call and system context | Information supplied when a call starts | The exact supported key, its format and when it is populated. |

For a supported variable, establish its exact key, source, availability and
behavior when empty before relying on it in a script. Never assume that a time
value uses the caller's timezone; check the configured source and timezone.

## Add context to a script

1. Open the agent's context settings and review the fields already connected.
2. Select an existing field or custom value from the location’s list.
3. Connect it to the agent, then insert the variable into the script.
4. Write instructions for how to use the information. If it is missing, ask the
   caller naturally or omit the detail instead of speaking a placeholder.
5. Test with a contact that has a value and one that does not.

See [CRM context fields](/agents/crm-context-fields) for the editing controls
and [GHL resources](/concepts/crm-resources) for calendars, tags and pipelines.

## Business knowledge or a variable?

A durable explanation such as your service area belongs in
[business knowledge](/agents/knowledge-base). A fact that differs for each lead
belongs in contact context. For a master campaign, check
[what stays local](/campaigns/master-agent/what-syncs) before making one
location's information part of a shared script.

## In the API

* [Update agent](/api-reference/agents/update-agent) sets `contextFields`
* [Get agent](/api-reference/agents/get-agent) reads the mappings back