ClickSend

Enable the ClickSend connector in your fastn dashboard, then let each customer authenticate their own ClickSend account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ClickSend client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own ClickSend 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.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent sends a notification within governed permissions.

fastn does. When ClickSend 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.

Yes. Every customer authorises their own ClickSend 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.

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.

A common starting point: send SMS from your product using their own account and sender id. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ClickSend does not change your per-connector cost. You can start free with 3 connected accounts.