All the most recent updates and improvements to Surgehttps://surge.app/en-ushttps://surge.app/changelog/https://surge.app/changelog/Message list pages and `GET /accounts/{account_id}/messages` have been optimized, dramatically reducing load times for smaller and less-active accounts.Mon, 31 Aug 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where changing a phone number’s call handling could leave the previous configuration active for up to 15 minutes. Updates now take effect immediately.Fri, 28 Aug 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Tooltips now appear when controls receive keyboard focus, and the account switcher reliably stays above the rest of the page without passing clicks through to underlying content.Thu, 27 Aug 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Embedded phone integrations can now add `ring=false` to the iframe URL to disable Surge’s incoming ringtone when the embedding application provides its own.Thu, 27 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/HQ now has dedicated campaign list and detail pages. Eligible accounts can register additional campaigns and edit existing campaigns that are still open for changes.Thu, 27 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where an embedded phone could appear unregistered even though registration had already succeeded, then return an error when asked to register again.Tue, 18 Aug 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/The embedded phone can now transfer an active call to a contact or phone number. Headless integrations can also initiate transfers and receive structured success or error messages.Tue, 18 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Contact API requests can now set `outbound_disabled` to prevent all outbound messaging to a contact. See the [API documentation](https://docs.surge.app/api-reference/endpoint/contacts/create#body-outbound-disabled) for more details.Tue, 18 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Embedded inbox conversation lists and unread badges now use optimized queries, reducing initial load times and making unread counts much faster for larger accounts.Tue, 18 Aug 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Campaign registrations using a screenshot of a web-form opt-in flow can now explain why a screenshot was provided instead of a live form URL, helping carriers evaluate the submission correctly.Mon, 17 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Attempting to register an additional campaign for a sole proprietor account now returns a clear validation error instead of an internal server error.Mon, 17 Aug 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Sole proprietor campaign registrations now require a website URL in HQ and through the Accounts API. The URL is included when the registration is submitted to carriers, and must include enough information to establish business legitimacy.Fri, 14 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Messages throttled by a receiving carrier now report `carrier_rate_limit` with a clear explanation instead of an unknown delivery failure.Fri, 14 Aug 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Usage calculations now allow additional time for large or uncached result sets, preventing the first usage-page request from timing out.Fri, 14 Aug 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Projects in the Caller Reputation Profiles private beta can now manage profiles in both the API and HQ.Wed, 12 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/SIP trunk private beta projects can now select a SIP trunk as a phone number’s call handling method directly from the phone number page in HQ. This means you can fully set up SIP trunks in our UI without having to make API calls.Mon, 10 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Businesses in supported countries outside the United States and Canada can now register messaging campaigns using their local VAT or tax ID and international address. While we remain focused on the US and Canadian markets, this allows customers whose businesses are registered outside of these jurisdictions to send messages in the US and Canada.Mon, 10 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/When undeliverable-number blocking is enabled, direct and scheduled sends to destinations already known to be unreachable now return an `undeliverable` error before a message is created, so the send is not billed.Thu, 06 Aug 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/You can now use our embedded form for verifying a caller ID number. Outbound calls can use the verified number as the display number on calls from the embedded phone component.Tue, 04 Aug 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where some territories sharing a country code—such as Guernsey, Jersey, Curaçao, and Sint Maarten—could inherit the wrong international SMS price.Sat, 01 Aug 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Contact detail pages now show every message sent to or received from the contact across all conversations, including message IDs and statuses. You can select a message to open its detail page.Fri, 31 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Contact search in the embedded inbox now limits initial results and correctly debounces input, making it much faster for accounts with large contact lists.Fri, 31 Jul 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Projects in the Caller Reputation private beta can now submit caller reputation profile registration details through the API.Fri, 31 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Inbound calls answered through an embedded phone or mobile client now use the lower client-call rate instead of the call-forwarding rate.Mon, 27 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/You can now retrieve an individual account using the new `GET /accounts/{account_id}` endpoint. See the [Retrieve account endpoint](https://docs.surge.app/api-reference/endpoint/campaigns/get) in the docs for more information.Fri, 24 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Sole proprietors can now resend a brand verification code using `POST /accounts/{account_id}/brand_verification_messages.` See the [Resend Brand Verification Message endpoint](https://docs.surge.app/api-reference/endpoint/campaigns/resend-brand-verification-message) in the API documentation for more information.Mon, 20 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/API authentication now uses a short-lived cache and batches API-key activity updates, reducing database work on each request. Last-used timestamps may take a few minutes to update, but this should provide lower latency and better reliability for our API.Mon, 20 Jul 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/We redesigned the notification email templates with the updated brand, typography, and visual system.Sat, 18 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Sole proprietor brand verification texts now use the platform name for white-label projects instead of identifying every registration as Surge.Sat, 18 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/SIP trunk private beta projects can now list, view, create, edit, and delete SIP trunks directly in HQ.Fri, 17 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/The campaign registration form now collects the business’s brand name separately from its account and legal business names.Thu, 16 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/New webhook events are now prioritized over retries, preventing failing endpoints and retry backlogs from delaying deliveries to healthy endpoints.Tue, 14 Jul 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Surge now prevents messages from being sent through released phone numbers. The embedded composer is also disabled when its sender is no longer active.Tue, 14 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/You can now browse available US and Canadian phone number inventory, retrieve an individual phone number, and purchase a specific number through the API. See the API documentation for more information: * [List available numbers](https://docs.surge.app/api-reference/endpoint/phone-numbers/list-available-numbers) * [Purchase phone number](https://docs.surge.app/api-reference/endpoint/phone-numbers/purchase)Mon, 13 Jul 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Call detail pages now resolve call-leg participants into contacts, Surge phone numbers, and users, with clearer labels and links to related records.Mon, 13 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Phone number API responses and phone-number webhook payloads now include a `campaign` object with the campaign ID and current attachment status. The existing `campaign_id` field is deprecated.Thu, 09 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Verification destination rate limits are now scoped to each project, preventing activity in one project from consuming another project’s allowance for the same destination.Wed, 08 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/`voicemail.received`, `call.ended`, and `recording.completed` webhook events now include the Surge phone number ID along with the `to` and `from` numbers. See the documentation for more information: * [Voicemail received event](https://docs.surge.app/api-reference/webhooks/voicemail/received) * [Call ended event](https://docs.surge.app/api-reference/webhooks/call/ended) * [Recording completed event](https://docs.surge.app/api-reference/webhooks/recording/completed)Mon, 06 Jul 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue that could prevent customers from seeing their previous conversations in the embedded support chat.Mon, 06 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Fixed a race condition that could return a `422` when multiple messages were sent simultaneously to the same new contact or conversation.Thu, 02 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Creating a campaign with a TCR ID that is already linked now returns `409 Conflict` instead of a generic validation response.Thu, 02 Jul 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Webhook event history queries were optimized to improve page load times, especially while the database is under heavier load.Wed, 01 Jul 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/You can now pass a settings object when creating a message to override account-level settings for that message. Currently, `settings.link_shortening` supports `"enabled"` and `"disabled"`.Tue, 30 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We redesigned the login, registration, email confirmation, forgot password, and reset password pages with the updated Surge visual design system. More of HQ to come!Sat, 27 Jun 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/SIP trunk private beta projects can now list, retrieve, update, and delete SIP trunks through the API, in addition to creating them.Fri, 26 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/HQ now has call list and call detail pages, including call direction, status, duration, contact, phone number, and call leg details.Tue, 23 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Phone number call handling can now use audio files for voicemail greetings.Tue, 23 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where monthly campaign fees could be counted once per campaign submission instead of once per campaign.Mon, 22 Jun 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Message senders are now easier to identify in the inbox and embedded conversation views.Fri, 19 Jun 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where request and response bodies could disappear from API logs when filtering.Wed, 17 Jun 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/You can now update a phone number through the API, including its display name and attached campaign. See the documentation for the [update phone number endpoint](https://docs.surge.app/api-reference/endpoint/phone-numbers/update).Mon, 15 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Accounts can now create and retrieve call signing profile registration status through the API. This means that you can now register so that we can send phone calls on behalf of you and your customers with an A-level STIR/SHAKEN attestation.Mon, 15 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Inbound vCard attachments now render as contact cards in message views instead of appearing as generic files. The API also has a `contact` attachment type now to indicate when an attachment is a vCard.Mon, 15 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Fixed a race condition that could move delivered messages back to `sent`. All affected messages have been updated.Fri, 12 Jun 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Verification requests to reserved 555 numbers (eg +18015551234) now return an immediate validation error instead of failing silently.Wed, 10 Jun 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Platform admins can now remove team members and cancel pending invites from the Team page.Mon, 08 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Usage and invoice calculations now split campaign and phone number pricing, which lowers phone number pricing for accounts with multiple numbers on one campaign. Updated phone number and campaign pricing can be seen on our [pricing page](https://surge.app/pricing/#phone-numbers).Sat, 06 Jun 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Surge now blocks sends earlier when the selected sender cannot be used for a destination country, returning an `invalid_sender` error instead of failing later.Fri, 05 Jun 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Projects in our SIP trunking private beta can now create their own SIP trunks through the API. SIP trunks support both IP-based and credential-based authentication, and once created you can attach a phone number to a SIP trunk as a call handling method.Mon, 01 Jun 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Previously, if you submitted a campaign to us through either the API or HQ, we would charge you for it. Now we will only bill you for the campaigns that are sent through to the carriers.Sun, 31 May 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We've added optional monthly message limits that cap the number of outbound messages a project can send each month based on its subscription plan. These limits are high enough that most accounts will never see them, but they will prevent unintentional runaway spend or abuse. If you'd like to have the limit lifted for your account, please reach out to support.Fri, 29 May 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/You can now release a phone number through the API with the new `DELETE /phone_numbers/{phone_number_id}` endpoint. See the [release phone number endpoint](https://docs.surge.app/api-reference/endpoint/phone-numbers/release) in the documentation for more details.Tue, 26 May 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Fixed an issue where re-purchasing or re-adding a phone number that had previously been released could cause conflicts between the released and active versions of the number.Tue, 26 May 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/We've added new API endpoints to streamline onboarding for AI agent platforms. `POST /agents/v0/projects` provisions a passwordless user, platform, account, and API key in a single call, along with a demo phone verification, and `POST /agents/v0/phone_verifications/{verification_id}/checks` confirms the SMS verification code to finish setting up a demo participant. See our new [skills file](https://surge.app/skills.md) for instructions.Fri, 08 May 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Following our undeliverable number detection, projects can now choose to bypass the undeliverable-number check. This is useful if you'd rather attempt delivery to numbers that have previously failed than risk blocking a message that might still get through. Reach out to support to enable this for your project.Thu, 07 May 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/In order to prevent abuse through demo numbers, Surge now prepends `[SURGE DEMO]` at the beginning of any messages sent through the demo number. This way recipients will be able to see that it's a demo message, and demo numbers can't be used for smishing attacks.Sat, 02 May 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We added a new endpoint for listing all of the accounts in your project. See the [documentation for the list accounts endpoint](https://docs.surge.app/api-reference/endpoint/accounts/list) for more details.Fri, 01 May 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Projects can now disable public attachment access and require authenticated access for attachment files. This goes hand in hand with our [get attachment file endpoint](https://docs.surge.app/api-reference/endpoint/attachments/get_file) that we shipped last week.Thu, 30 Apr 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/API logs can now be filtered by success or failed status, making it easier to investigate request history.Tue, 28 Apr 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Queries for our embedded inbox component were optimized, resulting in a 68% reduction in average load time. You should now see much faster page loads and updates.Sat, 25 Apr 2026 00:00:00 GMTperformancehttps://surge.app/changelog/https://surge.app/changelog/Saved usage reports now use the pricing plan that was active during the report period instead of always showing current pricing. This should make historical usage reports more accurate.Wed, 22 Apr 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Phone numbers can now be named, and the name will be visible across the UI, API, and webhook payloads. See the [purchase phone number endpoint](https://docs.surge.app/api-reference/endpoint/phone-numbers/purchase) in the documentation for more details.Tue, 21 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/While we've had multi-factor auth as an option for a long time, we now have the ability to enforce MFA in projects. If you would like to require MFA for all members of your project, please reach out to support.Mon, 20 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/A new authenticated API endpoint is available for retrieving attachment files, providing a more secure alternative to public attachment URLs. See the [get attachment file](https://docs.surge.app/api-reference/endpoint/attachments/get_file) endpoint in our documentation for more details.Wed, 15 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Surge can now automatically warn and log users out after 15 minutes of inactivity for stronger account security. Please reach out to support if you would like to have this enabled for your account.Mon, 13 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/`link.followed` webhook events now include the full message object instead of only a message ID. This means any metadata stored on the message, along with all other message details, will be present on those webhook events to make it easier for you to track conversion for your messages and blasts.Fri, 10 Apr 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Projects can now manage multiple named AI agent API keys and choose which key to use when configuring a phone number integration. This allows you to set up multiple AI agent platforms within your project or even within the same account.Tue, 07 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Surge now tracks permanently undeliverable destinations and blocks future sends to numbers that are known to fail, with sender-type-specific handling for local, toll-free, and short code traffic. This should save you money as you will no longer be charged for those messages.Tue, 07 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Inbound MMS attachments with unrecognized MIME types no longer fail during ingestion. Surge now stores them without guessing a file extension.Mon, 06 Apr 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Campaigns created through the API can now be updated with a new `PATCH /campaigns/{campaign_id}` endpoint. See the [update campaign endpoint](https://docs.surge.app/api-reference/endpoint/campaigns/update) in the documentation for more details.Fri, 03 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/The API now supports creating audiences and adding contacts to audiences, making audience management available without using the UI. See the [create audience](https://docs.surge.app/api-reference/endpoint/audiences/create) and [add contact to audience](https://docs.surge.app/api-reference/endpoint/audiences/add_contact) endpoints in the docs for more details.Wed, 01 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/When sending a Blast through our API, it was already possible to provide the phone number from which the Blast should be sent. HQ didn't previously support that feature though, so we've now added a dropdown so that you can select which phone number should send the Blast when sending through our UI.Wed, 01 Apr 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've now added Retell as a supported AI agent platform for Voice. On the phone number settings page, you can select to have inbound calls handled by an AI agent, then select Retell as your platform of choice. By providing your Retell API key, we will import your Surge phone number into Retell for you so that your Retell agent can make and receive calls using your Surge phone number.Tue, 31 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/For phone calls through the ElevenLabs agent platform, we had some issues where calls were cut short when we deployed a change to our servers. That has now been fixed, so ElevenLabs agent calls should now be more reliable.Mon, 30 Mar 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/While Canadian accounts could previously be created manually through HQ, we've now added the ability to create Canadian accounts through the API as well. Accounts in Canada will need to have a valid Canadian Business Number instead of an EIN. You can validate the business number beforehand using [Canada's Business Registries](https://ised-isde.canada.ca/cbr-rec/en/search) and [Federal Corporation Search](https://ised-isde.canada.ca/cc/lgcy/fdrlCrpSrch.html). If the business was registered provincially or doesn't appear in either of the registries, a special registration process will be needed which requires additional fees. Reach out to support for more information.Thu, 26 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've updated the embedded components to use message clustering similar to the way iMessage does it. Messages sent within a minute of each other will be grouped together with less spacing than normal, and messages sent within an hour of each other will be grouped under a date/time header. This helps to declutter the conversation view and provide a more familiar interface for customers. Right now this new functionality is disabled by default. If you would like it enabled for your project, please reach out to support. Once we've tested it thoroughly, we will enable it for all projects.Tue, 24 Mar 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/For users in our private beta for recording calls, you now have the ability to always record outbound calls as well as inbound calls. In the phone number settings, you will see a new "Record outbound calls" checkbox right below the "Record inbound calls" checkbox. Currently this functionality can only be enabled or disabled for all calls. We have no way to override it on a specific call yet.Tue, 24 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We have added an endpoint for listing all of the users in an account. See the [documentation for the list users endpoint](https://docs.surge.app/api-reference/endpoint/users/list) for more information.Mon, 23 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/When an area code was provided to the API for purchasing a phone number, and that area code is associated with a country or territory outside the US (like the `345` area code for the Cayman Islands), our system was returning an unknown error. We will now handle that properly and return an error explaining that the area code is not valid.Sun, 22 Mar 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/For projects in the beta for our embeddable softphone, you can now route inbound calls to a list of multiple users instead of just a single user. When you do this, all users' softphones will ring simultaneously, and the first user to answer the call will receive it.Fri, 20 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've added new endpoints for getting a recording or listing all the recordings in an account. This will be especially helpful for making sure that you've deleted all recordings if you don't want to pay Surge to store them for you. See the documentation for the [get recording endpoint](https://docs.surge.app/api-reference/endpoint/recordings/get) and [list recordings endpoint](https://docs.surge.app/api-reference/endpoint/recordings/list) for more information.Fri, 20 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Some code paths for creating a message weren't saving message metadata properly, and the metadata wasn't being returned in the API responses. This has been fixed so that message metadata will now work as expected.Wed, 18 Mar 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Our embedded softphone component will now take a `phone_number_id` parameter to allow you to specify the phone number from which any outbound calls should be made.Mon, 16 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Our existing [`campaign.approved` webhook event](https://docs.surge.app/api-reference/webhooks/campaign/approved) notifies you when a campaign has been approved, but each phone number needs to be attached to a campaign as well before it can begin sending. Now we've added a `phone_number.attached_to_campaign` webhook event as well so that you can be notified when phone number attachment is complete. See the [documentation for the new webhook event](https://docs.surge.app/api-reference/webhooks/phone_number/attached_to_campaign) for more information.Wed, 11 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/For platform customers with many accounts, finding the account you needed would often require ⌘+F to make it work. We've now added a search input on both our accounts page and the account switcher on our other pages so that you can easily find the account you need. In addition, we've changed both the switcher and the accounts page to display the accounts in alphabetical order so that you can more easily scan through them.Fri, 06 Mar 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We have added a new API endpoint for moving a phone number to another account under your project.Tue, 03 Mar 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/For our customers in Canada (or who have their own customers in Canada), you will now be able to purchase Canadian phone numbers both through HQ and our API. In HQ you will need to switch the country in the picker on the page for purchasing a phone number, and then you can also search for Canadian area codes. With our API, you will need to provide a Canadian area code, and then if we have any inventory in that area code, the number will be purchased.Thu, 26 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Since adding blasts and segments in 2024, we haven't made many improvements to it. It's been a long time coming, but we finally added pagination to the audience contacts page in HQ so that the page will load a lot faster and not crash your browser if you have an audience with thousands of contacts.Wed, 25 Feb 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/For those of you using segments to segment the contacts in your account, we have now renamed segments to audiences. This is because segments is also used to refer to SMS segments, and we wanted to separate the terms to make it easier to clarify what was being discussed. There are no breaking changes to the API because we have not yet exposed endpoints for segments, but we will create new audience endpoints soon.Wed, 25 Feb 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We just added a new billing settings page. By clicking your name in the bottom left corner of the screen on desktop, or your avatar in the top right on mobile, you can then select "Billing." This page will allow you to view and download your past invoices, change or cancel your usage commitment, or update the payment method on file for your project.Tue, 24 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Our UI is now set up to enable Canadian entities to register campaigns through the dashboard. The necessary changes will be made to the API as well in the near future.Mon, 23 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've added a password visibility toggle to the login, registration, and change password screens so that you'll be able to see your password if necessary.Mon, 23 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've added a new endpoint for listing the campaigns in an account. For more information, see the [documentation for the list campaigns endpoint](https://docs.surge.app/api-reference/endpoint/campaigns/list).Fri, 20 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We previously added a `metadata` field to messages to allow you to pass information from your system when sending a message. However, we forgot to add that to the message webhooks (`message.received`, `message.delivered`, `message.sent`, and `message.failed`). That will now be included on those webhooks.Fri, 20 Feb 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Pages where no user was logged in previously used light mode by default, whereas pages with a logged in user would use dark mode. Sorry for burning your eyes. We will now use your system theme everywhere in HQ.Tue, 17 Feb 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/The attachment `type` field was previously listed as a string in our OpenAPI spec. We've now updated that to be an enum so that it's clear what the possible values are. See the [documentation for the attachment type field](https://docs.surge.app/api-reference/endpoint/messages/get#response-attachments-items-type) for more information.Mon, 16 Feb 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We've now added an endpoint to allow you to delete recordings. This will allow you to remove them from Surge's storage so that you won't be billed for them, or in case you want them deleted for privacy reasons. See the [documentation for the delete recording endpoint](https://docs.surge.app/api-reference/endpoint/recordings/delete) for more details.Mon, 16 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Historically we've sent emails directly to our email provider, but we were seeing several issues where their server didn't accept the email and it never got sent. We've now cloned our SMS messaging queue infrastructure for emails so that failed emails will automatically be retried, and we can guarantee that email notifications are delivered at least once.Fri, 13 Feb 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/We now allow you to record your incoming calls. By enabling this feature the call will be recorded and we will send you a `recording.completed` webhook as soon as the recording has been processed and stored. You can then download the recording. Please note that you are responsible for compliance with federal and state laws surrounding recording phone calls.Tue, 10 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/You can now export your usage as a CSV. While this won't be a big deal for those of you with single-account projects, for our customers with many accounts, this will allow you to get the breakdown of line items for all of your accounts in a single CSV so that you can easily break down usage by accounts for attributing costs. Let us know if there's anything else you'd like to see in that CSV or anywhere else you'd like to see similar export buttons.Tue, 10 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We added a new endpoint for getting a campaign. This will allow you to check the details of a campaign that you've previously submitted, as well as check the status of the campaign. See the [documentation for the get campaign endpoint](https://docs.surge.app/api-reference/endpoint/campaigns/get) for more details.Sat, 07 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Verifications still require that recipients be able to opt out of receiving messages. In the event that a Verification is created and the recipient has opted out of receiving messages, we will now return an error response with instructions for the recipient to opt back in, rather than failing silently as we did before. An error response will look something like this: ```json { "error": { "type": "opted_out", "message": "This number has opted out of receiving verification messages. Send START to (801) 555-1234 to opt in again." } } ```Sat, 07 Feb 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/For our customers making outbound calls, we can now register your business with the carriers to avoid the "Spam Likely" label on outbound calls.Wed, 04 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Sometimes you or your customers would rather handle incoming calls asynchronously rather than in the moment a customer calls. We've now shipped voicemail in beta to allow you to receive voice messages from callers. By enabling voicemail on a phone number, we allow you to provide a greeting message. When someone calls your number, they will hear the greeting and be given the opportunity to record a message for you. We will then send you a `voicemail.received` webhook to let you know that the voicemail was received and is ready for download.Tue, 03 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've added a new endpoint for listing all the contacts in an account. See the [documentation for the list contacts endpoint](https://docs.surge.app/api-reference/endpoint/contacts/list) for more details.Sun, 01 Feb 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We've added a new endpoint for listing all the messages sent and received from an account. See the [documentation for the list messages endpoint](https://docs.surge.app/api-reference/endpoint/messages/list) for more details.Sat, 31 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Messages with attachments aren't required to have a message body, and messages aren't required to be associated with a blast. We previously had both fields in our OpenAPI spec and our SDK types show that a string would always be returned, but we have now updated that to allow string or null to reflect the actual behavior of the API.Fri, 30 Jan 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/We've added a new endpoint for listing all the phone numbers in your account. See the [documentation for the list phone numbers endpoint](https://docs.surge.app/api-reference/endpoint/phone-numbers/list) for more details.Mon, 26 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Whenever changes were needed on a toll-free verification, we displayed that on the phone number page, but we didn't provide a link to allow you to make those changes. We now include a button that links to the form where you can make the necessary changes.Sun, 25 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Blasts previously would always be sent from the default phone number on the account sending the blast. We added a `from` field which allows you to provide the phone number from which the blast should be sent. This should be helpful for users with multiple phone numbers in a single account. See [the docs for creating a blast](https://docs.surge.app/api-reference/endpoint/blasts/create#body-from) for more details.Sun, 25 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/We added a `blast_id` field to the message schema so that anywhere that our customers who use blasts will be able to more easily track all of the messages sent by a blast. See [the docs for messages](https://docs.surge.app/api-reference/endpoint/messages/get#response-blast-id).Sat, 24 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Once an SMS autoresponse message was set, the form on the phone number settings page would hide itself when you attempted to change it. This made it impossible to edit the autoresponse message. We've fixed this issue so that the form remains visible, allowing you to edit it once it's been set.Thu, 22 Jan 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/Previously when an invalid id was passed to the [embeddable unread count component](https://docs.surge.app/ui/components/unread-count), the filters would just be ignored, and the component would show the count of all messages the user could view but hadn't read. We have now fixed this behavior so that if an invalid filter id is provided, the component will hide the unread count entirely, similar to how it behaves when the user has no unread messages. This change helps prevent confusion so that it won't appear that there are unread messages when the filters are not valid.Wed, 21 Jan 2026 00:00:00 GMTbugfixhttps://surge.app/changelog/https://surge.app/changelog/We now support attaching custom metadata to messages sent via the API. Like the metadata fields on Contacts and Users, this allows you to store additional information relevant to your application. Metadata can be used for filtering, reporting, tracking, and analytics. The metadata field allows you to attach up to 50 key-value pairs to a message, with each value being a string up to 500 characters long. For more information, see the documentation for the [Create message endpoint](https://docs.surge.app/api-reference/endpoint/messages/create#body-one-of-0-metadata).Sun, 18 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/By default, any links included in messages sent through our platform are shortened to better fit within a single SMS segment. These links are also tracked to provide insights on user engagement. Historically we've only shown statistics about link clicks within our dashboard and the embedded inbox component. With this update, we've introduced a new `link.followed` webhook event that notifies you whenever a recipient follows a tracked link. For more information, see the documentation for the [link followed webhook](https://docs.surge.app/api-reference/webhooks/link/followed).Sun, 18 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Users can now be deleted via the API using `DELETE /users/{user_id}`. Deleting a user removes their access to any any embedded UI components, and they will no longer show up as targets for incoming calls. Any messages sent by that user will still show the user's name as the sender. For more information, see the [documentation for the delete user endpoint](https://docs.surge.app/api-reference/endpoint/users/delete).Thu, 15 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/You can now filter API logs by request ID, making it easier to trace specific requests and debug issues. This also makes it so that you can link to individual log entries directly for sharing with your team or with Surge support.Tue, 13 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Toll-free numbers will now require business information for verification. This matches the requirements for local numbers and helps to prevent spam from application-to-person messaging. The carriers are requiring this change to be implemented for all SMS APIs before February, so we've added these fields now to ensure compliance ahead of time. Now when registering a toll-free number, you'll be prompted to provide the following fields: * Business Type (sole proprietorship, corporation, LLC, etc.) * Legal Business Name (as registered with the IRS) * EIN (Employer Identification Number) Sole proprietors will still be able to register toll-free numbers without needing an EIN, but all other business types will need to provide this information for verification.Mon, 12 Jan 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Accounts can now be archived both from the dashboard and via the API. Archiving an account removes it from the account list, releases all phone numbers in the account, and deactivates any campaigns in the account. After an account is archived, messages and other resources can no longer be created in the account. Please note that this will not delete the associated data. To permanently delete an account and its data, please contact Surge support. ## Dashboard To archive an account from the dashboard, navigate to the account settings page and look for the "Archive" button in the top right corner of the page. ## API Accounts can be archived from the API using the `DELETE /accounts/{account_id}` endpoint. See the [API documentation](https://docs.surge.app/api-reference/endpoint/accounts/archive) for more information.Sun, 11 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Webhook endpoint URLs can now be up to 2048 characters long, accommodating more complex configurations and integrations.Fri, 09 Jan 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/The embeddable phone component can now receive incoming calls. This allows users to take calls directly within the embedded UI, enhancing the communication experience.Fri, 09 Jan 2026 00:00:00 GMTfeaturehttps://surge.app/changelog/https://surge.app/changelog/Carriers have begun enforcing the requirement that a terms and conditions URL be provided when registering a number to be able to send SMS. While we were previously accepting a terms and conditions URL for campaigns registered via the API, we have now made this a required field for all new campaign registrations, and we've added a new screen in the dashboard to allow users to provide this URL when registering a new campaign. This screen also contains boilerplate terms and conditions that you can host on your site in order to be compliant.Fri, 02 Jan 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/Rather than displaying a generic error message when something goes wrong on our servers, we've implemented a custom 500 error page that provides a little more direction. Hopefully you never get the chance to see it, but it will be slightly more delightful when you do.Fri, 02 Jan 2026 00:00:00 GMTimprovementhttps://surge.app/changelog/https://surge.app/changelog/You can now provide a `phone_number_id` parameter to the Inbox component to tell it to only show conversations associated with a specific phone number. This is great for use cases where you have multiple phone numbers and want to embed the Inbox component for each individual number separately. See the [Inbox component documentation](https://docs.surge.app/ui/components/inbox#installation) for more details.Thu, 01 Jan 2026 00:00:00 GMTfeature