Indoor Monitor vs Smartphone Intercom: Does Every Installation Still Need a Screen?
Essential Security Supplies
Not every intercom installation needs an indoor monitor. Smartphone answering may suit a customer who accepts its connection and account dependencies. A fixed monitor remains worth assessing where people need a predictable answering point, several occupants share responsibility or the site requires a tested local call path.
For New Zealand installers, the decision is about who must answer, where they will be and what happens when a phone or connection is unavailable. Compare the complete call and door-release architecture before removing a screen from a quotation. A mobile app and an indoor monitor can complement one another, but neither guarantees that the other will provide a working fallback.
Separate the answering device from the system architecture
An indoor monitor is an answering endpoint. A smartphone app is another answering endpoint, usually with additional dependencies involving the phone, account and remote service. The outdoor door station, network, power equipment and release interface still need to be specified in either case.
Draw the call path from the entrance to the person answering. Identify whether a call stays on the local network, uses a local SIP service or passes through a cloud platform. Then draw the release-command path separately. A picture appearing on a screen does not prove that the correct door output will operate.
The first decision is whether people need a fixed answering point, mobile answering or both. For the broader distinction between entry-system types, read the video doorbell versus video intercom guide. Do not carry a general claim that intercoms work without internet into every IP installation: the actual topology and provisioning determine that behaviour.
When a fixed indoor monitor adds practical value
A monitor creates a known answering location. In a household, visitors do not depend exclusively on the account holder being available with a charged phone. At a reception desk, staff can see the answering device and include it in the daily opening checks. In a shared building, the location and responsibility can be documented during handover.
The Akuvox S562W white indoor monitor is a listed seven-inch Linux monitor option. The S562 family includes different configurations, so confirm the exact suffix and required network connection rather than treating every S562 as identical. Akuvox S562 product information provides the manufacturer starting point; confirm the supplied unit and current manual before ordering.

Screen position matters as much as screen size. Survey the proposed height, glare, background noise and access for the intended users. A wall-mounted screen in a closed office is a poor answering point for a busy front counter. Where several people need to answer, define whether additional endpoints ring together or in sequence.
A monitor is not automatically independent of internet or cloud services. Its usefulness during an outage depends on the configured local calling method and the continued operation of every necessary local component. Specify that requirement explicitly and prove it during commissioning.
When smartphone answering can suit the customer
Mobile answering can be valuable when the responsible person moves around the site or needs to respond away from the premises. It may also avoid adding a fixed screen in a location where nobody will reliably hear it. The benefit depends on the user's willingness to manage an app, keep the account active and maintain a suitable phone connection.
Akuvox's SmartPlus single-house setup guidance describes resident accounts, device assignment and app use. Its troubleshooting section identifies network conditions, registration and app permissions as possible causes of missed calls. Use that as evidence to test the whole service path, not a promise that an app will always ring.
Before recommending app-only answering, ask the customer to demonstrate the intended phones. Test normal locked-screen use, notification settings and the transition between site Wi-Fi and mobile data. Record which users are authorised to release which entrance. Do not leave all staff using one personal account simply because it worked during a demonstration.
Confirm current service entitlements, account quantities, provisioning responsibilities and any continuing charges through the supplier. Do not assume that buying a door station includes every remote service indefinitely. Keep commercial terms in the project quotation rather than publishing unverified prices or plan comparisons.
Compare monitor, smartphone and hybrid answering
| Decision | Indoor monitor | Smartphone app | Hybrid design |
|---|---|---|---|
| Where people answer | Known fixed location | Where the authorised phone user has service | Fixed location plus supported mobile endpoints |
| Shared responsibility | Visible shared answering point | Requires suitable accounts and permissions | Requires an agreed ring and escalation plan |
| Internet outage | Local calling must be specifically verified | Remote service path may be interrupted | Only useful if the local path remains operational |
| User support | Device location and operation | Phone settings, accounts and app updates | Both sets of support tasks |
| Handover test | Call, audio, video and correct release | The same, using actual customer phones | Both paths and their failure behaviours |
Choose app-only where the customer knowingly accepts the tested dependencies and the intended users can operate it. Assess a monitor where a shared local answering point is important. Assess both where fixed and remote answering serve different operational needs. The hybrid option adds flexibility only when the configured call behaviour is understood.
Hybrid calling must be commissioned, not assumed
Akuvox documents both local and SmartPlus group-calling arrangements. Its group-call instructions distinguish device families, firmware examples and cloud configuration conditions. They also describe how refusing a call can affect other targets in supported configurations. A generic statement that every screen and phone will ring together is therefore insufficient.
Write a short call schedule before programming. For example: call the reception monitor and authorised mobile endpoints during staffed hours; use a separately agreed after-hours destination when reception is closed. This is a proposed project requirement, not a claim that every product can perform that schedule.
Test one endpoint accepting, declining and ignoring the call. Check what the other endpoints do and when the entrance returns to idle. Record the result for the actual firmware, application version and configured service. A successful test on the installer's phone does not replace tests on the customer's devices.

