Frequently asked questions about CallerPeek
Everything store owners ask before rolling it out: what happens to customer data, how number recognition works on the phone, how to manage employee phones, what happens to missed calls and what the PrestaShop module installation needs.
Data safety and GDPR
Does my customer data reach CallerPeek?
No. The phone app talks only to the module installed on your own server — the same one your PrestaShop store runs on. We keep no database of phone numbers, create no user accounts and never relay the lookups, so there is no place your customer data could end up in. The only connection outside your store is a once-a-day update check, in which the app sends nothing but its own version number. You can verify this yourself by inspecting the phone's network traffic — no address other than your own shop domain will show up.
Is caller identification from a shop database GDPR-compliant?
You remain the data controller — the data is not entrusted to us or to any third party, because it never leaves your server. Showing customer details to the employee who answers that customer's call falls under the controller's legitimate interest, namely customer service and order fulfilment. You are not creating a new data set either: you are using the one already in PrestaShop, only at the moment when it is useful. In your record of processing activities it is worth noting that customer contact data is displayed on the support team's mobile devices and that access is tied to named, individual phones. Our privacy policy covers the details.
Is the connection between the phone and the store encrypted?
Yes, and it cannot be turned off. The app accepts https:// addresses only — pairing it with an unencrypted address fails with an error, and the module rejects requests that arrive without SSL. The caller number and the returned customer data therefore travel through the same encrypted channel as the orders placed in your store.
Could someone steal my customer database if they got a device token?
The module defends itself on three levels. First, a per-IP request rate limit cuts off bulk querying. Second, a daily request limit per device (300 by default — a real phone never needs that many) means even a stolen token would reach a fraction of the database before it stops working. Third, the module panel shows a "Lookups today" column per phone, so unusual traffic stands out immediately and one click revokes the token. On top of that, the module only ever returns the customer matching one specific number — there is no way to list customers or browse the database.
Is the pairing QR code safe?
Yes. The QR code shown in the module panel contains no token, only a one-time code valid for 10 minutes, which the app exchanges for the real token over an encrypted connection. After that a photo of the screen is worthless, and each code works exactly once — a second attempt is refused. You can safely pair an employee's phone even if somebody glances at your screen.
What do I do when an employee leaves or loses the phone?
In the module panel you click "Revoke" next to that device. The phone loses access instantly — on the next call the app receives a 403 response, stops querying the store and shows a disconnected notice. The other phones keep working, with nothing to reinstall and no password to change. A new employee gets a separate device entry and a fresh QR code, so the call history stays readable.
Does the customer know I use CallerPeek?
There is no difference on the caller's side — the call goes through completely normally, with no announcements and no delay. You simply see data you already hold in your own store, at the moment it matters. From the customer's point of view, the only change is that they no longer have to spell out their order number.
How it works
How does caller recognition work?
When the phone starts ringing, the app reads the caller number and sends an encrypted HTTPS request to the module in your store. The module looks the customer up by phone number in the PrestaShop database — checking the phone field on the customer account and on the addresses — and returns a ready-made set of details: name, number and value of orders, the date of the last order and its status. The whole round trip takes a fraction of a second and usually finishes before the second ring, so the customer card is on screen before you decide whether to answer. The store decides what the card contains — the app is only a viewer for whatever the module returns.
What exactly do I see on screen during a call?
A popup with the customer card appears above every other app: the store name, the caller's name, highlighted figures (for example the number of orders and their total value), a few detail lines and a "Call back" button. You can pin the popup to the top or the bottom of the screen so it does not cover the system call window, and in automatic mode the app picks the opposite side by itself. In parallel a notification is created and stays in the shade as history — useful when you never got to look at the popup.
What happens when someone outside the store database calls?
The app shows a discreet "Unknown number" notification and records an entry in the local history, but does not open the large customer card — it does not grab your attention when there is nothing to show. That is deliberate: in a store where half the calls come from couriers and sales reps, an aggressive full-screen window quickly becomes a nuisance. The history entry remains, so you can check later who called and call back with one tap.
How does the store know a call was missed?
The app can tell whether the ring was followed by a conversation or the phone simply went back to idle, and it reports that back to the module. As a result your store panel gets a "To call back" list of numbers that rang and were never handled, together with the customer details and the time of the call. This is usually the most profitable part of the rollout: a single recovered order from that list can pay back half the price of the module.
Will numbers stored in different formats still match?
Yes. The module normalises numbers before comparing: it strips spaces, dashes and brackets, reduces 0048, +48 and 48 to a common form and compares the endings of the numbers. A customer stored as "601 234 567" is therefore recognised when they call from "+48601234567". In the module settings you set a default country prefix — taken from the shop configuration by default — which is prepended to locally stored numbers.
My customers call from several countries. Is that a problem?
No. Foreign numbers usually arrive in full international format and are compared as they are, while the country prefix is only prepended to numbers stored in local form. The app also passes its selected interface language with every request, so the module can return labels ("orders", "last order") in the language the employee actually speaks. Thirteen languages are supported.
Can I see which SIM the call came in on?
The app recognises incoming calls on both SIM cards, and in the settings you can restrict it to one of them. That is the usual setup when one card is a business line and the other private — CallerPeek then reacts only to the business number and never queries the store about private calls.
Phone, Android and permissions
What permissions does the Android app need?
Reading the phone state and the call log — without them Android does not hand over the caller number at all — displaying over other apps (the customer popup), notifications and internet access. Optionally it asks you to disable battery optimisation and to allow full-screen notifications, because without those some phones put the app to sleep and the card does not make it to the screen in time. The app never asks for contacts, SMS, location, microphone or files — and never will, because it has no use for them. The Settings screen lists every permission with its current state and a shortcut to the right system screen.
Does CallerPeek work while the phone is locked?
Yes, and it is one of the more important features — most calls land on a phone lying face up with a locked screen. The customer card appears above the lock screen without unlocking the phone; we use the same mechanism that voice-calling apps rely on. On Android 14 and newer this needs a one-time consent for "full-screen notifications", which the app requests on first launch, and you can switch the feature off in settings if you prefer the notification alone.
Which Android versions are supported?
Android 8.0 and newer, including Android 15 and 16. The app handles the differences between system versions — notification changes, background-launch restrictions and the newer rules for windows drawn over other apps — so there is nothing to configure by hand. We test it on stock Android, on Pixels and on the Xiaomi (HyperOS/MIUI), Samsung (One UI) and Huawei skins.
What should I do if notifications do not appear on calls?
Almost always the cause is the phone maker's aggressive battery saving, which puts background apps to sleep. The app has a Help screen with step-by-step instructions separately for Xiaomi/Redmi/POCO, Huawei/Honor and Samsung, plus shortcuts that open the relevant system settings. If that is not enough, turn on "Reliable mode" in Settings — the app then keeps a permanent background service with a minimal notification, which the system no longer suspends.
Does the app drain the battery or use much data?
No. Between calls the app does nothing — there is no polling loop, it is woken by the system ringing event. A single lookup is a few hundred bytes, so even several hundred calls a month amount to a fraction of a megabyte. With reliable mode on, a lightweight service runs in the background whose energy cost is negligible compared with the call itself.
Is the app available on Google Play?
Not for now — we distribute it as an APK file from the product page. The call-log permission requires a separate declaration and review process on Google Play, while distributing outside the store gives us full control over release timing and lets us ship a fix the same day. The app checks for a new version once a day and tells you about it with a notification; you can also check for updates manually from the menu.
Does it work on a tablet or a phone without a SIM card?
Caller recognition needs a phone with a SIM card, because it is the operating system that tells the app about an incoming call. On a device without telephony the app will start and let you browse the history, but there is nothing to listen for. If you handle calls through a VoIP system, write to us — the API contract is open and can be wired to a different source of events.
Rollout, requirements and licence
What are the technical requirements?
A store on PrestaShop 1.7.6 or 8.x with an SSL certificate (the module rejects unencrypted connections) and PHP 7.4–8.3. A phone with Android 8.0 or newer. You need no extra server, no third-party account and no telephone exchange — all the logic runs inside your own store, and the only new component is the app on the phone.
How long does installation take?
About fifteen minutes. You upload the module through the PrestaShop panel just like any other, open its configuration, add the first device and scan the QR code with the app. The app immediately runs a connection test and shows a green dot with your store name, so you know everything works before the first customer calls. There is no need to modify the store template, the database or the server configuration.
Does the module slow the store down?
No. The module adds nothing to the customer-facing pages — no scripts, no template changes, no extra queries on product pages. Only its own controller is called, and only at the moment the phone rings: a single query on an indexed phone-number field. Even with several hundred calls a day the load is not measurable.
How many employees can use one store?
As many as you like — there is no device limit and no per-seat fee. In the module panel you add a separate device for each person: each with its own token, its own QR code and its own entries in the call history. That way you can see who answered which call and which numbers are still waiting for a call-back. It is a meaningful difference from subscription CRM systems with caller ID, where every user is billed every month.
What does the licence look like and are there subscription fees?
The licence is a one-off purchase covering one store and an unlimited number of phones in it. There are no monthly fees and no lookup limits — once bought, the module is yours and works for as long as your store does. A year of updates and support is included; renewal is optional, and when it lapses the module keeps working, you only lose access to new versions.
Can I test it before buying?
Yes. The app has a "Test connection" button that runs the full round trip — the phone queries your store and the answer appears as a customer card and a history entry, exactly as it would on a real call. You can also simply call the paired phone from a number that exists in your store database. If you would like to see it working before deciding, write to us and we will arrange a demo.
Will there be a WooCommerce version?
Yes, the plugin is in preparation. The Android app will need no changes and no second purchase — it talks to any backend that implements our open API contract, so the same app will serve a WooCommerce store. Write to us if you would like a message when the plugin is ready.
I have my own warehouse system or ERP. Can it be connected?
Yes. The API contract is documented and open: your backend has to accept a request carrying a phone number and a token, and return a simple JSON response describing what the card should contain. In that setup the app is a universal viewer — it knows nothing about PrestaShop and simply renders what it receives. If you are planning such a rollout, write to us for the contract documentation.
How is CallerPeek different from apps like Truecaller?
Community caller-ID apps identify numbers from a huge shared database built out of their users' address books — they will tell you that "John K." is calling or that a number is often flagged as spam. CallerPeek has no shared database and does not care who the caller is to the world: it checks your own customer base only and shows what matters for a sale — how many orders they placed, for how much, when the last one was and what its status is. It also never uploads your address book anywhere, because it never reads it in the first place.
Your question is not here?
Write to us — we reply on business days and are happy to help you pick the right setup for your store.
info@callerpeek.comBuy CallerPeek — PrestaShop module with the Android app →