What's New

Message list pages and GET /accounts/{account_id}/messages have been optimized, dramatically reducing load times for smaller and less-active accounts.

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.

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.

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.

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.

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.

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.

Contact API requests can now set outbound_disabled to prevent all outbound messaging to a contact. See the API documentation for more details.

Embedded inbox conversation lists and unread badges now use optimized queries, reducing initial load times and making unread counts much faster for larger accounts.

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.

Attempting to register an additional campaign for a sole proprietor account now returns a clear validation error instead of an internal server error.

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.

Messages throttled by a receiving carrier now report carrier_rate_limit with a clear explanation instead of an unknown delivery failure.

Usage calculations now allow additional time for large or uncached result sets, preventing the first usage-page request from timing out.

Projects in the Caller Reputation Profiles private beta can now manage profiles in both the API and HQ.

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.

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.

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.

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.

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.

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.

Contact search in the embedded inbox now limits initial results and correctly debounces input, making it much faster for accounts with large contact lists.

Projects in the Caller Reputation private beta can now submit caller reputation profile registration details through the API.

Inbound calls answered through an embedded phone or mobile client now use the lower client-call rate instead of the call-forwarding rate.

You can now retrieve an individual account using the new GET /accounts/{account_id} endpoint. See the Retrieve account endpoint in the docs for more information.