Cloud phone systems: 999, power cuts and call recording

Understand where the phone system now lives

A hosted phone system runs some or all of its calling functions outside your premises. Voice over Internet Protocol, or VoIP, carries calls through a data connection. Staff may use desk handsets, computer software or mobile apps connected to that service.

The change does not remove local dependencies. A desk phone may need a powered network switch. A computer-based phone needs the computer, its audio equipment and a working connection. A mobile app depends on the handset and whichever data route it is using.

Draw up an equipment list in plain English. Start at the broadband termination point, then include the router, switches, wireless access equipment and devices used for calls. Ask the provider or IT support which parts it manages and which remain your responsibility.

That list helps with faults as well as purchasing. If calls fail but the internet works, the problem may be in the calling platform or configuration. If all internet services fail, start with the connection and local network. Staff need a clear fault route rather than being passed between suppliers.

Keep administrative access under business control. Record who can change routing, add users and retrieve recordings, and arrange an approved way for another authorised person to help when the usual administrator is unavailable.

Check emergency access and location

Ofcom's emergency-access rules require relevant calling providers to support emergency calls, including 999 and 112, and address caller-location information. Digital calling introduces practical complications when a number is used away from the office where it was first installed.

Ask the provider how location is registered, updated and used for your service. A fixed desk handset, a laptop taken home and a mobile app may need different instructions. Do not assume the number's area code identifies where the caller is physically located.

Train staff to state their location clearly in an emergency. Make sure the instructions are available where people work, including remote staff. Do not make unarranged test calls to emergency services; ask the provider for its approved verification procedure.

Keep emergency access separate from the ordinary reception call flow. A system can be excellent at transferring customer calls while still having an outdated location record or an unexplained limitation during an outage.

Plan for loss of power and connectivity

Ofcom's power-cut guidance includes a minimum one-hour emergency-access solution for relevant landline-dependent customers. That safety provision does not amount to a guarantee that an entire business phone system, booking platform and payment service will keep running.

An uninterruptible power supply, or UPS, provides battery-backed electricity. Ask what it needs to support in your setup. Powering a handset alone achieves little if the network switch, router or fibre termination equipment has stopped.

Request a realistic assessment using the devices actually connected. Batteries age and the runtime depends on load. Put testing and replacement responsibility into the maintenance record instead of assuming a green light proves the arrangement remains adequate indefinitely.

A separate data route can address a connection failure. For example, the provider may propose mobile failover or a calling arrangement that directs incoming calls elsewhere. Ask which faults trigger it and what happens to calls already in progress.

Test the agreed fallback through normal business tasks. Can reception answer, identify the caller and transfer the call? Can remote staff access the information they need? Does the main number still present appropriately on outgoing calls? The answer depends on the system design and should be demonstrated, not inferred from the feature name.

Decide why calls are being recorded

A recording can contain personal information about callers and staff. The fact that a cloud service offers recording does not establish a lawful reason for the business to enable it. Start by defining the purpose: resolving order disputes, meeting a particular obligation or another identified business need.

The Information Commissioner's Office explains that you need an appropriate lawful basis before processing personal information and must document it. Consent is not the only possible basis, but neither is legitimate interests an automatic permission to record everything. The choice depends on the purpose and circumstances.

Tell callers what happens to their information through an appropriate notice and accessible privacy information. Also explain the arrangement to staff. If recordings can include sensitive health information or other special-category data, additional conditions may be needed.

Set the retention period against the purpose. Ask how automatic deletion works and whether downloaded copies, voicemail attachments and backups follow the same rules. Retaining recordings indefinitely because storage is available is not a retention policy.

Limit access to people who need it. A supervisor resolving a complaint may need a particular recording; that does not mean every employee needs access to the complete archive. Keep a record of administrative access and establish how permissions are removed when someone leaves.

Treat transcription as another use of the information

Automatic transcription creates a searchable text version of a conversation. Summaries and quality-scoring features can create further records. These may make the system more useful, but they also change where personal information appears and how easily it can be found or shared.

Ask the provider where audio and text are stored, which organisations process them and what contractual data-protection arrangements apply. Work out whether information is used only to provide your service or for any additional purpose. Do not assume an existing recording notice describes every new feature.

Review who can search, export and delete transcripts. A recording removed from the phone portal may still exist in a customer-management system, email attachment or staff download. The business needs a manageable record of those routes.

Subject access requests can include call recordings and transcripts containing a person's information. The normal response period is one month, with qualifications and possible extensions under the rules that apply. Have a process for identifying the relevant material and reviewing information about other people before disclosure.

Use the ICO's lawful-basis guidance and appropriate professional advice for your circumstances. A supplier describing its platform as compliant does not make the business's chosen use of it compliant automatically.

Keep card-payment information out of stored calls

The Payment Card Industry Data Security Standard, or PCI DSS, restricts storing sensitive authentication data after a payment is authorised. Card security codes are a key example. This issue applies to voice recordings as well as notes and transcripts.

Ask the payment provider and telephone provider to design the payment process together. A system that pauses audio but continues transcription can leave the same information in another form. A member of staff remembering to click pause is also different from a control that is built into the payment flow.

Consider arrangements that prevent the sensitive data entering the recorded conversation in the first place. The appropriate design depends on your payment service and security requirements. Have the relevant provider confirm the process and its assessment rather than relying on a generic assurance from a phone salesperson.

Train staff on what to do if card details are spoken unexpectedly. The response should include the approved handling and escalation process. Do not forward a recording containing payment information around the office while asking who can remove it.

Keep payment controls in the acceptance test when changing calling platforms. The new system's default recording settings can differ from the old one even where the handset looks identical. A routine migration should not quietly create a new archive of sensitive data.

What to do next

Before retiring the previous system, organise one practical review involving the people responsible for phones, IT, payments and privacy. For a small business that may be a short conversation with the owner and two support contacts.

• Confirm emergency access, location records and remote-working instructions.
• Identify every device that needs power for calling to work.
• Test the agreed fallback route and document who reports faults.
• Record the purpose, lawful basis, notices and retention for recording.
• Check audio, transcripts, exports and access permissions together.
• Have payment handling reviewed and tested through the approved process.

Ask the provider to demonstrate call groups, failure diverts and simultaneous-call limits. A hunt group is the arrangement deciding which staff phones ring; quality of service, or QoS, prioritises relevant traffic within supported network equipment. Useful features still need correct configuration.

Keep the completed checklist with the service agreement. Repeat the relevant checks when adding recording, moving premises or changing how staff work. The business phones and VoIP guide helps frame the broader comparison once these operational requirements are clear.