The Bot Creation Matrix: Four Ways to Deploy AI, Now All Live on WFW

Dual-mode agent support just shipped. With it, the Bot Creation Matrix is complete.

This is the "we've arrived" post. Every mode of AI deployment we set out to support is now live and production-ready on WFW. It took eighteen months to get here, and the last piece — the ability for a single agent to serve both human callers and AI agent callers from the same phone number — is what makes the whole thing coherent.

What the Bot Creation Matrix Is

The Bot Creation Matrix describes who creates an agent and who consumes it. Two axes, five modes:

• Who creates: a human (dashboard or manual API) or an AI (programmatic API call from a bot)
• Who consumes: a human caller or an AI agent caller

Most voice AI platforms handle Mode 1 — human creates, human consumes. Some handle Mode 3 — AI creates, human consumes. WFW now handles all five modes, including the ones that are genuinely new.

What Just Shipped

Dual-mode agent support (Mode 2 + Mode 5) — A single WFW agent can now serve both human callers and AI agent callers from the same phone number. Same number. Different behavior based on who's calling.

Caller-type detection at the service layer — When a call comes in, WFW detects whether the caller is human or AI before routing to the agent. It looks at a combination of signals: the X-Caller-Type header (for API callers that self-identify), the Accept header, call setup patterns, and audio characteristics for voice callers. Detection happens in under 300ms.

Structured JSON output for bot callers — When an AI agent calls a WFW number, it can declare Accept: application/json and receive the response as structured JSON instead of synthesized voice. The agent processes the information as data, not audio. No transcription step, no parsing uncertainty.

The Five Modes, With Examples

Mode 1: Human creates, human consumes A dental practice owner logs into the WFW dashboard, pastes their website URL, hits deploy. Ninety seconds later, their agent is live and answering patient calls. The most common mode. The one we built first.

Mode 2: Human creates, AI consumes An insurance verification AI needs to check a patient's coverage at Ridgeline Dental. It calls the Ridgeline WFW number, declares itself as a bot caller, and asks about benefit coverage for D4341. It gets back a structured JSON response with the coverage information — no hold music, no "press 1 for billing." The same agent that talks to patients handles this request as data.

Mode 3: AI creates, human consumes A DSO's operations platform detects a new practice coming onto its network. It calls POST /v2/agents with the practice's URL and template_id: "dental-general-practice". Workforce Wave provisions the agent in 90 seconds. No human touched a keyboard. The newly provisioned agent starts serving that practice's patients.

Mode 4: AI creates, AI consumes A hospital's discharge coordination AI triggers post-discharge follow-up calls for patients leaving the ER. It creates the outbound campaign via API, the WFW agent places the calls, and results — appointment confirmations, patient-reported symptoms, medication questions — flow back to the hospital's Epic instance via webhook. Human staff reviews exceptions. The routine cases are fully automated.

Mode 5: Human creates, dual consumers A hotel deploys a single WFW number for guest services. Human guests call and talk to the agent by voice — it handles room requests, restaurant reservations, check-out questions. OTA booking platforms call the same number programmatically to check availability and request holds, and they get structured JSON responses. One agent, one number, two completely different interaction modes running in parallel.

Why This Matters

The internet became transformative when machines could talk to other machines over HTTP without a human in the loop. Phone-based service businesses are at the same inflection point, except the "machines" are AI agents and the protocol isn't HTTP — it's voice and structured API calls layered on top of telephony.

A WFW agent isn't just a receptionist. It's a node in an emerging AI-to-AI service network. It can receive instructions from an orchestration layer, execute the work (the phone call, the booking, the verification), and return structured results — to a human or to another AI, whichever is asking.

That's what full-parity on the Bot Creation Matrix means. The agent is a first-class participant in whatever network you're building.

What's Next

The next chapter is the WFW developer ecosystem. Third-party MCP registries that list WFW agents as callable capabilities. Agent-to-agent (A2A) directories where AI orchestrators discover WFW agents by capability. Webhook integrations with major EHR, PMS, and CRM platforms so results flow automatically to the systems that need them.

The matrix is complete. The ecosystem is next.

---

Dual-mode support is live now for all accounts. Agents with a business_url automatically support both modes — no configuration change required. If you're calling a WFW number programmatically and want structured JSON responses, add Accept: application/json and X-Caller-Type: bot to your request headers.

Full documentation at workforcewave.com/docs/dual-mode.