Short answer: There isn’t a built‑in system variable for a specific timezone. ElevenLabs only exposes system__time_utc (ISO UTC). (elevenlabs.io)
Ways to give the agent Europe/Copenhagen time:
Pass it as a dynamic variable you compute your side at session start (or via the widget), then reference it in prompts/messages with {{your_var_name}}. Dynamic variables are designed for this and can be injected at conversation start or via the widget’s dynamic-variables attribute. (elevenlabs.io)
Provide a webhook “time” tool that returns Copenhagen time and map its response field into a dynamic variable using tool assignments. The agent can call this whenever needed so it stays current. (help.elevenlabs.io, elevenlabs.io)
Alternatively, inject the current time directly into the system prompt using Overrides (enable overrides in the agent’s Security tab first). Note: Overrides replace the prompt at start; ElevenLabs recommends using Dynamic Variables for real‑time data. (elevenlabs.io)
Helpful details:
system__time_utc is available automatically; system variables are set once in system prompts and refresh at tool execution time inside tools. Use a tool if you need the time to update mid‑conversation. (elevenlabs.io)
ElevenLabs’ own guide notes agents don’t know the current time by default and suggests either a time‑retrieval tool or injecting time via overrides—both approaches above. (elevenlabs.io)
If you’d like, tell me whether you’re starting the conversation via SDK or the web widget, and I can point to the exact parameter/field to set for the dynamic variable. (elevenlabs.io)
boreal bone
ashen fulcrum