Changelog¶
Stay up to date with the latest improvements, new features, and bug fixes in Outsprint.
February 2026¶
February 23, 2026¶
New Public Documentation Site
Launched the Outsprint documentation site with comprehensive guides for getting started, chat interface, CRM management, email integration, admin settings, and troubleshooting.
New Knowledge Base Integration
You can now publish a public-facing knowledge base for your customers. Articles are searchable and integrated with the AI assistant for intelligent support suggestions.
Improved HubSpot Migration Wizard
The migration wizard now auto-maps HubSpot custom properties and preserves pipeline probability values during import.
February 15, 2026¶
New Slack Integration
Connect your Slack workspace to receive CRM notifications in channels. Configure routing rules to send deal alerts, ticket updates, and task assignments to the right channels.
Improved Webhook Delivery Reliability
Webhook retry logic now uses exponential backoff with up to 5 attempts. Webhooks that fail for 50 consecutive deliveries are auto-disabled with an admin notification.
Fixed CSV Import Encoding
Fixed an issue where CSV files with non-ASCII characters were not parsed correctly during import.
February 8, 2026¶
New Custom Properties for Tickets
You can now add custom properties to ticket records, just like contacts, companies, and deals.
Improved Audit Log Filtering
The audit log viewer now supports filtering by source (Chat, Admin, API, Workflow) in addition to action type and user.
Fixed Notification Preferences
Fixed an issue where Slack DM notification toggles were visible even when Slack was not connected.
January 2026¶
January 25, 2026¶
New Forms & Lead Capture
Build embeddable web forms that automatically create contacts in your CRM. Forms support custom fields, spam protection, and GDPR consent checkboxes.
Improved Pipeline Configuration
You can now drag and drop stages to reorder them directly in the pipeline editor.
Fixed Session Timeout
Fixed an issue where session timeout settings were not applied consistently across all users in the organisation.