FirstAML + Alterspective + Clio Operate
A joint story for FirstAML and Alterspective: verification powered by FirstAML, workflow shaped by Alterspective, and operational decisions surfaced inside Clio Operate. The copy stays disciplined. Every claim below is tied to implemented widget and plugin behaviour, not aspirational integration language. This page now carries three ready-to-use narrative angles so marketing can pick the right voice for the room.
Scroll — the joint story starts below
Why it matters
This is the version a sales team can use without slipping into fiction: FirstAML powers the verification, Alterspective shapes the legal-operating workflow, and Clio Operate is where the firm sees, reviews, and acts on the outcome.
The same insight surface can render on the Client record and on the Client Compliance cycle, so operations, compliance, and partners are not chasing separate tools to understand the current position.
On client placements, refreshed FirstAML data is persisted to both the active compliance cycle and the client copy, keeping the operational view and the audit record in step.
The plugin handles case-created, status-updated, PDF-updated, verification-report, and unwrap-status events, then maps them into Clio Operate events the platform can act on.
The integration package includes actions to create a FirstAML case, retrieve case details, and download the case summary PDF.
Business angle
The commercial story is straightforward: FirstAML provides the verification engine, Alterspective shapes the legal workflow around it, and Clio Operate becomes the place the firm reviews, refreshes, and acts.
Technical capability
Under the hood, the pattern is equally concrete: outbound case calls, inbound signed webhooks, mapped platform events, and a host-aware widget that resolves the right record before falling back to the relevant compliance cycle.
Marketing angles
Your marketing team should not need to translate one page into three different voices. These are the three usable variants: executive, co-branded, and technical-buyer.
Executive / sales-led
Use when: Use when the audience cares about speed, control, and audit confidence before they care about architecture.
Lead line: FirstAML verifies the client. Alterspective brings that verification into the matter-opening workflow so the firm can act without leaving Clio Operate.
Co-branded partner marketing
Use when: Use when FirstAML and Alterspective are presenting together and need a balanced story that gives both brands a clear role.
Lead line: FirstAML provides the verification engine. Alterspective operationalises it inside Clio Operate. Together, the firms get AML that is not just connected, but usable.
Technical buyer / BA / IT
Use when: Use when the room will ask how it works, how it fails, and how support teams recover when automation is imperfect.
Lead line: The integration is built as a governed operating seam: workflow actions outbound, signed webhooks inbound, mapped platform events, host-aware widget resolution, and explicit refresh/write-back behaviour.
Who it serves
The page needs to survive three conversations without changing its story: partner-facing value, operational reality, and delivery-team scrutiny.
For FirstAML
The message is not just ‘we call your API’. It is that FirstAML results become operational inside Clio Operate: surfaced on the client, attached to the compliance cycle, refreshable by the team, and visible at partner decision points.
For law-firm buyers
The compliance team can see status, hits, outstanding items, and next steps in the same platform the firm already uses to open files. That reduces swivel-chair work and gives the firm a cleaner audit story.
For BA / IT / delivery teams
Webhook management, event mapping, GraphQL case refresh, host-aware widget resolution, and write-back behaviour are all explicit implementation points rather than hidden magic.
How it works
This is the capability chain as it exists today, based on the FirstAML plugin and the Compliance Case Insight widget work.
Clio Operate can create a FirstAML case as part of the client-compliance flow rather than relying on a separate operator ritual.
Each organisation can register its webhook endpoint, failure email, and verifier key through the configuration widget so the callback path is explicit, supportable, and not buried in infrastructure folklore.
The callback endpoint accepts named FirstAML events, validates the HMAC signature, rejects oversized or unsupported payloads, and rate-limits inbound traffic before those events touch workflow logic.
Webhook payloads are mapped into named platform events such as `firstaml-case-status-updated` and `firstaml-verification-report-generated`, so downstream workflows can subscribe without parsing raw webhook JSON everywhere.
On a client record it prefers the copied compliance result on the client itself, then the current compliance-cycle reference, then the newest relevant compliance cycle. On a compliance-cycle record it normally reads self first and stops there.
The UI can auto-fetch when a case exists, auto-poll while work is in progress, show per-individual next steps, bulk-refresh multiple cycles on the client host, and fall back to a clear read-only state if write permissions are missing.
What teams see
This is the part sales, delivery, and partner teams can point at with confidence: the workflow actions, the FirstAML event triggers, and the Clio Operate insight surfaces that make the integration usable day to day.
Action in workflow
Create the FirstAML case from the Clio Operate workflow itself, then route success and error paths without leaving the operating model.
Action configuration
Field-level mapping lets the workflow decide how the case should be named, referenced, and initialized when FirstAML is invoked.
Verification setup
The workflow can choose the verification mode that fits the matter, from screening-only through to stronger ID and biometric combinations.
FirstAML events
Case created, status updated, PDF updated, unwrap status changed, and verification report generated can all trigger downstream Clio Operate behaviour.
Available actions
The packaged workflow actions expose the practical seam: create the case, get the case details back, and download documents when needed.
Insight surface
The compliance insight view turns FirstAML status into an operational summary with signals, timestamps, case metadata, and refresh controls.
Sync-back controls
Individual reviewed records are visible, their outcomes are explicit, and the user can add or sync them back into Clio Operate at the right moment.
What's implemented
These are not aspirational architecture bullets. They are the concrete behaviours already built into the widget and plugin work we reviewed.
The compliance insight widget renders on both the client-compliance process and the client entity, with an explicit preference order for where it resolves AML data.
Even with webhook-driven updates, the UI keeps a manual refresh path from FirstAML so support and compliance teams can recover without waiting for automation to re-fire.
The widget turns raw payloads into row-level outcomes, signals, and next-step guidance such as fail, sanctions, PEP, adverse-media, screening hits, or outstanding documents.
Partial persistence warnings, permission-aware read-only mode, and bulk refresh progress are built in so the integration remains usable under imperfect tenant permissions or partial write failures.
Webhook registration is not hard-coded. The feature config supports organisation-specific hostname, email, and HMAC verifier settings, with cache invalidation when configuration changes.
The plugin converts inbound FirstAML notifications into named Clio Operate events so the rest of the file-opening workflow can subscribe in a platform-native way.
Use it in market
The strongest joint message is that AML does not stop at an API connection. It becomes a governed legal-workflow surface inside Clio Operate: visible on the client, tied to the compliance cycle, refreshable by the team, and usable at the exact point a firm needs to decide whether work can proceed.
