Skip to content
Lambert Consulting

Artificial Intelligence: A Cross-Functional Offering

Results first. Infrastructure second.

An assistant for your documents, end-of-line verification, a platform for multiple services. Where artificial intelligence is applied is determined by your data, not by a catalog.

See all solutions
4Comparing Architectures, Criterion by Criterion
2 fieldsSoftware and hardware under one roof
All Use CasesUse cases first, technology last

Our first department

This is what needs to work every morning.

Your servers, your workstations, your phone systems, and your identities. The foundation that no one notices as long as it holds, but that everyone notices the day it fails.

View the department
Multi-siteNational and international projects
3Branches in French-speaking Switzerland
View our client projectsCase Studies and References
Let us know how you're doingGetting a quote is free

How We Work

A piece of advice, not a sales pitch.

Our approach is consultative: we tell you what we think, even when it’s not in our best interest. That’s what makes projects succeed.

About Us
1995First project, using Microsoft SMS
Family-orientedOn a human scale and sustainable

Our Branches

Vaud, headquarters9 Avenue des Baumettes, 1020 Renens+41 21 806 37 15
Valais134 Oscar-Bider Street, 1950 Sion+41 27 552 00 22
FribourgChemin de Montmoirin 18a, 1618 Châtel-Saint-Denis+41 26 322 59 05
Monday through Friday8:00 a.m. – 6:00 p.m.
Contact UsFirst 30-minute consultation, with no obligation
Product designed and developed by Lambert Consulting

Microsoft Teams didn't have a tool for managing voice on a large scale. We developed one.

Multiple sites, multiple operators, multiple tenants: a single portal.

NexTeams365 Automates user creation, number assignment, and the enforcement of Microsoft policies Teams, site by site and carrier by carrier. It is installed on a server you own, and data never leaves that server.

Watch the video demonstration

On your serversThe portal, database, and reports remain within your infrastructure
Direct Routing and Operator ConnectBoth operator connections in the same portal, using your session controllers
Your users can't see anythingIt’s an administrative tool: Microsoft Teams remains Microsoft Teams

The Starting Point

What Manual Provisioning Really Costs.

The Microsoft Administration Center Teams and just a few commands are enough to last a very long time. What causes them to fail isn’t the number of users— it’s the number of sites, operators, and people who interact with the same numbering plan. Three issues then arise, always in the same order.

01

The same work, done differently in each location

One administrator creates users using their own commands, while another uses theirs. Microsoft policies Teams vary from site to site without anyone having decided to do so, and the way to proceed was known only to the person who was familiar with it.

The expertise is real, but it isn't written down anywhere.

02

The numbering plan is stored in a spreadsheet

The beaches by location, the numbers already taken, those reserved for an expected arrival, those freed up by a departure: all of this is tracked in a file that several people edit, and in the memories of a few.

Duplicates and orphan numbers are only noticeable when they cause problems.

03

The bill arrives before the explanation

The telecom statement is a general overview. There is nothing linking it to a specific location, service, or cost center, so no one can say how much of the increase is due to actual usage and how much is due to a forgotten setting.

A budget that can't be cut is a budget that can't be defended.

Before we go any further

What types of companies is this portal designed for?

Six situations in which a dedicated portal quickly proves its worth. These situations often occur together: it is their combination that makes the difference, not any one of them on its own.

Scenario 01

Multiple locations, multiple numbering plans

Each site has its own ranges, prefixes, and Microsoft policies Teams. What is consistent across sites is precisely what causes the discrepancies.

Scenario 02

More than one carrier

Direct Routing on one site, Operator Connect on another, with a session controller somewhere in between. Today, the two environments are managed separately.

Scenario 03

A directory maintained in two locations

Active Directory on your servers and Entra ID, sometimes with an identity management tool in between. The telephony system must sync with both without requiring data to be entered twice.

Scenario 04

Costs to be Allocated

A telecom statement to be broken down by location, department, or cost center, and an accounting department that expects an export rather than a file that has to be manually revised each month.

Scenario 05

Multiple environments to manage

A company that has grown through acquisitions ends up with multiple tenants. Multi-tenant compatibility is one of the reasons this product exists.

Scenario 06

An IT team that no longer has the time

Provisioning isn't difficult; it's repetitive. It involves hours of an engineer's time spent on tasks that a machine can perform flawlessly.

And what if the answer is to install nothing at all? A single site, a single operator, a few dozen workstations, and a directory maintained in one place—the Microsoft Administration Center ( Teams )—is more than enough, and adding another portal would do nothing but create yet another server to maintain. We say this before making the offer, not after. NexTeams365 is justified when replication between sites becomes the real cost—not when the entire environment fits on a single screen.

Where it fits in

It controls what you already have.

NexTeams365 It does not replace your phone system, your directory, or your session controllers. Everything that contains your data fits within the left-hand pane: that's yours.

