About

Spark now always displays in light mode, even when your phone or browser is set to dark mode, so forms and controls look the same for everyone.

Incident updates from your CAD connector now stay with your agency even when another CAD uses the same incident IDs, and incident status reads show the CAD's priority once it is reported.

Public report forms now load correctly right after an update, instead of sometimes showing an error until the browser refreshed its saved files.

The Data page shows where each incident came from, its delivery status and whether it is sandbox, with a filter for each.

Release notes have their own page in the side menu, listing each version's changes labeled by type.

Both public reporting forms have a cleaner layout that works on phones, and the standard report adds section navigation.

The admin area has new navigation that adapts to phones, and Settings sections open directly from the side menu.

The Dashboard, Data and Log pages and their detail dialogs have a refreshed layout that stays readable on phones, and Push to CAD now asks for confirmation first.

The quarantine review queue is easier to read, shows a fixed 14-day range, and confirms releases in a dialog that fits phones.

The /api/GIS geocoding and jurisdiction lookups now require an agency connector key and are rate limited; the unused Geocode and ReverseGeocode routes are removed.

Integrators can read an incident's delivery status, CAD number, open or closed state and disposition with GET /api/v1/incidents and the new incident.read scope.

When CAD delivery can't be confirmed, create answers 504 and never sends the incident twice; admins are alerted and can mark it delivered or failed on the Data page.

Requests over 256 KB are refused with 413, and updates for an agency without a configuration return 404 instead of a server error.

API clients can subscribe to signed webhooks for incident delivered, rejected and closed events instead of polling; agency admins set the URL and events on the API Clients page.

Each API client can now read, update and cancel only the incidents it created.

Restored incident creation by the AI voice agent, which now authenticates with the agency's connector key.

Agency admins can create, revoke and delete API clients on the new API Clients page; revoked clients lose access immediately and new clients start in sandbox.

Admins are warned before regenerating a connector key that other agencies share.

Agencies set to SSO only no longer accept password sign-in, and repeated failed sign-ins are rate limited.

The new Incidents API at /api/v1/incidents lets integrators create incidents, update fields, add narrative and cancel, using OAuth client credentials.

Requests from sandbox API clients are validated and recorded without anything being sent to CAD.

The public Developer Hub at /developers documents the API, its rules of use and its rate limits, replacing the Swagger page.

Additional fields sent with an API incident appear in the CAD narrative as name: value lines, with no per-agency setup.

API incidents are accepted for agencies that have no boundary file.

403 and 415 errors explain what was wrong.

CAD acknowledgements and closes no longer undo field changes made through the API.

The legacy create-incident endpoint and retired integration endpoints are removed; integrations use /api/v1/incidents.

Admin pages, user management and agency CAD maps now check the user's role and agency, not just that they are signed in.

Settings changes made in quick succession are all saved instead of some being dropped.

Business rule location checks no longer treat points as outside an area when its boundary file contains an empty shape.

On-site CAD connectors no longer drop and reconnect while the server is busy processing heartbeats.

AI abuse screening holds suspicious public reports in a quarantine queue for admin review, with an on/off setting per agency.

Global admins can edit the AI moderation prompt used for all agencies.

Content moderation works again after the AI model it used was retired.

The admin Log page loads quickly instead of timing out on large logs.

Editing a global business rule no longer crashes the page.

Routine front-desk and dispatch requests are no longer quarantined as abuse.

Releasing a wrongly quarantined report stops similar reports from being held again.

Fixed location validation rejecting valid addresses on incident reports. The 'specific location' check relies on an AI service that had stopped responding, which caused every entered location — even complete street addresses — to be turned away with 'You must enter an address, cross streets, or specific location name.' The check has been restored, and it now lets reports through if that service is ever unavailable so it can't block submissions.

Tow Company Phone Number — new required field on the tow report form captures the tow company's phone number separately from the driver's personal cell, giving CCIC operators a reliable company contact for callbacks. SMS confirmations still send to the driver's phone.

Agent Management — new tab on the Telephony page to view, edit, and manage ElevenLabs agent configurations directly from Spark

Direct prompt and tool editor with full diff preview before applying changes to ElevenLabs

Tool editor now captures the complete ElevenLabs tool schema including webhook URLs, secret references, request headers, body parameters, transfer destinations, and system tool configurations

