Squid Alerts Release Notes

February 22, 2021

  • New Company Verification Process - New companies are now required to verify their SMS phone number before sending any notification or reserving inbound phone numbers in Squid Alerts.

February 15, 2021

  • Create New Incidents - Incident no longer have to be generated from an alert. On the team's incidents page, my incidents, or the company wide incidents page there is now a button for "New Incident". Any incident in the New status will follow the team's escalation chain and send notifications. Incidents created with another status will not be processed by the escalation chain.
  • UI Improvements - Added assigned user column on the team and company incidents screens, removed padding on mobile, improve button color consistency.

February 8, 2021

  • Release Notes - You're looking at it.
  • My Incidents Screen - Users can now see and filter on all incidents that have been assigned to them. From the profile menu in the top right of the screen, select "My Incidents".
  • Bulk User Import - Administrators can add users to Squid Alerts by uploading an Excel file. The file provides options for name, email address, phone number, role, and whether or not the user should receive an invitation email. Bulk import is accessed on the Admin > Users screen.

February 1, 2021

  • Inbound SMS - Teams that have inbound phone numbers can now receive SMS messages. Inbound SMS messages can either be converted to an alert which will be processed by the team's routing rules (converted to an incident by default) or they can be directly forwarded to whomever is on-call.

January 25, 2021

  • Two-Factor / Multi-Factor Authentication - Administrators can require users in their company to have a secondary authentication mechanism when they login to Squid Alerts. Users logging in for the first time will be required to configure and verify their phone number to receive SMS messages. Each time they login, they will receive a temporary access code over SMS to verify their identity.
  • Team Links - Team managers can now add links to their team's dashboard. Links are a simple way for your team to share commonly used sites such as internal documentation.

January 18, 2021

  • Password Requirements - Administrators can now define custom password requirements for their company. Options include minimum password length and whether the password requires an uppercase, lowercase, numeric, or symbol. Existing passwords will not be affected until they are changed by the user.

January 11, 2021

  • Skipped Reason - Now, when you see a notification was skipped in the esclations of an incident, a reason is provided. Current reasons include: no resources for the stage (e.g. no one is on-call), the user was set to do not disturb, communication method not configured for the user (they haven't setup their phone number yet), flood protection limit reached, or your trial is expired.
  • Alternate Team Escalation - Some companies have a dedicated team that handles off hour incidents. Now team managers can setup another team's primary or secondary on-call in their escalation chain. If someone from another team acknowledges the incident, the incident will remain in the original team's queue.
  • Additional Country (Spain) - Partial functionality is now available in the Spain (+34) country code. Notification counts may be more due to increased costs of sending calls and SMS messages to Spain. Teams cannot currently reserve Spanish phone numbers.

January 4, 2021

  • All Incidents Screen - Users can now see and filter on all incidents across multiple teams. From the company menu, select "Incidents".
  • Additional Country (United Kingdom) - Full functionality is now available in the UK (+44) country code.