Cloud phone system: when telephony becomes a sales problem

Piattaforma di comunicazione Wildix: centralino cloud con AI per le PMI

Tuesday morning, an installation company with two sites. The phone at the head office rings three times and nobody answers: the receptionist is signing a delivery note for the courier. The number stays on the display of a handset nobody will look at. Half an hour later the same customer sends a WhatsApp message to the technician they know, who at that moment is on a roof. In the afternoon a web form arrives too, with the same request worded differently. Three contacts, three routes, nobody in the company seeing them together: this is where a cloud phone system stops being a question of phone lines.

The question management asks in cases like this is not about the cost of voice traffic. It is about how many requests get lost and how long it takes before someone picks them up.

Why a traditional system cannot answer management’s questions

A classic PBX does its job: it routes calls, manages extensions and queues and keeps communication running. The limit does not depend on the age of the equipment; it depends on memory. Whatever passes through a phone call vanishes the moment you hang up, and with it the information management would like to reason on.

How many calls went unanswered last month, in which time slots they were concentrated, how many customers called a second time because nobody had got back to them: these are reasonable questions, and almost nobody in the company can answer them. A traditional system does not keep that kind of data, because it was not built to. A cloud phone system starts from a different premise: every conversation leaves a trace.

The customer who writes to the sales rep’s personal number

We meet this situation in almost every analysis. The customer has the sales rep’s or technician’s mobile in their contacts and writes there, because it is the shortest route. The conversation stays on a personal phone and the company knows nothing about it.

The consequences fall on three levels. Operationally: when that person goes on holiday or changes role, nobody knows what had been promised to the customer. On coordination: two colleagues work on the same request without knowing it and the customer receives two different answers on the same day. On confidentiality: quotes, addresses and contract data travel on a channel the company does not control and from which it cannot extract anything.

What changes when conversations enter a single flow

A unified communications platform brings telephony, internal chat, video calls, website channels and messaging into one environment. Whoever answers sees the contact’s history while talking, and a request arriving on WhatsApp ends up in the same queue as the call.

The practical advantage lies less in the convenience of having everything in one window than in the trace each contact leaves: who answered, how long the customer waited, what was decided, what remains open. Shifts are built on that trace, workloads are rebalanced and the point of the day when the service saturates becomes visible. Read this way, a cloud phone system looks more like a management tool than a piece of telephone equipment.

Artificial intelligence on the cloud phone system: what already works today

Here it is worth separating the levels. A voice assistant that answers outside business hours, recognises the request and routes it is mature technology, and it is assessed by counting how many requests it closes without passing them to a person. Call transcription with a summary and an indication of tone adds a further level of analysis: a sales manager reads in a few minutes how ten negotiations went, instead of waiting for Friday’s report.

The next step concerns automations that act on someone’s behalf: opening a ticket, updating the customer record, reminding of a promised call-back. Here the result depends less on the language engine and more on how well processes upstream are organised, a topic linked to managing sales data in the CRM and to integrating telephony, collaboration and security.

Cloud phone system: the questions to ask a vendor before signing

Anyone assessing a platform faces presentations that look very much alike. These six questions help tell them apart, whatever name is on the cover.

  1. On the day the company changes vendor, which data does it take away and in what format: recordings, transcripts, statistics, directories?
  2. When voice quality degrades, who takes charge of the problem: the platform provider, the line provider, or a single point of contact responsible for both?
  3. Has the integration with the ERP and CRM in use already been built for other customers, or would it be the first time?
  4. Where are recordings and transcripts physically stored, for how long do they remain available and on what basis does the company keep them?
  5. How long does porting the existing numbers take, and what happens during the switchover window?
  6. Which features are within the initial scope and which become add-on modules at the first renewal?

For the rules of the Italian electronic communications market the institutional reference remains AGCOM, the communications regulator, where buyers of voice services find the obligations and protections in force.

Who manages the cloud phone system after activation

