Dashboard
Overview of received tone alerts
Top Tone Sets
Recent Alerts
Alerts
All received tone alert dispatches
| Time | Tone Set | System | Talkgroup | Transcript | Audio | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Alert Detail
System
API keys, password, data retention, and integrations
Change Password
API Key
This key must be entered in the Thinline Radio admin page for each channel or the global downstream setting.
It is sent as the X-API-Key header with every tone alert.
Data Retention
Alerts older than this many days are automatically deleted. Set to 0 to keep forever.
Integration Settings
Configure the pipeline that curates incoming tone alerts and dispatches them as formatted CAD emails. All keys are stored securely in the local database — no environment files needed.
OpenAI — Transcript Curation
Used to extract and curate structured alert fields from the raw transcript (gpt-4o-mini). Optional — raw transcript is used as fallback.
When enabled, each Active911 CAD match automatically adds clean street names and STT corrections to the tone set's street group via GPT. Recommended while building up your street library — disable once coverage is solid (typically after ~1 year of active use).
When > 0, the email is held while Active911 is polled for CAD data — attempt at 0 s, then every 5 s up to this limit. If no match is found by the deadline the email sends with transcript data only. Set to 10 for most agencies (CAD typically posts within 5–10 s of dispatch).
Google Maps — Address Geocoding
Validates and corrects the extracted address, supplies lat/lon. Optional.
SendGrid — Email Dispatch
Must be a verified sender in your SendGrid account.
These addresses receive every alert regardless of tone set. Per-tone-set recipients (configured in Tone Sets) are added on top.
Audio Playback Link
Base URL of this server, reachable from outside. Used to build the /play/{token} link embedded in each email. No trailing slash. Leave blank to omit the link.
Local Context
Tells the AI where dispatches originate — improves address and street name correction. Example: Trumbull County, Ohio
PostgreSQL Database (Optional)
Connect to a PostgreSQL database for operational data (tone set configs, street groups). Leave blank to use SQLite. Changes take effect on server restart.
Standard PostgreSQL DSN. Leave blank to use SQLite fallback.
User Management
Manage department users who can login and edit known streets and street corrections.
Tone Sets
Per-tone-set unit labels, email recipients, street groups, and geocoding
Tone Set Groups
Groups hold simultaneous dispatches and merge them into one notificationCreate a group and assign tone sets to it. When the same callId fires multiple tone sets in the same group within the merge window, they are combined into a single alert (e.g. STA40 / STA41). Tone sets without a group are processed immediately.
Tone Set Configurations
Pushed from TLR · configure per tone set belowEach tone set has its own unit label, email recipients, street group, location context, and geocoding radius. Tone sets are synced from TLR — use Add Manually for testing.
+ Add manually
Street Groups
Each group contains known street names (used by the AI) and STT corrections (bad→good replacements). Assign a group to a tone set on the Tone Sets page.
Street Groups
Nature Codes
Known emergency call types / incident classifications used in the OpenAI transcript parser. Codes are seeded from built-in defaults and auto-expanded from Active911 descriptions when Auto-learn is enabled in Integration Settings.
Add Custom Code
Codes are case-normalised to ALL CAPS. Adding a code here marks it as builtin (manually curated).
All Nature Codes
Known Streets
Edit known street names for your department
Street Corrections
Map incorrect street names to correct ones
Display Board
Live alerts with maps and Active911 integration