Automation Journey

Microsoft Teams Telephony — from manual to 30-second provisioning

What once took a team of people, multiple systems, and up to 27 hours to complete now runs end-to-end in under a minute. This is the story of how O365Automated transformed Teams Telephony provisioning from a managed-services contract into a fully automated, 24/7 workflow engine.

27h
Before
30s
After
Time to provision & resolve 99.97% faster
Background

How it started

Teams Telephony provisioning was originally managed externally through a Managed Services contract with Dimension Data, handling around 100 colleagues per month. As the organisation's Automation Strategy matured, an opportunity emerged to bring that capability in-house — faster, smarter, and always on.

📞
~100 users
provisioned per month at peak managed-service volume
🏢
Dimension Data
managed the provisioning workflow via contract
Timeline

The journey from contract to cloud

2022 – 2023

Managed Services — Dimension Data

Teams Telephony provisioning handled externally. ~100 colleagues provisioned per month under a structured managed services contract.

2023 – 2024

Opportunity identified

Automation Strategy review surfaced provisioning as a high-value candidate for end-to-end automation — reducing manual effort and improving SLA compliance.

2024

Cloud onboarding

Platform infrastructure prepared. Foundational cloud architecture laid out to support the automation engine and integration with Microsoft Graph and Remedy ITSM.

2025

Enlivening, development & integration

Full automation workflow brought to life. BOT-driven provisioning, SRD form integration, billing updates, welcome emails, and Remedy ticket closure — all automated end-to-end.

Process comparison

Manual process vs automated workflow

The same eight steps — one driven by people, one driven by the BOT.

⚙️

Manual process

People-driven
📋
Call recorder functionality check
Manually verified before any action taken
🎫
Remedy ticket logged and resolved
ITSM ticket raised, tracked, and closed manually
📊
TMS / reporting update
Billing and reporting systems updated by hand
📧
Welcome email sent to user
Manually drafted and dispatched
🔔
Notify requestor of provisioning
Manual follow-up communication
Approval & deployment info required
Chased manually — approvals delayed 2–3 weeks
🔑
License allocation by SWAM
Licence assigned through a separate manual workflow
📱
Available number look-up & assignment
Manual search, selection, and Teams provisioning
⏱ Average ticket closure: 27 hours
🤖

Automated workflow

BOT-driven
📋
Call recorder functionality check
BOT validates compliance recording status automatically
🎫
Remedy ticket read, actioned & closed
SRD form parsed by BOT — ticket resolved automatically
📊
TMS / billing update
Billing records updated in real time by the automation engine
📧
Welcome email sent to user
Templated, personalised welcome email dispatched instantly
🔔
Requestor notified automatically
Confirmation sent without any manual follow-up
Approval & data validated at SRD submission
Correct info captured upfront — no chasing required
🔑
License validated and allocated automatically
Graph-based licence check and assignment in real time
📱
Number selected and provisioned by BOT
Policy-based number allocation and Teams assignment — zero manual effort
⚡ Average ticket closure: 30 seconds
Challenges identified

What the manual process exposed

⚠ ITSD

Incorrect call logging, insufficient information provided, and requestors unaware of the correct process — creating repeated rework cycles.

⚠ Requestors

Inadequate information submitted with requests. Manager approvals delayed by 2–3 weeks. Multiple follow-ups needed before action could be taken.

⚠ Remedy Stats

Aged requests skewed perception of SLA compliance and ITSM performance. Reporting was misleading and difficult to act on.

⚠ Actions taken

Training sessions run, a 3-day SLA established, and multiuser requests split to improve throughput before automation was introduced.

Opportunities envisioned

What automation made possible

✓ Remedy SRD Form

A structured SRD form ensured correct information was captured at submission — reducing errors, improving data quality, and enhancing client experience from the first touchpoint.

✓ Automation tool

An agile cradle-to-grave automation platform capable of handling the entire provisioning lifecycle — from request intake to ticket closure — without human intervention.

✓ Process & provisioning automation

BOT reads SRD forms, validates data, checks licensing, provisions telephony, updates billing, sends welcome emails, and closes the Remedy request — fully automated end-to-end.

Benefit realisation

Measurable outcomes delivered

30s
to provision & resolve a staff telephony request end-to-end
🕐
24/7
automation availability — no business-hours dependency
📉
↓78%
ITSD call volume drop in the 2nd half of 2025
🎯
100%
SRD form uptake for new service requests in 2025
Benefit summary

What the team gained

  • Faster Remedy ticket closure — from days to seconds
  • Increased ITSD efficiency with reduced inbound call logging
  • Improved customer experience through instant, accurate provisioning
  • Voice team freed to focus on business pain points and higher-value work
  • Cleaner, more reliable analytics and reporting
  • Consistent provisioning outcomes — no human variation or error
Analytics

Time to deliver — ticket closure

Pre-SRD & automation 27 hours
With SRD form only 11 hours
With SRD + automation 6 hours
Full automation (provision only) 30 seconds
Strong uptake of SRD forms through 2025 service requests confirms adoption momentum
See it in action

Ready to automate your Teams Telephony provisioning?

From 27 hours to 30 seconds. See how O365Automated can bring the same transformation to your organisation.

An unhandled error has occurred. Reload 🗙