Multi-site community healthcare provider · 2026

Automated Teams call-flow documentation

Turned an unreadable, auto-generated call-flow export into a linked set of diagrams and PDFs covering every auto attendant and call queue across a multi-site phone system.

  • Microsoft 365 & Teams
  • Code & DevOps
bugs fixed in the open-source tool
3
Graph consent prompts needed
0
diagram per auto attendant and queue
1
Architecture

How it fits together

  1. 01

    Export

    • Teams PowerShell
  2. 02

    Visualise

    • Forked call-flow visualiser
    • Node.js
  3. 03

    Render

    • Mermaid
    • PDF generation
  4. 04

    Deliver

    • Master overview
    • Per-site PDF set
Outcome

A master overview plus a per-site diagram set — and three bugs fixed in the open-source tool along the way.

The problem

Layered auto attendants, clinic queues, holiday routing and overflow paths. The existing tool produced one giant, tangled diagram nobody could read — and it needed broad Graph consent to run.

What I did

  • Forked the visualiser to run on the Teams PowerShell module alone, removing the Graph dependency and its recurring admin-consent prompt.
  • Fixed three bugs: node IDs starting with a digit broke rendering, orphaned overflow targets crashed the run, and an empty-array comparison threw.
  • Split the output so every auto attendant and queue gets its own diagram with previous/next links, and factored shared paths (overflow, after-hours) into single-source files.
  • Kept the default layout engine because the alternative broke chronological reading order, and used invisible edges to control sibling order.

Result

The customer received a master call-flow overview that names every detailed PDF, plus one document set per site — something their team can actually read and maintain.