Branch management — create branches, set traffic split percentages across branches, merge branches into main, and archive branches

Change set abstraction — all agent configuration changes (from QA review, direct edits, or rollbacks) are tracked with full before/after snapshots for audit and rollback

Rollback support — any applied change set can be rolled back to restore the agent to its previous state

QA analysis upgraded to Claude Sonnet 4 and now includes agent tools and first message in analysis context

QA analysis is now scope-aware — identifies the specific call scenario and classifies proposed changes as global or scenario-specific to avoid unintended side effects

QA review dialog restructured with persistent footer actions, branch targeting when applying changes, and inline traffic split for new branches

Conversation details dialog restructured with proper dialog layout and buffered action buttons

Consistent spacing and padding across all telephony dialogs — tab content, button groups, and dialog footers

PSAP phone overrides now support manually adding entries in Global Settings, not just auto-discovered PSAPs

Fixed occurrence time being off by one hour when the reported date falls in a different daylight saving time period than the current date

PSAP phone number overrides — global admins can set preferred contact numbers for any PSAP in Global Settings, replacing numbers returned by RapidSOS

Automatic PSAP encounter logging — the system tracks every unique PSAP encountered from RapidSOS lookups, with a searchable table in Global Settings

Out-of-jurisdiction phone numbers now use global overrides consistently across all report forms (Dynamic Report, Tow Report, and Configurable Form)

Fixed AdministratorAlertService failing to start in development mode when Redis is unavailable

Fixed business rule trigger types being misaligned after adding OnFormLoaded, causing existing rules to not fire correctly.

Fixed SMS consent and caller location status not appearing in CAD narrative.

Fixed two-way SMS failing when the caller texts dispatch first after incident creation.

Introducing the Integrations Hub! Administrators can now configure outbound webhook integrations to send incident data to third-party systems in real-time.

Integrations support API Key and OAuth2/JWT authentication methods with customizable payload templates.

Integration filtering allows triggering webhooks based on incident type, sub-type, or exclusion rules.

Integration logs provide detailed request/response history with retry tracking for troubleshooting.

Built-in connection testing validates endpoint connectivity before saving integrations.

Fixed critical issue where CAD incident ID was not being saved to incidents after acknowledgement from CAD connector.

Fixed critical business rules evaluation bug where rules would always return "None" due to fire-and-forget async pattern not awaiting completion.

Increased AI moderation timeout from 10s to 30s and improved error detection for truncated responses.

Fixed Data page not refreshing when incidents are acknowledged via "Push to CAD" button.

SMS consent information now included in CAD narrative for both Call for Service and Tow forms.

Increased SignalR client timeout from 90s to 120s to better tolerate network delays and prevent premature connection drops.

Reduced connection pruning check interval from 5 minutes to 2 minutes for faster detection of stale connections.

Added SMS alerts for administrators when connections are pruned due to stale heartbeats.

Fixed business rule time restrictions to properly evaluate in customer's configured timezone (Mountain, Pacific, etc.).

Form restriction messages now display specific times when forms are unavailable.

Improved multi-container heartbeat processing to prevent false connection pruning.

Enhanced connection alert suppression to reduce duplicate notifications.

Global Settings now include explicit "Save" button for improved control and user feedback when modifying global configuration.

Anonymous Keywords field is now properly bound and functional, allowing administrators to configure keywords for anonymous report identification.

Implemented Redis pub/sub for instant cross-container synchronization of global configuration changes, reducing propagation delay from up to 5 minutes to under 1 second.

AI moderation prompts now sync instantly across all containers, ensuring consistent content moderation behavior.

Added new APIs, including Artificial Intelligence call answering. Now, calls answered and processed by AI can create a CAD call!

Added additional message handling, logging, and error recovery to messaging between on-premise CAD connectors and Spark.

Resolved a bug where the "Push to CAD" button would successfully generate a CAD call, but would not show successful in the Spark interface.

Resolved several bugs in the Tow form.

Added ability for administrators to change the 'Method of Call Received' for the CAD alert method.

Added new business rule evaluation condition of Form Type (Call for Service, Tow, etc).

Added new business rule evaluation condition for day of week.

Fixed an issue where duplicates of the same incident would be created in CAD when the connector status changes.

Fixed an issue with AI evaluation models which would result in a false negative.

