The point of a mobile app is not that it exists. Nearly every provider has one. The point is whether a business call on it behaves like a real call.
Native call handling
Our app uses the phone’s own call interface. Incoming business calls ring on the lock screen and appear in the recent-calls list like any other call. You answer them the way you answer everything else, rather than hunting for a notification and hoping the app is awake.
That sounds like a small detail until you have used an app that does not do it, and watched people miss calls for a fortnight before admitting it.
One extension, everywhere
The same extension runs on the desk phone, in the browser and on the mobile. One voicemail box. One number on the outbound caller ID, so a salesperson calling from a car park does not show a personal mobile number and does not have to give one out.
What is in it
Company directory with presence, transfers to any extension, hold and park, call history synced with the rest of the system, voicemail, and push notifications that arrive when the app is closed.
Common questions
Does it drain the battery?
It uses push rather than holding a connection open, so it sits idle until a call arrives.
Do staff need a company phone?
No. It runs on personal devices without exposing personal numbers, which is usually the reason people want it.
Does it work over mobile data?
Yes, and it hands over between wifi and mobile data without dropping the call. If someone regularly works somewhere with poor coverage, an extension can roll to their mobile number instead.
Anything to watch out for?
Yes, and we would rather say it plainly: a phone that moves around has an emergency service address that does not. Users away from their registered address must keep their location current — see our VoIP Service Terms.