Your Infrastructure Identities Active Directory Entra ID FIM / MIM On your server NexTeams365 Data SQL Server Reports SSRS Costs ERP Microsoft 365 Users Microsoft Teams Your operators Direct Routing via your SBC Operator Connect allocates call logs calls

The portal reads your phone book, provisions Microsoft Teams , and retrieves call logs from it to allocate costs. The calls themselves never go through the portal: they go from Microsoft Teams to your carrier, exactly as they do today. That’s why an outage of the portal delays new provisions without cutting off a single line.

What he does

Five modules, each with the details that matter.

A single portal replaces orders and files. What follows is not a list of promises— these are the settings your team will work with on a daily basis.

Module 01

Provisioning and Automation

Create a user, assign a number and extension, and apply Microsoft policies Teams  —all in a single step. Numbers are drawn from ranges defined by site, with priority, manual reservation, and temporary blocking.

Module 02

Multi-site and multi-carrier

Direct Routing and Operator Connect side by side, a visual representation of the correspondence between site, gateway, and number range, and multi-tenant compatibility for enterprises with multiple environments Microsoft 365.

Module 03

Routing and Number Conversion

Routing by location, department, or extension; conversion of incoming and outgoing numbers; conditional blocking by reason, range, or category. Rules are defined once and apply everywhere.

Module 04

Reports and Monitoring

Fourteen ready-to-use reports on SQL Reporting Services, exportable to PDF and spreadsheets, plus your own reports. SCOM integration, and detection of errors, blocked calls, and unusual discrepancies.

Module 05

Costs and Billing

Cost allocation by user, site, and gateway; a pricing matrix specific to your contracts; automatic export toERP; and integration with Microsoft call logs Teams.

And on top of that

Security and Roles

Authentication Windows or unique identification, with permissions based on your groups Active Directory, general administrator, or single-site administrator. Every action is logged.

Demonstration

NexTeams365 in action.

The portal, number ranges, and user provisioning—all in just a few minutes.

Our Position

A tool that manages your phone system has no business being anywhere other than on your servers.

NexTeams365 is deployed within your infrastructure. The portal, database, and reports are hosted on a server you own; authentication is handled through your directory, and no data is sent to an external service.

The data never leaves your infrastructure

Everything the portal processes remains in your database, your directory, Active Directory and your Microsoft Teams environment. There are no copies stored elsewhere, because there is nowhere else.

Access is through your groups Active Directory

Authentication Windows or unique identification, encrypted HTTPS communication, role-based and site-based permissions, and daily limits on the number of creations, modifications, and deletions.

We do not access your data

Unless you have explicitly authorized us to provide support—in which case access is restricted, logged, and subject to confidentiality.

What the project does not change

Your users won't notice any changes.

This is an administrative tool, not a rollout to be implemented among teams. The benefit is for the IT department, and there is no risk to employees.

No training

Microsoft Teams remains the same for your employees

No new app to install, no workstations to reconfigure, no internal communications to prepare. Your employees can continue to make calls just as they did the day before.

No dependency

If the portal goes down, calls will continue

Microsoft Teams does not rely on NexTeams365 to function. An outage of the portal delays new provisions but does not disconnect any active lines.

No manual rework

A loss of connection puts tasks on hold

Automatic processing is paused without affecting existing services, and synchronization resumes automatically as soon as the connection is restored.

What You Need

The prerequisites, written before the first appointment.

NexTeams365 It is deployed within your infrastructure, which means you’ll need to allocate a server. Here is the exact list, so that capacity planning can be done before the proposal is submitted, rather than during implementation.

What You NeedDetails
A dedicated serverWindows Server 2022, 16 GB of memory, 4 processors
A databaseMicrosoft SQL Server 2016 or a later version
ReportsSQL Reporting Services, in the same installation
Microsoft LicensesMicrosoft 365 E5 or Teams Phone Standard
The directoryActive Directory, Entra ID, or both in a hybrid setup
IdentificationAuthentication Windows or unique identification
The EnvironmentTeams , a Microsoft phone service, is already in use

There are two things you need to keep in mind, and it’s best to know them now. Backup and high availability depend on your database infrastructure: NexTeams365 relies on the rules you already have in place; it doesn’t introduce any new ones. And a dedicated server is a physical machine that requires ongoing maintenance and monitoring —it’s not a subscription service. We include this component in the quote rather than having you discover it later on; if you’ve already entrusted us with managing your servers, it’s included at no extra cost.

One term, six phases

How is the rollout proceeding?

It starts with a trial run on your own system, not with a promise. The fourth step is the one that determines how long the rest of the process will take, and it’s almost always the one that gets underestimated.

01

NexTeams365 for testing on your system

Before rolling out the system across the entire network, the portal is installed on a limited scale and set up for real-world use: a pilot site with its own zones and operator, a test environment, or a small group of users—whichever works best for your installation.

You'll see the provisioning process in action on your own directory, using your own numbers. And any specific issues with your setup will come up here rather than at the end of the project —there are always some.

