Provectus Secure Contacts

Caller ID Works Without a Phone Contact Entry

Open the app after your IT department deploys it through Intune. The first thing that happens is not a contact list. It is a login screen that requires a Microsoft Entra ID account. This is not an app you just download and open. It is an enterprise tool that expects your company's Microsoft setup to be in place already. The login uses Microsoft Authentication Library, so you are signing in with your work credentials, not creating a new account inside the app itself.

Once logged in, the app pulls contacts from every source your company has connected. Outlook. Teams. The company address book. Whatever CRM system your sales team uses. These all show up in one list. But the real test comes when a call comes in. The caller ID feature does not need a phone contact to exist on your device. If a number belongs to someone in your Outlook directory, the app shows their name even when your phone's native contacts app has never heard of them. That is the core value here — business contacts live in the app, not in your personal address book.

The interface itself is clean. A search bar at the top. A list of contacts. Tabs for different source directories. It looks like a standard address book until you start using the features. Tap a contact and you get options to call directly, start a Teams chat, or see their Teams status. The out-of-office function shows who is on vacation. The organizational chart display shows who reports to whom. These are not features you find in a typical contacts app.

What Happens When You Add a Contact to Outlook

Here is where the original behavior emerges. Add a new contact in Outlook on your desktop. Within seconds, that contact appears in the Secure Contacts app. The caller ID system recognizes the number immediately, even before you have saved anything to your phone's native contacts. At the same time, the duplicate detection system scans across all connected sources to see if this person already exists somewhere else — maybe in the CRM with a different email, or in Teams with a different display name.

If the duplicate detection finds a match, it suggests merging the two entries. If it finds nothing, the new contact stays as a standalone entry from Outlook. The interesting part is the timing. The caller ID works instantly, but the duplicate detection runs a background check that can take a few seconds. So you might get a call from this new person, see their name through caller ID, answer the call, and only after hanging up does the app notify you that it found a duplicate in the CRM. That sequence — caller ID first, duplicate check second — is not documented anywhere on the Play Store page.

This creates a practical workflow for sales teams. A new lead comes in through Outlook. The salesperson sees the name on an incoming call before they have even opened the app to look at the contact details. They take the call. After the call, the app prompts them to merge the new contact with an existing CRM entry that has a different email address. The merger preserves both sets of information. The salesperson never had to manually type anything or search for duplicates.

The License Wall and What It Blocks

Here is the reality check. The app is free to download, but that gets you nowhere. A valid license is required for most key features. Without a license, the app runs in demo mode. Caller ID does not work. The duplicate detection does not work. The Teams integration does not work. You basically get a contact viewer that shows your directories but does not let you do anything useful with them.

The license is delivered through App Configuration Policies in Microsoft Intune. This means your IT department has to set it up. You cannot just buy a license and enter a code. The admin creates an AppConfig policy, adds the package ID de.provectus.securecontacts.droid as a custom app, and pushes the license key through that policy. If your company does not use Intune, you are out of luck — the documentation explicitly states that MDM management is required, with Intune preferred.

Some users have reported sync delays with external data sources. The mi9.com review notes occasional delays when pulling from CRM systems. The app protection policies for the Play Store version cannot yet be configured in Intune, according to the secure-contacts.com info page. That is a technical limitation that affects how the app behaves in corporate environments. The app works, but it requires a specific setup that not every company has in place.

The vCard and QR Code Exchange Flow

There is a vCard feature that generates a digital business card. The app pulls your contact data from the cloud and creates a VCF file. A QR code is generated automatically. Someone else scans that QR code with their phone, and your contact details go straight into their Secure Contacts app — or into any other app that reads vCards. The data transfers directly from the cloud, not from your device. This keeps your personal device storage clean and ensures the contact information is always current.

But here is the catch. The vCard contains whatever information your company has in the directory. If your Outlook profile has an old phone number, that is what goes into the vCard. Updating the vCard requires updating the source directory. The app does not let you edit your own contact details within the app and push those changes back to Outlook. You edit in Outlook, and the app reflects that change. This is a one-way sync for vCard data — from the source to the app, not the other way around.

The call blocking feature works through the system's call identification API. On Android, this requires enabling the app in the call blocking and identification settings. The iOS version uses Apple's CallKit. The activation process is manual — you have to go into settings and toggle SecContacts on. The app does not do this automatically. Users have to follow the onboarding guide step by step, which includes downloading Microsoft Authenticator alongside the Secure Contacts app.

The app is available on both Android and iOS, but the deployment methods differ. Android uses Managed Google Play through Intune. iOS uses Apple Volume Purchase Program. The app itself is a mobile-only solution. There is no desktop version. All contact data is retrieved directly from the customer's Azure tenant and protected according to Intune or MDM/MAM policies. No data flows out of the app, and there is no synchronization with other commercial platforms, messenger services, or rental cars. That is the entire point — keeping business contacts contained within the corporate ecosystem and away from personal apps like WhatsApp and Google.