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

# Variables

> Learn how to use variables in Famulor to retrieve information during a call

Learn how to use variables in Famulor to retrieve information during a call.

## What is a Variable?

A variable is a data value that you can store and reuse during a call. Variables allow you to capture, for example, the caller’s name, phone number, or AI-generated values.

## System Variables

System values that fill in automatically at call time. Use **double braces** — `{{variable_name}}` — in your system prompt, and in mid-call tool URLs, header values, or static fields.

### Available system variables

These fill in automatically at call time. Click to copy in the app, then paste where you need the value. Some are empty on web/chat.

<ResponseField name="{{customer_phone}}" type="string">
  The other party's phone number (caller for inbound, callee for outbound). Empty on web/chat.
</ResponseField>

<ResponseField name="{{assistant_phone}}" type="string">
  The assistant's own phone number. Empty if it has none.
</ResponseField>

<ResponseField name="{{assistant_id}}" type="string">
  The assistant's unique ID.
</ResponseField>

<ResponseField name="{{assistant_name}}" type="string">
  The assistant's name.
</ResponseField>

<ResponseField name="{{current_date}}" type="string">
  Current date in the assistant timezone (e.g. `2026-06-15`).
</ResponseField>

<ResponseField name="{{current_time}}" type="string">
  Current time in the assistant timezone (e.g. `14:30`).
</ResponseField>

### Usage in system prompts

Reference system variables with double braces in your system prompt:

```
Today is {{current_date}}. The caller's number is {{customer_phone}}.
You are {{assistant_name}}.
```

### Usage in mid-call tools

In a custom HTTP action or MCP tool setup, paste system variables into:

* The request **URL**
* A **header** value
* A **static field** in the request body

They are replaced with live values when the assistant runs the action during a call.

<Note>
  System variables use double braces (`{{customer_phone}}`). Custom call variables below use single braces (`{customer_name}`).
</Note>

## Call Variables

Call Variables are custom variables that you define before a call and pass to the assistant. They enable you to conduct personalized conversations and provide context-specific information.

### Variable Configuration

#### Variable Definition

Create Call Variables to pass information to your assistant before the call starts.

**Setup process:**

1. Define variable names and default values
2. Pass values when creating calls/leads or importing clients
3. Variables are immediately available in prompts and during the call
4. Use them for personalization and context

**Configuration:**

* **Variable Name**: The identifier (e.g., `customer_name`)
* **Default Value**: Used if no value is passed (e.g., "John")

### Variable Usage

#### Usage in System Prompts

How to use Call Variables in your assistant:

* Reference variables using the syntax `{variable_name}`
* Personalize conversations dynamically
* Provide context-specific information

**Examples:**

* **`{customer_name}`** for personalization ("Hello {customer_name}")
* **`{email}`** for calendar integrations
* **`{account_type}`** for tailored responses
* **`{company}`** for business context

### Data Sources

There are various ways to populate Call Variables:

#### Manual Entry

* When creating individual calls
* Via campaign lead creation

#### Import Methods

* **CSV Import**: Import leads with variable columns
* **API Integration**: Direct integration with client data
* **Direct CRM Synchronization**: Connect to your CRM system

#### Automation Platform Integrations

* **GoHighLevel (GHL)**: Automatically fetch contact data and custom fields
* **Google Sheets**: Import leads with variables from spreadsheet columns
* **250+ popular tools and platforms**: Use our no-code platform for integrations
* **Webhooks**: Custom integrations via webhooks for bespoke use cases

#### Platform Integration

* Automatically populated from client profiles
* Connected to existing customer databases
* No-code automation workflows

## Best Practices

1. **Use meaningful variable names**: Use clear names like `customer_name` instead of `name1`
2. **Define default values**: Ensure important variables have default values
3. **Document your variables**: Keep track of which variables are available and what they are used for
4. **Test your variables**: Verify variables are correctly passed and used

## Example Usage

### System Prompt Example

```
You are a sales assistant for {company}.

Hello {customer_name}, thank you for your interest in our services.

Based on your account type ({account_type}), I can offer you the following options...
```

### Call Creation with Variables

When creating a call, you can pass variables as follows:

```json theme={null}
{
  "assistant_id": "123",
  "phone_number": "+49123456789",
  "variables": {
    "customer_name": "Max Mustermann",
    "company": "Muster GmbH",
    "account_type": "Premium",
    "email": "max@muster.de"
  }
}
```

***

## Related Topics

<CardGroup cols={2}>
  <Card title="System Prompts" icon="brain" href="/en/ai-assistants/system-prompt">
    Learn how to use variables in your system prompts
  </Card>

  <Card title="Tools & Functions" icon="screwdriver-wrench" href="/en/ai-assistants/tools-and-functions">
    Enhance your assistant's capabilities with tools
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Automation Platform" icon="wand-magic-sparkles" href="/en/automation-platform/introduction">
    Use the no-code platform for advanced integrations
  </Card>

  <Card title="API Reference" icon="code" href="/en/api-reference/introduction">
    Learn more about API integration
  </Card>
</CardGroup>

<Tip>
  Call Variables are essential for personalizing AI conversations. They allow the AI to use specific customer information during the call, making interactions more relevant and effective.
</Tip>

<Tip>
  Related pages: [What Is AI Assistant](/en/ai-assistants/what-is-ai-assistant) and [Prompt And Tools](/en/ai-assistants/prompt-and-tools), and [Assistant Best Practices](/en/ai-assistants/assistant-best-practices).
</Tip>

<Tip>
  Need a whole toolset instead of building HTTP actions one by one? Connect an external **MCP server** — tools are discovered automatically. See [MCP Servers](/en/platform/mcp-servers).
</Tip>