Artisan

Agents take authenticated action in outside systems rather than reading from them or handing work back to a person: bi-directional CRM sync writes to Salesforce, HubSpot and custom CRMs, the agent sends from the reps' own mailboxes under ownership rules, and it books meetings directly onto AE and AM calendars.

The customer can add their own connections, through custom CRM support and custom webhooks as a data source, so the catalogue is not a fixed list. Breadth spans five classes: CRM, mail, calendar, messaging through Slack for performance reporting, and import from the customer's data warehouse, alongside a native dialer. No enumerated catalogue is published, which is a documentation limit reflected in the medium confidence rather than in the grade.

Sourceartisan.co/solutions/enterprise and artisan.co/pricingread 2026-09-01

The agent runs five stages end to end without handoff: sourcing from a 250M-plus contact database or the customer's CRM and data warehouse, researching and enriching each prospect across 22-plus sources, writing and sending personalised multi-channel sequences, handling replies and objections, and booking meetings on the right AE or AM calendar.

Execution branches on configured rules rather than running a fixed path: coaching rules apply per campaign and per sequence step, escalation rules divert to a human, ownership rules and round-robin decide which mailbox sends, and call steps are queued to the right human owner while meetings route to the account owner. Campaigns run continuously across markets and over 50 languages.

Sourceartisan.co/solutions/enterpriseread 2026-09-01

The agent grounds on the customer's own material: it researches each prospect across the customer's CRM, accepts import from the CRM or data warehouse, and writes in the customer's brand voice using coaching rules defined per campaign and sequence step, with compliance requirements and brand guidelines configured during rollout. External grounding runs across 22-plus enrichment sources plus intent data.

Held at Partial because no maintained retrieval structure over customer knowledge is documented: no document or file ingestion, no knowledge base, no vector store and no retrieval configuration was reached on either pass, and brand voice and coaching rules are authored configuration rather than a grounding corpus.

Sourceartisan.co/solutions/enterpriseread 2026-09-01

Both halves of the axis are shipped and configurable. The approval half: the vendor states the customer controls escalation rules deciding when a human is in the loop, sets approvals and when a human steps in, and can require approvals at any stage before letting the agent run unsupervised.

The guardrail half: built-in compliance with banned phrases and the ability to coach the agent's writing, coaching rules defined per campaign and per sequence step, do-not-contact list enforcement, ownership rules governing which mailbox sends on whose behalf, a read-only CRM mode that pulls data into campaigns without writing back, and field-level export controls over what the agent may write. Upgraded from an April Partial that carried no vendor evidence.

Sourceartisan.co/solutions/enterprise, artisan.co/pricing and artisan.co/blog/artisan-launches-ava-2-0-first-autonomous-ai-bdrread 2026-09-01

Attestation and control surface are both documented. SOC 2 Type II certification is stated on the enterprise page with SOC 2 and AICPA badges in the site footer, a trust centre at trust.artisan.co carrying the sub-processor list, and the DPA commits to providing the current SOC 2 Type II report or executive summary under NDA annually, with a bridge letter where a current report is unavailable.

Named customer-facing controls: SSO and SAML through the customer's identity provider, role-based access control, team and workspace permissions, audit logs, field-level export controls, read-only CRM mode, annual third-party penetration testing, a bug bounty programme, just-in-time internal access with logged requests and six-monthly privilege review, TLS in transit and encryption at rest, 48-hour breach notification and 90-day deletion on termination. GDPR, UK and Swiss transfers covered by SCCs with addenda, and CCPA service-provider certification with no sale or share. Resolves an Unspecified cell straight to Full.

Sourceartisan.co/solutions/enterprise, artisan.co/dpa and artisan.co/pricingread 2026-09-01

Audit logs are named as a shipped customer-facing feature on the pricing page, and the vendor describes rolling every conversation and every number up into a single view so one ops team can see activity across the org. Campaign performance reporting is surfaced through Slack.

Held at Partial because this is the what rather than the why: no trace of the agent's reasoning over an individual send, no record of which enrichment sources or signals drove a given message, and no replay or inspection surface over a completed run was reached on either pass.

The extensive system logging described in the DPA's security exhibit is the vendor's own infrastructure monitoring, not a customer surface, and is not credited here.

Sourceartisan.co/pricing and artisan.co/blog/artisan-launches-ava-2-0-first-autonomous-ai-bdrread 2026-09-01

State persists across sessions at the prospect and campaign level: the agent tracks a sequence through multiple steps and follow-ups, carries conversation history into reply handling and objection responses, and reaches back into CRM context to re-engage dormant, closed-lost and churned accounts.

Held at Partial because the persistence is record-keeping rather than agent memory: no accumulation across runs, no corrections retained between campaigns and no memory store the agent writes to and reads back is documented, and the coaching rules and brand voice that do persist are customer-authored configuration, which is excluded from this axis. Much of the durable state also lives in the customer's own CRM rather than in the vendor's product.

