AiSDR

Agents take authenticated action in outside systems: the CRM integration collection documents syncing contacts, mapping fields and triggering CRM actions, with two-way HubSpot sync and Salesforce sync writing activity back.

Around it sit a fixed set of vendor-built connectors named on the platform page and in the help center: HubSpot, Salesforce, Aircall for calls, Gmail and Outlook for sending, Calendly and HubSpot Calendar for booking, and LinkedIn for social outreach.

That is a short fixed list with no way to add your own, with no custom connector, no generic HTTP action and no API through which a customer could reach anything not on it.

Sourcehelp.aisdr.com CRM integrations and LinkedIn collections, aisdr.com/platformread 2026-09-01

The platform carries the sequence rather than handing it back. Ami AI is documented as an assistant that plans, launches, analyzes and refines campaigns from one conversation, and multi-step sequences run across email, LinkedIn and Aircall call steps with campaign editing and monitoring covered in its own collection. Execution branches on what the prospect does: AI Smart Replies handle inbound responses automatically and route notifications to the rep, and CRM actions fire on the outcome. No retry or error-path behavior is documented.

Sourcehelp.aisdr.com Ami AI, campaign management and replies collectionsread 2026-09-01

Grounding is on the prospect rather than on the customer's own corpus. The agent runs live research and enrichment per contact against public sources and a large third-party contact database before drafting, and the customer supplies context through personas, prompts and messaging templates configured in the persona tab. Authored configuration is not a knowledge base, and no document or file ingestion, knowledge base or vector store is documented.

Sourcehelp.aisdr.com personas and prompts collection, aisdr.com/platformread 2026-09-01

A human handoff exists in one place and no general approval mechanism does. Replies and notifications are documented as tracking lead replies and alerting the rep, so a conversation can be taken over by a person, and campaigns can be paused or edited while running. Nothing lets the buyer decide which actions need sign-off, who signs off, or what happens while approval is pending, and AI Smart Replies are documented as answering automatically rather than as drafting for release.

Sourcehelp.aisdr.com replies and notifications and campaign management collectionsread 2026-09-01

AiSDR links a trust center at trust.aisdr.com from its site footer, hosted on Vanta, but what it attests to is not confirmed. The privacy policy names no certification, the terms are silent, and the help center's twelve collections carry no SSO, SAML, roles or permissions article. No SOC 2 report or description of how user access is controlled is publicly readable.

Sourcetrust.aisdr.comread 2026-09-30

Reporting is aggregate. The dashboard collection tracks leads engaged, emails sent and performance metrics, and the features page says AiSDR logs every interaction and writes call notes and deal stages to the CRM. No per contact view of what the agent did and why is documented, so this is reporting rather than an audit of agent behavior.

Sourcehelp.aisdr.com/collections/9292627813-dashboard_overviewread 2026-10-01

Ami AI is documented as remembering what the user told it across sessions, including the ICP, tone preferences and what worked, and sequences carry reply history over weeks. No scope beyond the account, no lifetime and no way to review or delete what Ami keeps is stated.

Sourceaisdr.com/featuresread 2026-10-01

The privacy policy states that data from users outside the United States is transferred to the United States and processed there, relying on the EU-U.S. Data Privacy Framework for EU and UK transfers, which is a single stated region with no customer choice; transfer cover is not residency. No region selection, dedicated tenancy or customer environment deployment is published.

Sourceaisdr.com/privacyread 2026-09-30

Ready-to-run starting points exist but a browsable library does not. Three campaign kinds ship configured, cold outreach, social signals and website visitor, and the AI Strategist generates a complete campaign with angles, sequences and targeting from the customer's website and ICP. No gallery of named agents or templates aimed at named jobs is documented, and the templates the help center documents are the customer's own word-for-word email templates rather than a vendor library to adopt from.

Sourcehelp.aisdr.com templates article and campaign collection, aisdr.com/platformread 2026-09-01

The agent starts on signals rather than on a person typing. The campaign collection, the largest in the help center at sixty-one articles, covers three campaign kinds: cold outreach, social signals and website visitor campaigns, so a prospect visiting the site or engaging on LinkedIn puts them into a sequence.

CRM actions can also be triggered from the integration. Channel coverage spans email through the customer's own Gmail or Outlook mailboxes, LinkedIn connection requests, direct messages and InMails, and calls through Aircall, with replies and notifications routed back to the rep and activity logged into the CRM.

Sourcehelp.aisdr.com campaign, LinkedIn outreach and replies collectionsread 2026-09-01

No model is named and no customer choice is offered. Neither the help center's twelve collections nor the platform page discloses which large language model powers the product, and no model selector, per-campaign choice, bring-your-own-key or routing control is documented anywhere.

Sourcehelp.aisdr.com collection index and aisdr.com/platformread 2026-09-01

No API, SDK, MCP server or webhook is documented. The help center organizes the entire product into twelve collections covering onboarding, Ami AI, campaigns, personas and prompts, dashboard, replies, CRM integrations, LinkedIn, billing and webinars, and none of them concerns a developer surface. The platform navigation is the same, listing prospecting, AI Strategist, HubSpot, Salesforce and Aircall with no developer or API entry. Integration is delivered through vendor-built connectors rather than an interface the customer's own systems can call.

Sourcehelp.aisdr.com collection index and aisdr.com/platformread 2026-09-01

Nothing the customer runs before a change ships is documented. Campaigns can be edited and monitored while active and the dashboard reports leads engaged, emails sent and performance metrics after the fact, which is reading results rather than testing a change. No preview or dry run of a sequence, no holdout or A/B framework the customer configures, no scored comparison between message variants and no sandbox is documented. Where optimization happens it is Ami AI refining campaigns on its own rather than the customer measuring them.

Sourcehelp.aisdr.com dashboard, campaign management and Ami AI collectionsread 2026-09-01

The help center devotes a ten-article collection to setting up the LinkedIn integration and using it for automated outreach, covering connection requests, direct messages and InMails, so the agent takes action inside an interface the vendor does not control. No first-party page states how those actions are executed. The other channels run over email through the customer's own mailboxes and calls through Aircall, both programmatic or telephony routes.

Sourcehelp.aisdr.com LinkedIn outreach collectionread 2026-09-01