The moment sales cross one time zone, managers start dialing blind: the card has a phone number, but not the hour on the other end. A 9 am call from London reaches Los Angeles at 1 am; teams selling across a large country hit the same wall between their own coasts. Bitrix24 (Alaio) has no native "client's local time", so people compute it in their heads — by area code, from memory, by guess. A Market field type closes the gap: the client's local time appears right in the CRM card and tells you at a glance whether calling now is a good idea.
Does Bitrix24 show the client's time?
No. In Bitrix24 the time zone is an employee property: each user picks a zone in their profile, and the portal recalculates the calendar, notifications and working day around it. CRM records have no such property — a lead, deal, contact or company does not know where the person lives. The address in the card stays a string the platform never turns into a time zone, and automation rules and triggers cannot see the client's time either. Teams that take zones seriously end up with a manual "region" field filled from memory — it goes stale faster than it helps.
How do you show the client's local time in the CRM card?
Applications can register their own field types on the portal via the REST API — the same mechanism behind the formula field or the countdown to a date. The Roboteka client local time field is such a type: attach it to a lead, deal, contact or company, and the card shows the client's clock. There is nothing to fill in and nothing to store: the time zone is derived from the phone number already in the record, and the field renders the live local time, the difference from yours ("+7" or "−3:30") and a colour-coded status — working hours, off hours or night. Hovering adds the region, the carrier and the difference in words: "7 h ahead of you". In effect it is a formula field that computes time instead of margin; the wider mechanics of third-party field types are covered in the custom field types guide, and the full set lives in the field types catalog.
How does the field determine the time zone from a phone number?
Offline, from telephone numbering data — the number never goes to third-party services. Landline numbers carry the geography of their area code. Mobile numbers are harder in countries where mobile prefixes say nothing about geography: there the field checks number-range allocation data — records of which region each block of numbers was issued to. Everywhere else the international numbering plan answers directly. One honest caveat: the field judges the number, not the person — a client who moved across the country and kept their SIM card will still be shown by the number's registered home. If you need the country or zone inside a workflow rather than in the card, the Phone number country robot does the same lookup offline and returns it to the process.
What can you configure?
Four things, all in the field's settings, available to an administrator. The number source: the stock Phone field or a string field of your own. The client's working-day boundaries — 9:00–18:00 by default; the field compares them against the client's local time, not yours. Working days — Monday to Friday by default. And two switches for showing the region and the carrier directly in the card: both are off by default, the details stay in the tooltip, and the card answers a single question — is now a good time to call. Night is not a setting: 22:00–08:00 is always highlighted, whatever the schedule. The carrier comes with its own caveat: numbers ported between carriers are invisible to range registries, so the region is more reliable than the carrier.
How does client time fit into a calling routine?
The fastest win happens before the dial: the status in the card stops a midnight call earlier than an awkward conversation would. Next comes planning: eastern regions get called in your morning, western and overseas ones after lunch, and a "call back tomorrow" lands in the client's morning, not yours. In automation the field pairs with robots: a delay until the right moment holds an automated call or SMS until the client's working hours, telephony robots bring call history into the process, and normalizing phone numbers to one format is the hygiene without which zone detection trips over malformed entries.
Where to go from here
Attach the field to the entity your team dials most — usually the lead or the deal — and watch for a week how many calls move from "off hours" into "working hours". The field types catalog lists sibling indicators for the card, and the CRM fields guide covers keeping the card lean while you add them. And if the catalog is missing the field or robot you need — describe the task: Roboteka builds missing activities for free and ships them into the shared library.