Variables and context

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

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 for the editing controls and GHL resources for calendars, tags and pipelines.

​

Business knowledge or a variable?

A durable explanation such as your service area belongs in business knowledge. A fact that differs for each lead belongs in contact context. For a master campaign, check what stays local before making one location’s information part of a shared script.

​

In the API

• Update agent sets contextFields
• Get agent reads the mappings back