build a call flow using SignalWire Markup Language (SWML)
domain: signalwire.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Write a SWML document (YAML or JSON) with a main section defining the default call flow.
Use methods like play, ai, connect, and enter_queue inside sections to control call behavior.
Add additional named sections for branches (sales, support, menu) and use execute to call them like functions, or transfer to hand off permanently.
Host the SWML document, or serve it dynamically from your own endpoint, and point your SignalWire number or Call Flow Builder at that source.
Test locally with SignalWire's developer tooling before pointing production numbers at the endpoint.
Known gotchas
execute (temporary, returns control to the caller section) and transfer (permanent handoff) are easy to confuse — using transfer where you meant execute breaks any flow logic expecting control to return.
Because a whole call flow can be expressed as one self-contained document, it's tempting to stuff too much conditional logic into a single SWML file — split into multiple sections once branching gets complex or debugging becomes painful.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?