Phone numbers are the dirtiest field in almost every CRM: one lead arrives as +1 415 555 0123, the next as (415) 555-0123, the third as 4155550123 with a note "WhatsApp only". Bitrix24 (Alaio) stores whatever the form or the manager typed — and every mismatch quietly breaks something downstream: duplicate detection, click-to-call, messenger matching, SMS delivery. This guide covers the format worth standardizing on and how to enforce it automatically, for new records and for the thousands already in the base.
Why do phone formats matter in a CRM?
Three mechanisms depend on numbers being comparable. Deduplication matches leads and contacts by phone — "+1 415 555 0123" and "(415) 555-0123" are the same person to a human and two different strings to a naive comparison, which is how duplicate cards multiply (the wider problem is covered in the duplicates guide). Telephony matches an incoming call to a card by number, and a mismatched format means the call pops up unrecognized. Messenger and SMS integrations refuse or misroute numbers with stray characters. A single canonical format fixes all three at once.
Which format should you standardize on?
Store numbers in the international E.164 form — a plus sign, country code and digits, nothing else: +14155550123. It is what telephony providers, messenger APIs and SMS gateways expect, it sorts and compares cleanly, and any national "pretty" format can be derived from it for display. The mistake to avoid is the reverse: storing a locally formatted string and hoping each integration will normalize it on its own — none of them promise to.
How do I format numbers automatically on entry?
Put an automation rule on lead and contact creation. Format phone number: custom prefix strips the punctuation a human typed, keeps the digits and returns the number with the country prefix you configure — so every record enters the base already canonical, whatever the form submitted. Set the prefix once to your market's country code and the robot handles both local-style and already-international input. Add the same rule on field update, not just creation — numbers get edited by hand later, and the second rule keeps them from drifting back into chaos.
How do I clean up numbers already in the database?
New-record rules do nothing for the existing base, and editing ten thousand cards by hand is not a plan. Format entity phone numbers: custom prefix normalizes all phone numbers of the current record — every value in the multifield, not just the first — in one robot call. Wrap it in a workflow and run that workflow over the whole base with a mass launch; the same pass fits naturally into a broader CRM data cleanup. After the bulk pass, the entry rules above keep the base clean going forward.
How do I get the country from a phone number?
Once numbers are in E.164, the country code becomes data you can branch on. Country by phone number resolves the country right in the workflow, and routing follows: assign the German-speaking manager, switch the message template language, apply the correct tax logic. Combined with Find contact by phone or email, a normalized number also becomes a reliable key for matching inquiries to existing customers — search by phone only works when both sides of the comparison use the same format.
Where to go from here
Do the bulk cleanup first, then switch on the entry rules — in that order, or new clean records keep mixing with old dirty ones and the win never becomes visible. The automation examples collection shows neighboring recipes for validation and typo fixing, and the calls guide covers what telephony data you can pull into workflows once numbers finally match.