The difference between a solid project and one that drags on shows in the months after go-live, when the effect of the demo has worn off. At Aesir Srl we manage unified communications within our managed services: MSP and MSSP under the same contract, with a single point of contact for the platform, the workstations and the security that protects them. Customer environments sit in our Tier IV data centres in the European Union with replication; the ISO 9001, 27001, 27017 and 27018 certifications describe how we manage them.

Connectivity stays within the project scope: we measure line quality before signing and we handle coordination with the carrier, so the customer has one point of contact from analysis to acceptance testing. We work on projects across Italy and, on specific request, in Switzerland, the United Kingdom and the United States: in those projects telephony is rarely the first component to be addressed, and this has taught us in what order it pays to move.

How to move to a cloud phone system without stopping the business

The move to a cloud phone system runs on parallel tracks: the new environment works alongside the old one until real traffic confirms the flow map. Migrating the lines is the most visible part and, as a rule, the least risky; the points to design carefully are connectivity, integrations with the ERP and CRM, and defining who answers what.

A well-run project opens with the flow map: which numbers exist, where they ring, who answers at what times and where a call ends up when nobody is available. It is the least technical work of the whole process and the one that decides its success, because every unwritten rule that emerges here is one less problem at acceptance testing.

Next comes checking connectivity at each site, measured at peak hours and not with empty offices. Voice is unforgiving: a line that handles browsing can give way with twenty parallel conversations.

Number porting comes only at that point, and it runs in parallel: the new environment works next to the old system until ring groups, hours and messages behave as the map says. No number stops ringing during the switch, and the old system is turned off when the new one has already been carrying the traffic for days.

Integrations with the ERP and CRM and staff training close the process. The most effective order starts with the system and the collaboration tools, gives people time to absorb them, then adds digital channels and automations. Those who start with the virtual assistant while processes are still in disorder get a new cloud phone system and the same problems as before.

The phases of the switch, in the most reliable order:

Phase What is done Why it matters
Flow map Survey of numbers, hours, ring groups and unwritten rules Every rule found here is one less problem at acceptance testing
Connectivity check Measuring each site’s lines at peak hours Voice stays stable even at full load
Parallel number porting The new environment runs alongside the old one until it behaves as mapped No number stops ringing
Integrations and training Connection to ERP and CRM, people supported on the new flows The tools become part of daily work

Frequently asked questions

Do all the phones need replacing?

Not necessarily. People work from a browser, a desktop app or a smartphone, and a physical handset is added where needed, for example at reception or in the workshop. The hardware scope is defined during the analysis, not from a catalogue.

Can WhatsApp become a company channel?

Yes: the platform handles different channels in a single flow, WhatsApp included. Methods and requirements must be checked during the project, together with the rules the company wants to apply to data and message retention.

Does the virtual assistant replace the receptionist?

In properly planned projects, no. It handles repetitive requests and passes those outside the pattern to a person. The aim is to avoid using people on questions repeated hundreds of times a month, while keeping the human presence where it counts.

What happens to the cloud phone system if the connection drops?

A cloud phone system depends on connectivity, so continuity has to be designed: a backup line, automatic diversion to mobile numbers, traffic priority on the router. These choices are defined during the analysis: designed together, they make the service more robust than a system tied to a single line.

Does the cloud phone system integrate with the CRM already in use?

Integrations with sales tools and company systems exist. Feasibility on the specific CRM or ERP in use must be checked technically before it is included in the project scope, not afterwards.

Let’s talk

Before watching a demo it is worth answering the six questions in the list with numbers, not impressions: how many missed calls, in which time slots, how many promised call-backs never made, how many requests arrive on channels the company cannot see. The company already has this information, scattered among different people, and half a day is enough to collect it. If you would like to explore the topic or assess your company’s situation, fill in the form at the bottom of the page or write to support@aesir-tech.it: we will book a free consultation and start from your numbers.

Vuoi parlarne applicato alla tua azienda?

Ti rispondiamo con l’esperienza di progetto, non con una brochure.

Request a call