Communication · Integration
DialMyCalls
Add DialMyCalls to your product for your customers, and give your AI agents governed access to it.
DialMyCalls exposes api.dialmycalls.com/v1 and rejects unauthenticated calls with an explicit invalid email and password message, a reminder that its auth model is account-credential based rather than a bare bearer token. A broadcast is a single object that carries its channel, its recipients and its content together, so a voice broadcast needs either an uploaded or text-to-speech recording attached before it can be scheduled, while an SMS broadcast carries plain text and is subject to the caller ID and consent rules attached to the account. Recipients come from contact groups held in the account rather than from arbitrary numbers passed inline, so pushing a new audience means creating or updating a group first. Delivery outcomes are read back per broadcast after the send completes, not synchronously. fastn keeps each customer's credentials scoped to their own account and handles the upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own DialMyCalls account so broadcasts are sent from their caller ID and billed to them
Sync a contact group from your app so the customer's audience stays current without manual uploads
Trigger an SMS or voice broadcast from an event in your product, such as a closure or schedule change
Report delivery outcomes for each broadcast back into your own activity timeline
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a broadcast and schedule it against an existing contact group, never an ad hoc number list
Have an agent report which recipients did not receive the last broadcast and suggest a follow-up
Audit, per tenant, every broadcast an agent scheduled or sent, with the group and channel it used
Example prompt
What was the delivery rate on the SMS broadcast we sent through DialMyCalls yesterday?
Set up DialMyCalls in 4 steps
- 01Enable the DialMyCalls connector from your fastn dashboard.
- 02Have each customer authorise their own DialMyCalls account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the DialMyCalls integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DialMyCalls integration without building it. Your customers connect their own DialMyCalls account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a DialMyCalls update is not your on-call problem.
- One integration serves your product and your agents. The same governed DialMyCalls connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
TwilioOften used alongside
Tools the same teams tend to run next to DialMyCalls, across other categories.
Aircall
Calendly
Gong
Google CalendarDialMyCalls integration FAQ
How do I add a DialMyCalls integration to my product?
Enable the DialMyCalls connector in your fastn dashboard, then let each customer authenticate their own DialMyCalls account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DialMyCalls client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DialMyCalls account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DialMyCalls account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this DialMyCalls integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a broadcast and schedule it against an existing contact group, never an ad hoc number list
Who maintains the DialMyCalls integration?
fastn does. When DialMyCalls changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own DialMyCalls account?
Yes. Every customer authorises their own DialMyCalls account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the DialMyCalls integration?
A common starting point: let a customer connect their own DialMyCalls account so broadcasts are sent from their caller ID and billed to them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the DialMyCalls integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DialMyCalls does not change your per-connector cost. You can start free with 3 connected accounts.
Add DialMyCalls to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.