Agent Communications Provisioning
A governed layer for AI agent communications — signed, disclosed, and provable.
Dialnode provisions phone, SMS, messaging and email bound to a verified agent identity. It applies the disclosure a counterparty is owed under the relevant jurisdiction, and writes an attributable, tamper-evident record of every exchange into the operator's audit trail.
Watch the film
Market, stated plainly
The opportunity, with its uncertainty labelled.
What Dialnode provides
A thin governance layer over commodity channels.
Six modules that provision, disclose and record — the compliance and provenance overlay, not a new communications network.
Agent-bound channel provisioning
Provisions numbers and channels bound to a specific agent identity rather than an individual employee, consuming agent identity and access management to make the binding. It integrates with the incumbent STIR/SHAKEN caller-ID attestation rail rather than replacing it, and is designed to interoperate with emerging Verified Agent ID standards.
Disclosure engine
Applies jurisdiction-specific rules so counterparties are informed they are interacting with an AI agent, configured per jurisdiction as a first-class channel primitive rather than left to the operator to script.
Conversation provenance ledger
Records a complete, attributable, tamper-evident transcript bound to agent identity across channels, linking which agent said or decided what, and writing into the venture's audit-trail infrastructure for governance and compliance.
A2P and carrier registration
Manages brand and campaign registration through a Campaign Service Provider so outbound SMS is not blocked by A2P 10DLC rules, and manages carrier onboarding under human authorisation.
Deliverability and sender-reputation monitoring
Continuously monitors deliverability and sender reputation across voice, messaging and email channels, so agent-originated traffic sustains delivery over time.
Escalation routing and approval gates
Routes first-line escalations to the right accountable human and enforces explicit approval gates for production-affecting actions such as campaign launches and jurisdiction entry.
How it works
Provisioning to provenance, in four steps.
Provision a new agent channel
A founder or technical lead self-serves. An AI colleague allocates the number or channel, binds it to the agent identity, registers the brand and campaign, configures the applicable disclosure, and integrates STIR/SHAKEN attestation before the channel goes live.
Launch an outbound campaign
An AI colleague prepares the campaign and disclosure configuration. An accountable human approves the campaign policy and disclosure at an explicit gate before any traffic is sent, with consent and disclosure applied per the target jurisdiction.
Enter a new regulated jurisdiction
An AI colleague proposes the disclosure configuration for the jurisdiction. An accountable human signs it off and authorises any carrier onboarding; the approval gate must clear before agents send traffic there.
Capture and attribute a conversation
Every interaction is recorded with provenance tags binding it to the agent identity and written to the audit trail, producing a defensible record of which agent communicated what for governance, retention and compliance review.
What is genuinely different
Compliance and provenance built in from inception.
Disclosure by default
Disclosure that a counterparty is dealing with an AI agent is applied per jurisdiction as a channel primitive, not left to the operator to script.
Provenance you can produce
Every conversation is captured as an attributable, tamper-evident transcript in the audit trail, so attribution and integrity are already in place when a record must be produced.
Provisioned, not improvised
Channels are provisioned against a verified agent identity, with registration and deliverability handled as first-class concerns rather than assembled from generic tooling that mainstream services often reject.
Governed operation
AI colleagues carry the operational volume; accountable humans set policy, approve production-affecting actions, own carrier and regulator relationships, and hold fiduciary duty.
No single vendor combines all four today
Our research finds no single vendor combining channel provisioning, verified agent identity, mandatory disclosure and provenance in one layer. We treat this as a provisional, absence-of-evidence finding rather than a proven claim.
For serious buyers
Questions a careful buyer would ask.
What does Dialnode actually do?
It provisions telecom and messaging channels tied to an AI agent's identity, enforces jurisdiction-specific disclosure that a counterparty is dealing with an AI agent, and captures an attributable transcript into the company's audit trail. It sits as a thin governance layer over commodity channels rather than as a new communications network.
How is this different from generic CPaaS or email tooling?
Conventional provisioning assumes a human account holder, offers no native agent-to-human disclosure, and scatters communications without a defensible record. Many mainstream services also reject VoIP or CPaaS numbers, and US carriers already block unregistered A2P 10DLC traffic. Dialnode binds channels to a verified agent identity, applies required disclosure, handles registration and deliverability, and records attributable provenance.
Is this fully automated, and who is accountable?
No. AI colleagues carry the operating volume — allocation, deliverability and reputation monitoring, disclosure-rule application, transcript capture and first-line escalation routing. Accountable humans set and approve outbound campaign policies, authorise carrier onboarding, sign off jurisdictional disclosure configurations, and handle all regulator-facing matters. Production-affecting actions pass through explicit human approval gates and named humans retain fiduciary and compliance responsibility.
Which jurisdictions does the disclosure engine cover?
Disclosure is configured per jurisdiction against dated obligations, including US TCPA and FCC expectations, the EU AI Act's Article 50 duty commencing 2 August 2026, and California SB 243. The initial release focuses on the United States, where A2P 10DLC blocking makes demand binding; EU sequencing is prepared ahead of the Article 50 commencement date.
What is the commercial model?
It combines per-number and per-channel provisioning fees with usage-based messaging and voice charges. Pricing remains to be validated; we treat willingness to pay as unproven and are gathering the first signals with design-partner ventures.
How mature is the product?
The venture is at pre-seed stage. The initial scope provisions US phone, SMS and email channels bound to an agent identity, registers brands and campaigns through a Campaign Service Provider, applies US disclosure configuration, captures attributable provenance into an audit trail, and integrates STIR/SHAKEN attestation. It deliberately does not replace channel pipes or build conversation analytics.
What are the principal risks?
We state them plainly: US regulatory reversal — a December 2025 federal executive order may preempt state AI-disclosure laws, which is why we treat the EU mandate as the more dependable timing anchor — incumbent feature encroachment, notably from Telnyx, and pricing that remains to be validated.
Talk to the founding team.
A direct conversation about agent-attributed provisioning, disclosure and provenance for your deployment.