Customers in test mode no longer appear in the main page search.

Fixed a bug making it possible for incidents to be retrieved by the connector more than once.

Lots of great work under the hood!

Added functionality to make it easier to test business rule geography.

Minor styling improvements.

Completed Redis backplane which ensures message delivery from connector to API services even during maintenance windows, temporary network disruptions, etc.

Added new Business Rule Geography trigger of "Point in Radius". Administrators may now configure rules to trigger when a point is within a specified radius of a geographic location.

Added CAD Incident sync functionality. Administrators may now turn on/off the extraction, from CAD, of incident data which was not created by Spark. This feature does require an update to the on premise connector service.

Added ability to enable/disable administrative alerts.

Added ability to see the software version of on-premise CAD connector service.

Streamlined messaging to/from on-premise CAD connector service during incident creation.

Fixed an issue with map files displaying for administrators in the "Map Settings" section.

Added ability to configure CAD Health Condition alerting (requires update to on-prem service). Administrators can now elect to receive Health Condition details via email or SMS.

AI models powering some geography and business rule evaluations have been improved.

Business rules can now evaluate multiple geography conditions. For example, Rule #1 can evaluate if a point is within a wide area (such as a county), and Rule #2 can ensure the point is outside of municipalities.

Officially introducing support for RapidSOS! ECCs not connected via CAD can now elect to receive Spark reports via the RapidSOS portal.

Added support for CentralSquare Enterprise CAD's ability to process vehicle information into Supplemental Information (Vehicles).

Added ability to restrict attachments to authenticated users only.

Improved speed for RapidSOS integration (test only).

Resolved a bug preventing administrators from being able to reset a user's password.

Improvements to logging allowing for more accurate monitoring of connectivity between on-premise connectors and Spark.

Resolved an issue where details of an interaction would not display in the "Data" page alongside details of a created incident.

Added new indicator in administrator Alerts Settings which shows if the CAD connector is connected to the hub.

Added new field for the caller's location when not at the location of the report.

Added new Business Rule action type of "Deny Submission". Rule can be triggered when matching a submitter's IP Address, name, or phone number.

Added a new configuration setting to allow/disallow unacknowledged incidents (when the connector service is down).

Added ability to configure administrator alerts for when a CAD connector connects/disconnects, or there is an error.

Data from the sandbox (testing environment) is now separated from production data.

Added support for RapidSOS Alerts

Fixed a condition where the "Submit" button would continue to spin as if the form was submitting when there is no connection to CAD

Modified "I'm at this location" to be a toggle selector

Added ability to configure a max character count for the narrative

Added language auto detect for narrative

Fixed an issue with the date and time validating correctly to the user's local time

Improved overall speed of application, including when a new location is chosen and when the form is submitted

Added support for common name (premise name or similar) along with the address

Added a configurable field where the reporting party can indicate they are currently at the reported location

Added ability to enable Artificial Intelligence summarization of the narrative

Fixed an issue with Google Maps scripts not loading properly

Introducing Business Rules V2

Business rules are now even more configurable and dynamic with geographic lookups

The ability to upload GeoJson files has been added to the "Map Settings" tab of the Settings page

A map file lookup test has also been added to the Map Settings tab

Administrators now have the ability to test whether a business rule would be invoked based on the configured conditions

Business rule processing speed is also significantly improved with this update

Fixed an issue preventing proper validation of the location field

Various visual improvements to settings pages

Added ability to configure a Method of Call received for CentralSquare Enterprise

Added the ability to configure the banner text for the primary reporting form.

Added a new confirmation box when the user uses the "Use My Location" button.

Fixed an issue with several fields not showing the "*" for a required field.

Fixed an issue creating a false positive for spam which could in some cases prevent submission.

Added ability to enable a new field to gather contact preferences (for officer contact).

Added global business rule which does not allow form submission if the location is too vague, such as only the city/state.

Fixed an issue showing an incorrect Date/Time incident occurred.

Various bug fixes and improvements.

Added audit log trail for administrator configuration actions.

Added new business rule type to change the Incident Sub Type (problem nature) of a call based on AI analysis.

Added ability to make "Use My Location" field enabled/disabled.

Added a new tow-specific form which can be enabled by agency. Tow form allows drivers to take a picture of the VIN which will automatically fill in certain fields.

Various bug fixes and speed improvements.