The Akuvox E12S/S562 IP intercom kit provides a useful starting point for a specified door station and monitor package. Confirm included parts, network equipment, power arrangements and any app provisioning separately. For wider entrance planning, the villa and gate intercom kit guide covers another part of the selection process.
What must work during a connection or power failure?
Describe failure tests in plain language. If the building loses its internet connection but the local network remains powered, should the entrance still call the indoor monitor? If a phone has no usable connection, who else answers? If a network switch loses power, which parts of the system stop working?
For a supported local IP calling design, the local door station, monitor, switching and power arrangement must remain operational. Any required local server or registration service must also be considered. Backup power should be sized from verified loads and the intended operating period; the presence of a UPS alone does not establish a runtime.
Do not treat visitor answering or an app release button as a substitute for the project's separate door-safety, emergency-egress or gate-safety design. Confirm those requirements with the responsible competent parties. This guide does not specify a compliant locking circuit or emergency release arrangement.
Accounts, privacy and change of occupants
Include an account lifecycle in the handover. Record the administrator, authorised users and the process for a lost phone, departing employee or tenant change. Give each person only the access they need and confirm that removing their account prevents the intended remote actions.
Identify what the selected service stores, who can access it and where current privacy information is available. Agree how visitor images and call records are handled before deployment. Do not promise local-only storage, a particular hosting region or a retention period without service-specific evidence.

A different monitor, such as the listed Akuvox S567W, should be assessed against a real user requirement rather than screen size alone. Confirm current support, exact features and compatibility with the proposed entrance devices before substituting it into a design.
Example: a New Zealand workshop with a shared reception
Consider a small workshop where the reception desk is staffed during business hours and the owner moves between the office and work area. A fixed monitor could give reception staff a shared answering point, while supported smartphone answering could let the owner respond away from the desk. This is an illustrative brief, not a tested installation or a guarantee of compatibility.
Record who answers during lunch breaks and after closing, which entrance they can release and what should happen if nobody responds. Before accepting the design, test the actual customer phones on site Wi-Fi and mobile data. Separately disconnect the internet connection while keeping the local network powered to establish whether the agreed local monitor call still works. Record the observed result and explain any limitations at handover.
Installer acceptance checklist
- List entrances, users, answering locations and required operating hours.
- Record exact hardware, firmware, app versions and service configuration.
- Test audio, video, ring behaviour and release at every intended endpoint.
- Test rejected, unanswered and simultaneous calls where supported.
- Prove the agreed behaviour during internet loss and other planned fault tests.
- Check customer phone permissions using their normal settings.
- Confirm account removal, administrator ownership and support responsibility.
- Provide simple user instructions and record limitations accepted by the customer.
Frequently asked questions
Can I use an intercom without an indoor monitor?
Potentially, if the exact door station, service and configuration support the intended smartphone answering arrangement. Confirm the account requirements and test the customer's phones before accepting an app-only design.
Will an indoor monitor work when the internet is down?
It may in a correctly configured local system with the necessary equipment powered and operational. Cloud-dependent calling is different. Prove the required behaviour by testing the agreed outage scenario.
Can a monitor and several phones ring together?
Supported systems can offer group calling, but endpoint limits, configuration and refusal behaviour vary. Check the exact manufacturer instructions and demonstrate the selected arrangement.
Is smartphone answering suitable for a shared reception?
It can be, if accounts, staff responsibility and availability are well managed. A fixed monitor may provide a simpler shared answering location. Decide from the operating workflow rather than a preference for one device type.
Specify the right answering arrangement
Explore the Akuvox indoor monitor range and the wider intercom collection. Contact Essential Security Supplies for technical assistance or a trade quotation with the entrance count, existing cabling, required answering locations and outage expectations so the proposed system can be checked as a complete design.