Teams Walkie Talkie for NOC / Field Operations Coordination Prompt

You are a senior operations engineer who has deployed Teams Walkie Talkie to field-services + NOC teams for instant voice coordination without the overhead of meetings or phone calls.

I will provide:
- Team distribution (field tech, NOC, in-office)
- Hardware (smartphones, ruggedized devices, headsets)
- Existing PTT solutions (Zello, ESChat, radio)
- Compliance requirements
- Pain points (slow phone-call escalation, missed alerts, hands-busy workflows)

Your job:

1. **When PTT (Walkie Talkie) wins over alternatives**:
   - **Field tech with hands busy** — PTT button on headset; no UI navigation
   - **Quick clarification** — "hey, is the bypass still active?" vs initiating a Teams call
   - **Distributed NOC** — instant comms across regions without scheduling
   - **High-noise environments** — gear with PTT button + boom mic better than phone

2. **Channel design** — Walkie Talkie channels are tied to Teams channels:
   - **`field-ops-region-east`** — region-specific field tech coordination
   - **`noc-current-shift`** — active shift NOC
   - **`escalation-on-call`** — gated to escalation chain
   - **`vendor-bridge-<vendor>`** — short-term, for active vendor coordination
   - Default: one PTT channel = one Teams channel (don't proliferate)

3. **Identity + accountability**:
   - Every PTT transmission identifies the speaker (Teams identity)
   - Posted in the channel as a brief audio clip (where supported)
   - Audit log of transmissions per shift

4. **Hardware**:
   - **iOS / Android** — built-in PTT button via Teams app or hardware key mapping
   - **Ruggedized devices** — Samsung XCover, Sonim, Zebra; programmable PTT button
   - **Headsets** — Jabra / Plantronics with PTT button; recommended for safety + clarity
   - **Vehicle integration** — CarPlay / Android Auto for in-cab PTT

5. **Integration with paging**:
   - PagerDuty / Opsgenie page → also broadcasts a brief PTT alert on the on-call channel
   - Useful for: shift-handoff (everyone knows new on-call is now active), incident notification (page + voice "incident in <service>")
   - Configurable per severity

6. **Conventions** (radio etiquette):
   - "10-4" style brief acknowledgments
   - Identify by name + role at start ("Mike, NOC east, copy?")
   - One topic at a time
   - End with "out" or "clear" so others can break in
   - Don't transmit prolonged conversations (use Teams call for that)

7. **Recording + compliance**:
   - Teams Walkie Talkie supports recording in some plans
   - For regulated environments: recording may be required
   - Consent disclosure (varies by jurisdiction)
   - Retention aligned to regime

8. **Use cases for SRE**:
   - **NOC shift handoff** — incoming shift PTTs to outgoing for verbal context
   - **Emergency escalation** — primary on-call PTTs the escalation chain
   - **Field tech to NOC** — field tech investigating a site PTTs status updates
   - **Cross-region coordination** — quick "is anyone seeing this?" without meeting

9. **What PTT is NOT** good for:
   - Long discussions (use a meeting)
   - Detailed instructions (use text)
   - Sharing log output (use chat)
   - Sensitive content (recordings may be retained)
   - Highly-distributed > 20 people (becomes one-way broadcast not conversation)

10. **Compliance overlay**:
   - Recording consent if recording enabled
   - PTT channel content subject to eDiscovery
   - Retention applied via the underlying Teams channel
   - In regulated industries: log PTT events similar to phone records

11. **Anti-patterns to avoid**:
   - PTT for sensitive customer data (recording risk)
   - PTT replacing real meetings for design discussions
   - No identification conventions (chaotic transcripts)
   - Spawning too many PTT channels (lose mind-share)
   - Forgetting to mute PTT during personal conversations

12. **Rollout plan**:
   - Pilot: one field-ops team, 4 weeks
   - Measure: cycle time on simple coordination, user satisfaction
   - Expand to NOC if pilot positive
   - Decommission legacy PTT (Zello, etc.) only after expansion

Output as: (a) when-to-use-PTT decision tree, (b) channel design, (c) hardware recommendations, (d) paging integration, (e) etiquette conventions, (f) recording + compliance policy, (g) what-NOT-to-use-PTT-for, (h) rollout plan.

Bias toward: brief, identified, accountable transmissions, hardware-PTT for safety, compliance-aware, complement not replace.