Timezone - OurAiCalling

Every assistant carries a timezone — an IANA identifier such as Europe/Berlin or America/New_York, picked from a dropdown in the assistant settings. It defines what “now” means for the assistant, so “tomorrow at 3 pm” resolves to the caller’s local tomorrow, not UTC. The default is Europe/Berlin.

What the timezone affects

Consumer	Effect
`get_current_time` system tool	The always-on system tool returns the current date and time localized to this timezone — used whenever the model resolves relative dates (“next Tuesday”, “in two hours”) or books appointments.
Time system variables	`{{time}}`, `{{date}}`, `{{datetime}}`, and `{{weekday}}` (see Variables) are rendered in this timezone at call start.
Business-hours tool	The `check_business_hours` built-in tool evaluates its weekly schedule in this timezone — “open” always means open locally.

Campaign override

Outbound campaigns have their own timezone (used for calling windows). On a campaign call it wins over the assistant’s timezone for that call:

effective timezone = campaign timezone (meta.timezone) ?? assistant timezone

So one assistant can serve campaigns in different regions and still tell each lead the correct local time. Calls without a campaign (inbound, single outbound calls, web) always use the assistant’s timezone.

The timezone changes what the assistant says and checks about time — it does not shift call scheduling itself. Campaign calling windows are governed by the campaign’s own timezone either way.

Setting it via API

timezone is a regular assistant field — set it in the editor, via PATCH /api/v1/assistants/{id}, or with the MCP update_assistant tool:

curl -X PATCH https://app.famulor.de/api/v1/assistants/{id} \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "timezone": "Europe/Vienna" }'