Sourceartisan.co/solutions/enterpriseread 2026-09-01

Cloud-only with no customer control over data location. The DPA states personal data may be accessed and processed on a global basis, transferred to Artisan AI, Inc. in the United States and to other jurisdictions where its affiliates and sub-processors operate, and that infrastructure is multi-tenant and hosted with outsourced cloud providers the vendor does not own hardware at.

What covers this is legal instrument rather than residency: EU Standard Contractual Clauses with UK and Swiss addenda, GDPR and CCPA commitments. Under the standing rule that legal cover is not residency, none of that clears the bar, and no region selection, VPC, private tenancy, on-premises or self-hosted option appears on any tier including Enterprise, whose differentiators are volume, security review and rollout support. Confidence raised because the absence is now visible in the vendor's own legal text rather than inferred.

Sourceartisan.co/dpa and artisan.co/pricingread 2026-09-01

Packaged campaign plays ship ready to run and are named in the product navigation: cold outbound to net-new prospects, intent-signal campaigns, CRM reactivation of existing and churned contacts, cross-sell and upsell, and meeting booking, with advanced campaign types listed as a paid-tier feature. The agent itself arrives configured rather than assembled.

What was not reached is a catalogue: no browsable template library, no importable starting configurations and no gallery of prebuilt campaigns a customer selects from appears on the marketing site or pricing page, and enterprise rollout is explicitly described as white-glove configuration by the vendor's own team rather than self-serve adoption. Partial: packaged capability without adoptable packaged assets, consistent with the aomni grading the same day. Downgraded from an April Full that carried no vendor evidence.

Sourceartisan.co/solutions/enterprise and artisan.co/pricingread 2026-09-01

Work reaches the agent through several documented routes rather than one. Event triggers: intent signals are detected automatically across the vendor's data sources and matching leads are instantly enrolled in tailored sequences, with funding rounds and leadership hires named as signals, and website visitor tracking triggers outreach to otherwise anonymous company visitors.

CRM state triggers reactivation of dormant, closed-lost and churned accounts. Custom webhooks bring the customer's own data in as a source. Campaigns then run continuously rather than on manual invocation. Outbound channel coverage spans email, social and queued phone calls from a native dialer, sending from the reps' own mailboxes across more than 50 languages.

Sourceartisan.co/intent-data, artisan.co/solutions/enterprise and artisan.co/pricingread 2026-09-01

No model is named and no customer choice is offered. The DPA confirms the service uses large language models and other AI technologies and carries contractual terms binding sub-processors that provide foundation models against training on customer data, which establishes that third-party models sit behind the product, but it names none of them and points to the trust centre for the sub-processor list.

No model selector, per-campaign model choice, bring-your-own-key or routing policy appears on the marketing site or any pricing tier, and the DPA describes the agent as executing the customer's configured parameters rather than the customer selecting the engine. Graded as not documented as first-class; confidence normalised from a non-canonical value.

Sourceartisan.co/dparead 2026-09-01

Two extensibility surfaces are documented: custom webhooks that bring the customer's own data into the platform as a source, named as a paid-tier feature, and bi-directional CRM sync described as working with Salesforce, HubSpot and custom CRMs via API. Held at Partial because no public API documentation, developer portal or SDK was reached on either pass.

The DPA's security exhibit does state that public product APIs may be accessed by API key or OAuth, but that exhibit is a boilerplate annex that also describes protecting hosted customer websites, which this vendor does not offer, so it is not read as a reliable statement about this product. A documented API reference would move this to Full.

Sourceartisan.co/pricing, artisan.co/solutions/enterprise and artisan.co/dparead 2026-09-01

Campaign outcomes are readable: the pricing tiers quote expected positive reply ranges per package, performance is surfaced through Slack, and conversations and booked meetings roll up into a single view.

Held at Partial because nothing the customer runs as a test is documented: no evaluation harness, no A/B or holdout framework the customer configures, no scored comparison between campaigns or sequence variants, and no sandbox or preview run before a sequence goes live was reached on either pass.

Where optimisation happens it is the agent tuning itself rather than the customer measuring it, which the convention places outside this axis.

Sourceartisan.co/pricing and artisan.co/solutions/enterpriseread 2026-09-01

The vendor documents its agent taking action inside LinkedIn, an interface it does not control, running social outreach as a channel within multichannel sequences alongside email and queued phone calls. That is action performed inside an external interface, which is the Partial band on this axis. Full requires documented control of a real interface, and no first-party page states how those actions are executed, so the mechanism is unrecorded and none is inferred here. The other channels run over email and telephony, which are programmatic routes rather than interface operation.

Sourceartisan.co/solutions/enterpriseread 2026-09-01