In Case You Missed It: WLC’s September Releases

White Label Communications (WLC) is not just a provider but an enabler — enabling our partners to build off our solution to meet specific customer needs. We can’t dream up all the scenarios a customer is going to have, but we can make it easier for our partners to meet those growing needs.

In case you missed it, September was about just that — three releases, all built to solve problems you’ve told us about and enabling you to tailor solutions around what your customers are asking for and what you’re seeing in the marketplace. Here’s what shipped, why it matters, and how to start using it today.

SIP URI: Connecting Atlas to Voice AI Agents

Voice AI agents only matter if they can answer the phone. That’s what SIP URI does — it’s the on-ramp and off-ramp between Atlas and virtually any voice AI agent service on the market. You pick the vendor. Atlas carries the call data.

Here’s the call flow: a call hits Atlas, routes out via SIP URI to your chosen voice AI agent service, and that service hands it back through a SIP Refer header — to a group, a device, an auto attendant, wherever it needs to land. The agent gets access to the same tools a human would use: CRM, calendar, support systems, email, SMS.

What this looks like at work:

  • Scheduling: dental and medical practices using agents to check calendars, book appointments, and send text confirmations.
  • MSP help desk: verifying caller identity, opening PSA tickets, and handling resets without a human on the line.
  • Intake requests: using an after-hours agent to collect caller details and write them straight into a CRM.
  • Missed call agents: replacing the voicemail box entirely. Ring groups go unanswered more than anyone wants to admit. Instead of a voicemail nobody checks, the agent captures the callback number, sends a text, and books the appointment on the spot.

We tested four platforms against Atlas, and each serves a different strategic need:

  • ElevenLabs: best-in-class voice quality and multilingual support. Highly technical and highly capable, but it demands a developer’s attention.
  • Retell AI: the easier build. Strong transfer handling, webhooks, and post-call analysis, backed by a real support team and a pro services shop if you need help building agents from scratch.
  • Reception AI: built on ElevenLabs, packaged for speed. No code, no developer, live in minutes. The right call when you need a turnkey receptionist, not a custom build.
  • Vida: a private-label option. Built by a team with deep telecom roots, it can run under your own brand if you want customers logging into a platform that looks like yours, not a third party’s.

Setup takes minutes, with no special equipment or complicated configuration. Add a connection in Atlas, route calls to it like you would any other destination, and give every user their own AI-powered voicemail replacement if you want it.

Why build this instead of a native Atlas voice AI agent? We’re building that too. But you shouldn’t have to wait on our roadmap to put this in front of customers now — SIP URI gets you there today.

Call Recording APIs: Built for the AI Pipeline Behind the Call

Transcription and AI pipelines don’t run on good intentions. They run on access to the data. That’s what the new call recording API delivers — direct MP3 downloads, programmatic access to metadata, and a completed integration with Xarios that lets you pull or stream recordings into the analytics platform you’re already using.

Six new endpoints are live:

  • List recordings
  • Get recording by call ID — pulled directly from the call detail record
  • Edit recording — update tags and notes, the same actions available manually in Atlas today
  • Get recording metadata — phone number, duration, inbound or outbound
  • Download/stream recording
  • Delete recording

Permissions follow the same roles already governing call recording access in Atlas. If you’ve got 30 users and no interest in managing 30 API keys, set up a single global user with access to the organization’s recordings — or a defined subset — and pull everything through one credential.

The use cases line up with what partners are already trying to build: AI transcription pipelines, CRM logging, embedded app streaming for things like in-platform voicemail playback, and now, full Xarios integration for partners already using it for analytics and reporting.

Full documentation — including curl, PHP, Node, and Python examples — is live now at docs.atlasapi.net. Expect a steady release cadence over the next six months, with more documentation landing as new APIs ship.

EdgeMarc Support in Atlas Aware: A Real Migration Path, Not a Dead End

EdgeView hasn’t been updated in years. Edgewater Networks was acquired by Ribbon, and the product was sunset. We kept EdgeView running for thousands of partners anyway, because pulling the rug out with no replacement isn’t how we operate. But end-of-life is end-of-life. We can’t support a product that no longer receives updates.

So we rebuilt it. Atlas Aware — the monitoring platform that came out of last year’s Intelitrex acquisition — now supports EdgeMarc devices directly. Reachability, device health, call quality monitoring, MOS thresholds, alerting by email or SMS: everything EdgeView did, Atlas Aware does now, with WAN and audio metrics built into the same platform.

The migration timeline:

  • Today: EdgeView moves to read-only. No new EdgeMarc devices get added to it.
  • Through the rest of the year: your channel manager will reach out to schedule your migration into Atlas Aware.
  • End of year: EdgeView goes offline for good.

This isn’t limited to partners running WLC’s EdgeView. If you’ve got your own EdgeView instance with nowhere to go, we’re already working with partners in that exact position — migrating their EdgeMarc fleet onto Atlas Aware and clearing a path to keep adding new devices in the field.

A few things won’t carry over. Firmware management isn’t supported through Atlas Aware. Packet captures still run on the EdgeMarc device itself but can’t be triggered from the platform. Event log browsing isn’t available, and historical EdgeView data won’t migrate — Atlas Aware starts fresh.

Catch the Next One

Three releases, three different problems solved — none of them required you to rip out what you already have. SIP URI gets a voice AI agent on the phone today. The call recording API puts your call data to work in the pipelines you’re already building. And EdgeMarc support in Atlas Aware means a sunsetting product doesn’t leave you stranded.

And we’re just getting started. WLC is focused on two overarching themes: easy and compelling. We’re making it easier than ever to engage with us, and we want a compelling solution, a compelling platform, and a compelling business model for our partners. Our monthly release cycle is part of that aim. Some months may be bigger, some smaller, but every month we’ll have something new — guided by requests from you, our partners.

Stay tuned for what’s next.