Home / Case studies / Communications
Communications

Every call answered or captured, with voicemails that become tasks

A Teams Phone menu routes callers by type, and unanswered calls become tracked tasks with a transcript instead of a blinking light.

Status
Running in production
Result
A voicemail becomes a task in 8 seconds.

Running in production

On the main number since 2026-09-22. We also record what is unproven: the settings screen’s apply path has not yet been exercised on a real change.

The situation

The agency’s main line rang a single person’s desk phone. Calls could not be routed by caller type, and voicemails had no shared place to be worked.

The cost of leaving it alone

A patient or a physician’s office who cannot reach the agency does not leave a second message. They call someone else.

What we built

A cloud phone menu on Microsoft Teams Phone. It plays an emergency notice first, then offers four options (patient, doctor’s office, therapy provider, other) plus an operator, each with its own queue. Hours, after-hours and holidays are handled automatically.

Unanswered and after-hours calls go to a shared, transcribed voicemail that becomes a row on a Phone messages list, a Planner task carrying the transcript, a Teams card and the audio file. Hours, holidays and menu options are editable from SharePoint lists and applied by a script that dry-runs first.

Teams Phone: auto attendant, call queues, calling planExchange shared voicemailPower Automate, SharePoint, PlannerPowerShell

Why AI, or why not

No generative AI. Routing is by key press. The only machine learning is Microsoft’s built-in voicemail transcription, which we never switch off “for privacy” because the transcript is what makes the message a task.

The results

2 min
outage at cutover, after a first attempt was rolled back at 9 minutes
8 sec
from a test call to a finished task
4
queues, with a 60-second wait and a 20-call overflow
8
holiday ranges handled with no one touching a phone

How PHI was protected

  • Transcripts and recordings stay inside the tenant: a group mailbox, Planner and Teams.
  • No outside AI service is used, and access is limited to the operations group.
  • The intake step refuses to copy a message outside the tenant’s accepted domains.

What we would tell you to skip

Every link in a chain can fail silently. Deleting a Microsoft 365 group deleted the Planner board it owned, and tasks quietly stopped for about two days while the phone itself looked fine. Place a real test call after every change.

Reusable for

Small Microsoft 365 agencies without a phone tree or an answering service.

Tell us the one workflow that costs you the most time.

A working session is free of obligation: we look at one process, tell you plainly whether AI belongs in it, and what keeping it inside HIPAA would take.

Book a working session