Organization Preferences
Set your organization's timezone so agents get dates right, and a default number for test calls.
Settings → Preferences holds two small settings that apply across your whole organization. The timezone in particular is worth setting before you go live.
Timezone
Your agents know what day it is. Whenever a caller says "tomorrow", "next Tuesday", or "end of the month", the agent resolves it against a real calendar date — and this setting decides which clock that calendar runs on.
Leave it unset and Talkr grounds dates in UTC. For a business in India, that's five and a half hours behind your actual day; for one on the US West Coast, it can put the agent a whole day ahead late in the evening. An agent booking "tomorrow" from the wrong day books the wrong day, and nothing about the call sounds wrong while it happens.
Set it to the timezone your business operates in — the same one you'd use to read your own calendar. If Talkr doesn't recognise the value, it falls back to UTC rather than failing the call, so a typo shows up as dates being consistently off rather than as an error.
This affects the agent's understanding of dates during a call. It does not change how timestamps are displayed in Reports or Agents & Runs.
Test Phone Number
The number test calls go to by default, so you don't retype it every time you try a change.
It's only a default — anywhere you place a test call you can dial a different number instead. Nothing outbound to your customers uses it: campaigns and API-triggered calls always take their destination from the campaign or the request.
Store it in full international format (+14155550123), the same as everywhere else in Talkr.
Related settings
Preferences is deliberately small. The rest of Settings covers:
Notifications
Talkr tells you when something needs attention — a campaign that stopped itself, a connector that lost access, credits running down, or a call your QA rules flagged.
Security Settings
Change your password and sign out other devices, lock access to known networks with an IP allowlist, connect your identity provider, and set the usage alerts that warn you before a cap bites.