For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

How to Test Synthflow Agents With TestMu AI

Synthflow is a no-code voice platform running on its own telephony infrastructure rather than a third-party carrier, with a visual flow designer and subflows for multi-agent setups. On the TestMu AI Agent Testing Platform you can test your Synthflow agent on whichever channel it runs, with multi-turn conversations across personas and edge cases scored on each run.

To connect one, you need a Synthflow account with a published agent, a number provisioned on Synthflow's telephony layer for phone agents only, source docs for scenario generation (prompt, PRD, or knowledge base), and a TestMu AI workspace with agent-testing permissions.

How do you test Synthflow's in-house telephony and modular flows?


Synthflow runs on its own telephony stack with modular flows, so a few behaviours are worth building dedicated scenarios around:

  • In-house telephony. In-house telephony means call quality issues belong to Synthflow's stack, not a carrier's, which changes how a failure gets triaged.
  • Modular flows. Flows are modular, so a subflow edit propagates to every parent flow using it.
  • Plan-gated features. Feature availability varies by plan, so some flow capabilities are absent on lower tiers.
  • Chat below voice parity. Chat and SMS do not run at parity with voice on the same agent.

Which channels does a Synthflow agent run on?


One Synthflow agent runs across channels on its own telephony stack. Paste the agent's prompt or import the flow to generate scenarios, then follow the linked setup for the surface you test:

  • Phone covers inbound and outbound callers over Synthflow's own telephony stack: DTMF entry, transfers, voicemail detection, and latency measured against in-house routing rather than a carrier's. Setup: phone agent testing.
  • Voice reaches the agent through the embedded web widget rather than a phone number, with the endpoint profile created against the widget's agent. It drops telephony out of the path and isolates the speech pipeline, so STT and TTS accuracy, turn-taking, and interruption handling get tested without telephony noise. Setup: voice agent testing.
  • Chat runs text conversations through the chat widget, SMS, or WhatsApp Business, with the endpoint profile created using the chat widget or the messaging channel. It catches reasoning and branching failures, and the text channel runs shallower logic than voice on the same agent. Setup: chat agent testing.

What makes a Synthflow test fail?


Common failure modes to watch for:

  • No transcript returned
  • Subflow not triggered
  • Plan-gated feature missing
  • Messaging session expired

Test across 3000+ combinations of browsers, real devices & OS.

×
Schedule Your Personal Demo
Book Demo

Help and Support

Related Articles