Real test calls into Microsoft Teams
E5 Sandbox and CDX tenants give you test users. They don't give you test calls.
We inject scripted, real-audio calls directly into your Teams tenant—with DTMF navigation, configurable caller IDs, and the ability to answer from Teams too.
What Teams developers use this for
Targeted at ISVs and developers building on the Teams calling platform.
Realistic call data for sandbox tenants
CDX and E5 Developer Sandbox tenants come with test users and pre-configured Teams resources — but no way to generate actual inbound calls. We close that gap. Inject real calls with real audio, configurable caller IDs, and scripted behaviour, on demand.
Trigger and verify audio-dependent apps
Call recording apps, transcription services, and compliance hooks need a real call with real audio to fire. We play actual audio during the call so your app triggers exactly as it would in production — then you verify it did. No more "it works on my machine" uncertainty in your sign-off.
Confirm your routing and DTMF logic
Ring your main number, press option 2 — does the right call queue ring? Do the right agents get alerted? We script the full call journey including DTMF presses and assert the outcome, so misconfigured routing gets caught before a real user does.
Two-way call simulation
We can answer calls placed by Teams as well as originate them. If your app triggers an outbound call — a bot callback, a click-to-dial flow, or a transfer — we answer it, giving you a complete round-trip to validate. Essential for any scenario where your application is the calling party.
Fits into your release pipeline
API access lets you configure scenarios and trigger suite runs from your CI/CD tooling. Run a set of call scenarios before each release and get back pass / warn / fail results you can attach to your sign-off.
Example call flow
Inbound call to an auto attendant with three menu options, DTMF selection of option 3, ring-all to a four-agent queue, one agent answers, two minutes on the line, then hang up.
Full-call scenarios (example suite)
Each row is one end-to-end scripted call test. The diagram unpacks a single representative journey. Illustrative suite summary only.
- Pass Call Alex via Main Number
- Pass Call Adele Direct
- Pass Long Call via Call Queue X
- Pass Main Number — AA to Support Queue
- Pass After-Hours to Shared Voicemail
- Pass Hunt Group Billing — Ring All
- Pass Callback Line to Mobile Pool
- Warn No Confirmation of Call Recording
- Fail External PSTN (Sim) — First Leg No Answer
How calls get into Teams
We add Direct Routing entries to your test tenant that point at our infrastructure. Calls arrive at Teams as genuine SIP-injected calls — no carrier, no PSTN costs, and no special configuration on your end beyond a standard Direct Routing setup.
You control pools of test From numbers and To numbers, so every run is predictable and every call is traceable back to the scenario that triggered it.
- E5 Developer Sandbox — development and pre-release verification cycles
- CDX — realistic, repeatable calling flows against provisioned users
Interested? Let's talk.
We're talking to Teams app developers and ISVs building on the calling platform to understand what scenarios matter most. If any of the above sounds useful, book a call and we'll walk through what it looks like for your specific setup.
- — No pricing commitment — this is an early interest conversation
- — We'll share what's available now and what's on the roadmap
- — Bring your scenario and we'll assess fit honestly