What's New

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.

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.

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.

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 and Federal Corporation Search. 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.

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.

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.

We have added an endpoint for listing all of the users in an account. See the documentation for the list users endpoint for more information.

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.

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 and list recordings endpoint for more information.

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.

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.

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.

Our existing campaign.approved webhook event 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 for more information.

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.

We have added a new API endpoint for moving a phone number to another account under your project.

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.

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.

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.

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.

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.

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.

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.

We've added a new endpoint for listing the campaigns in an account. For more information, see the documentation for the list campaigns endpoint.

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.

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 for more details.