# Other Operational and Administrative Threads A miscellaneous batch of remaining .msg files not covered by dedicated source pages. Each is a small operational or administrative thread of low individual significance but worth indexing for completeness so the wiki's source coverage matches the production's file inventory. Most are auto-notifications, vendor-marketing one-offs, or minor support / onboarding interactions. ## What's inside (selected files) **Account-activation / setup:** - `Action Required Complete Your Flock Safety Account Activation.msg` — Conway-side admin account activation (early-onboarding mechanic). **Operational / status:** - `Billing.msg` — Generic billing-thread; possibly the invoice-routing question that surfaces in the later [[Flock Safety Past Due Balance INV-81961]] thread. - `Conway Police Dept - Conway Arkansas.msg` (×10) — Generic Conway PD-titled thread (10 variants); likely a Flock-internal account-tracking subject reused across multiple correspondence types. Per-variant content not individually anchored. - `Conference and Visiting Customers - Delayed Response Re Invoice.msg` — Flock's response delay on a specific invoice inquiry. - `Conference and Visiting Customers - Delayed Response Re W-9 Needed.msg` — Companion: W-9 form delay. - `OOO until Monday Re Flock cameras.msg` — Burningham OOO autoresponse. - `OOO sitting by the beach or pool Re Network Utalization.msg` — Burningham OOO autoresponse (note: "Utalization" likely typo for "Utilization"). - `Out of Office Until 31125 Re Conway PD.msg` — Counterparty OOO autoresponse. **Flock product / feature:** - `Flock Safety A Work Order Has Been Created for AR - Conway PD.msg` — Work-order creation notification (operational maintenance / repair). - `Flock Safety Promotion.msg` — Vendor-promotional email. - `Flock cameras.msg` (lowercase, ×2) — Mixed-content threads with the same subject as the April-2026 Council Q&A thread but earlier dates; specific content not individually anchored. **Customer feedback:** - `Flock Feedback Request for Alison.msg` — Flock survey request addressed to "Alison" (first-name only; Conway-PD user not yet identified — a deferred corpus seed). **Mapping meeting requests (companion to [[Conway-Flock Map Pre-Procurement Mapping (Nov 2024)]]):** - `Mapping Meeting Request - Flock Safety.msg` + (×2 variants) — Flock-side meeting-request thread for the Nov 2024 mapping conversation. Already cross-referenced from the main mapping source page. **Single-instance subjects not covered above:** - `Flock's quarterly product launch webinar.msg` — Webinar invitation (companion to [[Vendor Newsletters and Flock Forward Conference]]). - *Various other small one-off subjects covering routine vendor-customer operational interactions.* ## Key takeaways - **The production contains a long tail of operational ephemera** — work-order notifications, account-setup confirmations, OOO autoresponders, generic-titled threads — that together represent normal SaaS-customer-vendor business but do not anchor any specific investigative finding. - **OOO autoresponders (3 surfaced files) confirm Burningham takes scheduled time off.** The "sitting by the beach or pool" autoresponder is informal — confirming the Conway-side Flock administrator is a single named person (Burningham) with normal vacation patterns and no clearly delegated backup, consistent with the single-admin pattern documented across [[Action Requested - Pending Flock Camera Share Requests Series]], [[SSO Provisioning Notifications Series]], and [[Conway PD Audit Logs Series]]. - **"Alison" remains a corpus seed.** The `Flock Feedback Request for Alison` file references a Conway-side user by first name only; Alison's role and last name are not anchored in the corpus. A candidate for cross-correlation with SSO sign-in records (the 73 first-time SSO sign-ins should include an "Alison" surname-resolvable identity). - **"Conway Police Dept - Conway Arkansas" (×10) is a recurring generic subject** that Flock uses across multiple correspondence types. Without per-file inspection, the 10 variants may carry different operational content under the same flat subject — an inspection opportunity if a specific question demands it. - **No additional smoking-gun documents** are expected from this batch on filename inspection. Where the filenames suggest substantive content (e.g., a "Work Order" thread might reference a vandalism repair tying to [[MSA via Cameras Thread]]), those would warrant individual reads in later review. ## People and orgs mentioned - [[Lt. Andrew Burningham]] — primary recipient. - [[Flock Safety, Inc.]] — sender across most files. - **"Alison" (CPD)** — corpus seed; role unspecified. ## Concepts invoked - (Inherits broadly from other source pages.) ## Cross-references - [[AR - Conway PD - Welcome to Flock!]] — onboarding context. - [[Conway-Flock Map Pre-Procurement Mapping (Nov 2024)]] — mapping-meeting context (the mapping-request files are sub-anchors here). - [[MSA via Cameras Thread]] — vandalism context (the Work Order thread may reference vandalism repairs). - [[Flock Safety Past Due Balance INV-81961]] — billing context (the Billing.msg thread may reference billing-routing decisions). ## Open questions / follow-ups 1. **Per-variant inspection of "Conway Police Dept - Conway Arkansas"** (10 files) — if needed to resolve any open question. 2. **Identify "Alison."** Cross-reference Conway PD SSO sign-in records or per-officer payroll data. 3. **Work-order content.** What did the "Work Order Has Been Created" notification reference? Possible link to vandalism repairs.