Servis.ai simplifies contact management by offering multiple phone number formatting options aligned with regional and international standards. These formats ensure consistency, improve data accuracy, and enhance system integrations.
Servis.ai also includes Smart Sharing, a feature that allows users to link phone calls to multiple records across different apps. This ensures a complete communication history and improves visibility across related records.
Phone Number Format
You can choose how phone numbers are displayed to ensure consistency across the system. Supported formats include:
E.164 Format
E.164 is the globally recognized format recommended by the International Telecommunication Union (ITU). It includes:
- Country code
- National destination code
- Subscriber number
Example (U.S.):
+1 555 1234567
+1 = country code, 555 = area code, 1234567 = subscriber number
National Format
National formats follow each country’s local standards, typically including area code and subscriber number.
Example (U.S.):
(555) 123-4567
International Format
This format is similar to E.164 but does not include the plus sign (+). It consists of:
- Country code
- National destination code (if applicable)
- Subscriber number
Example (U.S.):
1 555 1234567
Enable Smart Sharing
Smart Sharing allows users to associate calls with multiple records across all apps using the Share field. All selected records will include the activity in their Activity Timeline.
By default, the Share field suggests a related record based on the active Detail Page.
For example, when logging a call to a contact, the system may automatically suggest the related account if the Account Detail Page is active.
Accounts Use Case
When using Smart Sharing in an account, you can select contacts either from the information panel or from related records. This ensures the activity appears on both the Account and Contact records.
The Share field follows a structured format: App Name – Record Name. Example: “Account – Servis.ai”
You can also manually add additional records using the Share field to create a more comprehensive activity history across related records.