CRMConnect v3.6 – International Phone Number Formatting (Mindbody → HubSpot)

applies to crmconnect – mindbody < > hubspot version v3 6 and later audience crmconnect users (no builder access required) 1\ what this enhancement does starting with crmconnect v3 6 , your mindbody → hubspot sync can now automatically add the correct country calling code (e g +1, +44, +61) to phone numbers store phone numbers in hubspot in standard international format (e 164) so hubspot recognizes the number, the country, and marks it as valid use either the client’s country from mindbody, or a default country you define in crmconnect settings this is all handled inside the product; you don’t need to change your automations or write any code it’s an example of the “deep integration” logic that powers all apiant api apps 2\ why this matters before v3 6 mindbody stores phone numbers as local numbers (no +country code) crmconnect simply copied that number into hubspot hubspot often showed warnings like “wrong format” and could not reliably detect the client’s country use phone tools that rely on standardized numbers with v3 6 enabled crmconnect rebuilds the number with the correct +country code the same, correctly formatted number is written into hubspot phone number hubspot mobile phone number hubspot can now validate the number and recognize the country, which improves data quality and reporting calling / dialer behavior filtering and segmentation based on phone properties 3\ how crmconnect formats phone numbers when a mindbody client is created or updated and crmconnect syncs them to hubspot, the phone number is handled as follows check your setting if “add countrycode prefix to phone” = off → crmconnect sends the raw mindbody phone (no changes) if on → crmconnect will build a full international number if “add countrycode prefix to phone” is on crmconnect will look at the client’s country in their mindbody address if the client has a country convert that to the proper 2‑letter country code (e g “united states” → us) rebuild the phone number in e 164 format , e g 3105551234 → +13105551234 if the client has no country in mindbody use your default iso countrycode from crmconnect settings (e g us, gb, au) to rebuild the number save and send that international number to hubspot hubspot result after the sync, in hubspot you’ll see hubspot should now show the phone number as valid , and the country will be recognized automatically phone = +\<country code> \<number> mobile phone = same e 164 formatted value behind the scenes, crmconnect uses the same reusable “api app” patterns that power other advanced features like next‑appointment logic and multi‑location sync 4\ new settings in v3 6 you control this behavior from the crmconnect settings screen go to your crmconnect (mindbody → hubspot) configuration open the hubspot settings section you’ll see two new settings 4 1 add countrycode prefix to phone type checkbox / on–off toggle what it does on – crmconnect will automatically add the correct country calling code based on mindbody or your default store phone numbers in e 164 format in hubspot off – crmconnect will leave the phone number exactly as it appears in mindbody send that local number directly to hubspot recommended turn this on unless you have a strong reason to keep purely local numbers in hubspot 4 2 iso countrycode type text field example values us, gb, ca, au, nz, etc what it does used as a fallback country when the mindbody client has no country on their address crmconnect uses this default to determine which country code to add you can change this at any time to match the main country where you operate 5\ typical scenarios scenario a – client in the united states with country set in mindbody mindbody mobile phone 3105551234 country united states settings add countrycode prefix to phone on iso countrycode us (default) result in hubspot phone / mobile phone +13105551234 hubspot displays valid , country recognized as united states scenario b – client in the uk with country set in mindbody mindbody mobile phone 07123 456789 country united kingdom settings add countrycode prefix to phone on iso countrycode us result in hubspot phone / mobile phone +447123456789 hubspot displays valid , country recognized as united kingdom (mindbody’s actual country overrides your default ) scenario c – client with no country in mindbody mindbody mobile phone 0400 000 000 country (empty) settings add countrycode prefix to phone on iso countrycode au result in hubspot phone / mobile phone +61400000000 hubspot displays valid , country recognized as australia scenario d – you prefer local numbers only mindbody mobile phone 3105551234 settings add countrycode prefix to phone off result in hubspot phone / mobile phone 3105551234 hubspot uses its own validation (may show “wrong format”/unrecognized country) 6\ how to enable and configure the feature (step‑by‑step) confirm you’re on v3 6 or later this feature is part of the crmconnect (mindbody → hubspot) v3 6 release if you’re not sure which version you’re on, contact apiant or your implementation partner/support open crmconnect settings log into your crmconnect portal go to your mindbody < > hubspot crmconnect product open its settings locate the hubspot settings section find the section labeled hubspot settings (or similar) turn on international formatting set add countrycode prefix to phone to on click save set your default iso country in iso countrycode , enter your main country code (e g us, gb, ca, au) click save again if you changed it test with a client record in mindbody , open a test client make sure they have a mobile phone and a country on their address (to test the preferred path) save the client to trigger an update in hubspot , open the matching contact confirm that phone and mobile phone show the international number (+\<country code> ) and are marked as valid 7\ faqs q1 does this change existing phone numbers already in hubspot? not automatically the new behavior applies when a contact is created in hubspot by crmconnect, or a contact is updated due to a new event from mindbody (e g profile update, visit, purchase, etc , depending on your crmconnect configuration) if you want to normalize all existing numbers, you can trigger updates from mindbody (e g via a resync process), or contact apiant / your implementation partner to discuss bulk update options q2 which hubspot fields are affected? by default, crmconnect v3 6 writes the formatted number to phone mobile phone if you have custom mappings or custom fields, your implementation may vary—ask your integrator or apiant support q3 what if our business works with multiple countries? the feature is designed for that if a client’s country is set in mindbody, that country will be used to format the phone number—regardless of your default iso countrycode the iso countrycode setting only applies when mindbody has no country for that client this makes crmconnect flexible enough for studios/brands that serve multiple countries from the same hubspot portal, while still giving you a sensible default for incomplete mindbody data q4 what happens if my iso countrycode value is invalid? if you enter a value that is not a valid iso 2‑letter code, phone formatting may fail or not behave as expected use standard iso country codes (e g us, gb, ca, de, fr) if you’re unsure, contact apiant support or your partner to confirm the correct setting q5 do i need to change anything in my automations? no the enhancement is built directly into the crmconnect product logic as part of v3 6 once your instance has been upgraded and you enable the setting, it will automatically apply to the relevant sync operations this is the same “productized” approach used across all crmconnect api apps 8\ troubleshooting checklist if numbers are not appearing as expected in hubspot, check is “add countrycode prefix to phone” turned on? if not, turn it on, save, and run a new test does the mindbody client have a country set? if yes, ensure it’s correct and spelled properly (e g “united states”) if no, verify that your iso countrycode default matches the country you expect is the mobile phone valid in mindbody? remove non‑numeric characters that might cause issues (extensions, text notes, etc ) has the contact actually been updated since v3 6 was enabled? make a small change in mindbody (e g add a note) and save to trigger a fresh sync still stuck? contact apiant support with example mindbody client name their mindbody id the hubspot contact url a screenshot of your crmconnect hubspot settings if you’d like help reviewing your configuration or planning a data clean‑up using this new feature, your apiant partner or support team can guide you through best practices for your specific account setup