Microsoft Teams is a phone client. That is not the same as a phone system.

There are two ways to add calling to Microsoft Teams. They give you very different businesses. Five questions decide which one you need.

Almost every business we walk into is already living inside Microsoft Teams. Meetings happen there. Messages land there. Files, contacts, projects, the daily back-and-forth — it is where the day actually gets done.

So adding phone calls to Teams looks like an easy decision. And in fairness, it usually is an easy decision to make. It is a harder decision to get right, because “we put calling into Teams” can describe two completely different outcomes, and the difference does not show up in the demo. It shows up about six weeks later, at the front desk.

Teams is an excellent phone client

Let us be fair to Microsoft Teams handles person-to-person calling well. Dial a colleague, transfer a call, take it on your laptop, pick it up on your phone. For a knowledge worker at a desk, it is a perfectly good experience.

A phone client is the thing you talk into. A phone system is the logic that decides what happens to a call before, during and after somebody talks into it — where it lands, who else can pick it up, what happens when nobody does, whether anyone can prove what was said, and what you learn from the ones that never got answered.

Teams is very good at the first job. It is thin at the second. That gap is where most Teams calling projects quietly disappoint.

Road one: dial tone into Teams

The first road is Direct Routing. You keep your numbers, we connect proper New Zealand voice services into your Teams tenant through our own session border controllers, and your people make and take calls in the app they already have open.

It is clean. It is quick. If your calling needs are genuinely simple — a team of people at desks, calls arriving one at a time, nothing that has to be recorded or measured — this is a sensible answer and you should not be talked into more.

What you are accepting is that your call handling is now whatever Microsoft gives you. Not less, but not more either.

Road two: a cloud PBX behind Teams

The second road puts a full cloud PBX behind the Teams experience. Your people still work in Teams. But the call handling, the queues, the recording, the reception console, the mobile behaviour and the reporting all come from a platform built to do exactly that.

Presence stays in step, so a caller is not routed to somebody who is already on a call or in a meeting. Queues and hunt groups are visible and manageable. Calls can be recorded and retained. A receptionist gets a proper attendant console instead of a chat window. Mobile phones can connect like extensions. Wallboards and analytics show what is actually happening. And where the CRM supports it, the record opens before the greeting finishes.

Same app for the user. Very different business underneath.

Five questions that decide which road you are on

None of these are technical questions. All of them are answered by people who do not work in IT.

1. Who answers your main number, and what are they using to do it? If one person fields the switchboard, they need to see who is free, who is on a call, who is out, and move a caller in one action. A chat client is not built for that job, and the person doing it will tell you so within a fortnight.
2. How many of your people are not at a desk? Warehouse, field, trades, drivers, clinical staff, after-hours on-call. If a meaningful share of your team works from a mobile, you need one number that follows them and a device that behaves like an extension — not a second app they have to remember to open.
3. Could you prove what was said on a call last Tuesday? A disputed order. A complaint. A verbal instruction that turned out to be expensive. This is not a convenience feature; it is your position in an argument, and it is a compliance requirement in more sectors every year.
4. Do you know what your callers experienced, or only that calls happened? Call logs count activity. They do not tell you how long people waited, how many hung up before anyone answered, or which hour of which day you are losing business. Nobody complains about the calls you never knew about.
5. When it stops working at 4:45pm on a Friday, whose problem is it? Teams calling sits across a carrier network, a session border controller and a Microsoft tenant. That is three boundaries and, if you have bought it in pieces, three parties who can each point somewhere else. It is worth knowing in advance which single phone number resolves that.

The question underneath the questions

Most businesses do not get this wrong because they chose badly. They get it wrong because nobody framed it as a choice. Calling gets added to Teams as a line item, the front desk absorbs the difference, and eighteen months later somebody is quietly building a workaround in a spreadsheet.

If your calling is simple, keep it simple. If it is not — if there is a queue, a receptionist, a compliance obligation, a mobile workforce or a customer experience you are accountable for — then you need a phone system behind the phone client, and you should decide that on purpose.

And if you are heading towards a contact centre

There is a third thing worth saying, because it saves money later. Front-office calling and contact centre are different problems. Trying to force a general phone system to behave like a contact centre — or buying contact centre licences for people who just answer the phone occasionally — is how organisations end up paying twice.

The better shape is usually front office in Teams, contact centre on a platform built for it, one numbering plan across both, and one supplier accountable for the join. That way growth is an extension of what you have, not a replacement for it.

Where to start

Start with the five questions. Answer them honestly with the people who actually handle the calls, not with the people who sign for the licences. The answers will tell you which road you are on well before anyone shows you a product.

We are a New Zealand-owned communications provider and we build both roads. We will tell you which one you need.