What's New

Accounts, Phone Numbers, and Contacts tables now have reliable row navigation in Safari, fixing an issue where the final row’s click target could stretch across the page and interfere with other controls.

Project admins and managers can now include a brand name in Verification texts sent from an account.

Create signed user tokens with read_only: true using POST /users/{user_id}/tokens to provide access to embedded conversations, inboxes, and unread counts without allowing messages, read-state changes, contact edits, archiving, or calls. Restrictions are enforced server-side while search, navigation, history, and live updates remain available.

Automatic SMS-to-MMS conversion now runs only for recipients in the US, Canada, and Australia. Long text messages to other countries remain SMS instead of being routed through unavailable MMS service.

Direct, scheduled, and blast sends from US or Canadian local numbers without a completed campaign attachment, or toll-free numbers without an approved verification, now return unregistered_number before creating a message.

The embedded phone now includes an in-call keypad for navigating automated phone systems. Host applications can also send tones with send-digits and receive dtmf-error events when a request fails.

New and reconnected Vapi integrations now use Surge’s authenticated SIP routing. Failed setup attempts restore the phone number’s previous routing, reducing partial configurations and interrupted call handling.

Organizations in 14 additional countries can now complete carrier registration through HQ or the API using numeric VAT or tax IDs, bringing self-serve support to all 41 international countries accepted by The Campaign Registry.

Surge now applies the correct toll-free multipart limits to messages sent to the US and Canada, keeping Smart encoding, SMS-to-MMS selection, segment estimates, billing, and HQ previews aligned.

Surge now consistently uses projects across HQ, public URLs, and IDs. Project IDs use the prj_ prefix, while existing plt_ IDs and /platforms/... URLs remain compatible and redirect to their /projects/... equivalents. While we have no immediate plans to get rid of the redirects, we would recommend updating any bookmarks to avoid future disruptions.

The Australian phone number registration form now accepts familiar local contact-number formats such as 04... and converts them to E.164 automatically, so customers no longer need to enter the +61 form manually.

Campaign API responses now include account_id, and campaign.approved webhook data includes the same value as data.account_id, making it easier for integrations to associate each campaign with its owning account.

Phone Numbers and Contacts in HQ now offer responsive tables with search, A–Z or Newest ordering, pagination, and clearer empty states. Account Messages also surfaces contacts, message previews, direction, status, attachments, and relevant Surge-number context for faster scanning.

The Accounts page in HQ has been redesigned for large projects with 25-account pagination, exact account ID search alongside existing name search, a responsive table, accessible result updates, and clearer empty and account-creation states.

The embedded conversation and inbox now explain when sending is unavailable because a recipient opted out, has an invalid phone number, or has outbound messaging disabled. Notices update as restrictions change while preserving conversation history and the current selection.

PATCH /campaigns/{campaign_id} now properly accepts partial updates while preserving omitted fields. Send an empty object or no request body to resubmit the stored campaign details, while supplied arrays replace their stored values and explicit clears remain subject to registration validation.

Project managers and admins can now enable or disable Smart encoding from Account Settings. It replaces compatible Unicode characters when doing so reduces SMS segments, helping lower costs across direct sends, blasts, scheduled messages, keyword replies, autoresponses, and initial messages while preserving URLs and unsupported characters.

The embedded phone now renews its connection before credentials expire and restores registration after browser sleep, network interruptions, or page reconnects. Incoming and active calls remain intact while the phone recovers.

New and reconnected Vapi integrations now preserve the Surge phone number that a caller dialed, ensuring calls reach the intended Vapi phone-number configuration.

Inbound calls to embedded phones that reach voicemail or end before anyone answers now report no_answer instead of completed in call records and call.ended webhooks.

New Retell connections now use Surge’s encrypted SIP routing, bringing call metadata into Surge sooner and making setup more resilient to partial failures.

Sole proprietor campaigns awaiting brand phone verification now appear under Needs Attention with a Pending OTP status, and you can request a new verification code directly from campaign details.

10DLC campaign registrations using text-message opt-in now require an image showing how the phone number and consent terms are advertised.

Message objects returned by the API and included in message-shaped webhook payloads now contain a nullable failure_reason, making failed deliveries easier to diagnose without relying solely on message.failed events.

Message details in HQ now include a delivery timeline, sender and recipient addresses, protocol, encoding and segment information, carrier details, failure information, and an itemized message cost when available. Long messages and attachments are also easier to inspect.