What You Get: The portal in operation on a limited scale Controlled provisioning on your own numbers Specific details of your installation noted
02

An Inventory of Your Facility

The sites, operators, and gateways; the number ranges actually in use; the Microsoft policies in place Teams ; and how the directory is currently maintained.

This is when we measure the discrepancy between the official numbering plan and the one actually in use. This discrepancy always exists.

What You'll Receive: List of Beaches by Location List of operators and gateways Status of Microsoft policies Teams
03

The server, the database, and the portal

Set up the dedicated server, database, and reports for the entire fleet, followed by the portal. Roles are assigned to your groups Active Directory at this stage, ensuring that no one ever works with more access than necessary.

What You Get: Server and database up and running Portal accessible via HTTPS General and site-specific roles defined
04

The Transfer of the Numbering Plan

Each site is assigned its time slots, priorities, and reservations, and the numbers already assigned are reconciled with the directory. This step sets the stage for all subsequent steps.

Duplicates and orphaned numbers inherited from a spreadsheet appear here. This is normal, and now is the right time to address them : dealing with them now will take a few days, but dealing with them after the migration will result in incidents.

What You'll Receive: Time Frames and Priorities by Site Duplicates and orphan numbers processed Existing reservations imported
05

Call Routing

Routing by location, department, or extension; conversion of incoming and outgoing numbers; conditional blocking. Each rule is tested on a subset of numbers before being applied to the entire set.

What You Receive: Site-Specific Routing Rules Number transformation rules Documented Conditional Blocks
06

Operation and handover

The reports are up to date, cost allocation is set up for your cost centers, and the export toERP is managed from start to finish. Then your teams manage the portal themselves, and we remain available.

What You'll Receive: The fourteen reports currently in use Export to theERP under supervision Your teams working independently on the portal

Questions We Are Asked

Frequently Asked Questions.

Including the last one, which explains what the product doesn't do.

Should we upgrade our telecom equipment?

No. NexTeams365 integrates with SBC and existing telecom equipment: it controls them, it does not replace them. The same applies to the carrier connection itself.

Does this portal replace Microsoft Teams Phone?

No, and let's get this out of the way right away. Microsoft Teams Phone remains your phone system; NexTeams365 is the management layer on top of it. Microsoft licenses are still required, and the product does not reduce what you pay to Microsoft in any way.

What it reduces is the amount of time spent by engineers and the number of configuration errors.

Can you manage multiple tenants from a single portal?

Yes, multi-tenant compatibility is part of the product. In fact, it’s one of the reasons the product exists: a company that has grown through acquisitions almost always ends up with multiple environments Microsoft 365, and often with a different service provider in each one.

Can we try it out before committing?

That’s exactly the first step in a contract. A 30-day trial version is available for internal evaluation, but what we’re offering goes a step further: the portal is installed within a limited scope of your own environment and provisions your actual phone numbers.

It is budgeted as the first phase of the project because it involves engineering work on your environment—and because a management portal cannot be evaluated based on a generic demonstration.

What happens if we delete a user by mistake?

Its settings are preserved, and the record is marked as unused rather than deleted; its number remains reserved for thirty days before returning to the available range. A daily limit on the number of creations, modifications, and deletions is also enforced: an automated process that goes awry cannot empty a site.

What the portal doesn't do

This is not a contact center: multichannel queues, real-time monitoring of a support team, and integration with customer records are features of a product specifically designed for that purpose. It is not an operator either, and it does not replace your session controllers or your phone system.

Finally, it provides neither backup nor high availability: the features of your database infrastructure apply, and nothing else.

Why This Matters to You

What this product says about our work.

You may not need NexTeams365. You may need someone who can build it.

Microsoft Telephony: Beyond the Standard Settings

Direct Routing, Operator Connect, session controllers, multi-site numbering plans, call logs, and identity-based provisioning: these are the mechanisms this product handles, and the ones we handle in your projects.

If the tool doesn't exist, we develop it

NexTeams365 It arose from a need that no product on the market fully addressed. We apply the same approach to integrations, web services, and business applications.

We start with the problem, not the catalog

Assess the current situation, identify what’s truly missing, and then determine the appropriate solution: deployment, integration, or development—when nothing that currently exists is sufficient.

Continued

Let's start with your sites and connections

An hour with the engineers who will carry out the work, a list of your sites, and the names of your operators. We’ll tell you what needs to be inventoried, what the numbering plan transfer will reveal, and whether your situation warrants a portal—including when the answer is no.

There is no charge for preparing the quote; the on-site assessment is the first step in the project. We’d be happy to arrange a meeting with the engineers who will be doing the work. Three offices: Renens, Sion, Châtel-Saint-Denis.

The Decisive Question

How many number ranges does your company currently manage, and in how many files?

If you have a figure in mind, your project is ready to go: we can outline the acquisition and provide a cost estimate for the implementation within a few days.

If the answer is “you’d have to ask several people, that’s the most reliable sign that the portal is worthwhile—and that’s exactly where we start.