Operator AI Copilot
Audience builder in natural language, bulk draft across SMS, email, and in-app, policy-check lint, approval flow, workflow triggers, full audit trail. The admin tasks that used to need an ops person, done by a copilot.
Operator oversight before anything sends.
What it does
Describe the audience in a sentence. Describe the message in a sentence. The copilot drafts, lints for compliance, routes to approvers, and schedules the send. One operator does the work of three.
Two surfaces that share the same engine: audience selection, drafting, policy check, approval, send.
Send a notification to 1,200 traders who deposited last month but have not placed a trade. The copilot drafts the message, picks the right channel per trader (email vs SMS vs in-app), lints for policy, and queues after your approval.
Set a trigger: when a trader hits a 10% drawdown, when KYC expires, when a withdrawal fails. The copilot drafts the response, queues the message, and logs the action. All event-driven, all audited.
Audience Builder
Describe the audience in a sentence: traders who deposited last month but did not trade in the last 7 days, from countries we are licensed in, excluding those on a chargeback flag. The copilot translates to a SQL-like filter you can inspect and adjust before executing.
Describe
40+
Translate
50+
Save
80+
Preview
20+
Trigger
15+
Inspect
10+
Bulk Draft
Describe the message in a sentence. Copilot drafts versions for email, SMS, and in-app. Localized into the languages your traders use. Each draft respects the channel's constraints: SMS under 160 characters, email with proper subject, in-app with CTA button.
Policy Lint
Every draft runs through a policy-check lint before it can be queued. Checks for performance-guarantee language, forbidden claims per jurisdiction, missing risk disclosures, missing opt-out language. Operators see the specific lint hits and fix them, or override with a logged reason.
Lint hits are specific and actionable. Overrides are logged with the operator and reason.
Approval Flow
Sends above a configurable reach threshold require a second operator approval before they queue. The approver sees the audience, the drafts, the lint result, and a sample preview. Approve, request edits, or reject with reason, all logged.
Workflow Triggers
Set a trigger (drawdown breach, KYC expiry, withdrawal failure, inactivity threshold). The copilot generates the response, lints it, and queues it when the event fires. The operator oversight model stays the same: optional approval, lint check, full audit trail.
Common questions
An AI copilot that still gives you oversight.
No. Every send requires explicit operator approval, even for triggered workflows. The copilot drafts and queues. The operator approves. For high-reach sends, a second operator approval is required by the reach threshold you configure.
Trader segments, deposit and trade state, KYC status, communication history. All inside your admin. No trader PII is sent to the AI (names, emails, phone numbers are redacted). The copilot works on counts and patterns, not individuals.
Forge AI handles content and brand (announcements, SEO meta, logo generation, section rewrite). Ops Copilot handles operations (audience selection, bulk sends, workflow triggers, policy lint, approval flow). Two separate surfaces, one credits balance.
Yes. The default lint rules follow EU, UK, Australia, and US financial-marketing conventions. You can add operator-specific rules (words to flag, phrases to block, mandatory disclosures per segment). Lint rules version over time and are visible in the audit trail.
Failed sends (bounced email, SMS not deliverable, in-app offline) retry per the channel's standard policy and are logged. The copilot surfaces failure rates per send so operators see if a message is systematically failing somewhere.
Yes. Every audience generation, every draft, every lint hit, every approval or reject, every trigger fire, every send attempt is logged with timestamp, operator, and reason where applicable. The audit log is tamper-evident with the same hash chain as the rest of the admin.
An ops copilot
Audience in natural language, drafts across channels, policy lint, approval flow, workflow triggers, audit trail. Oversight before anything sends.
A copilot, not an autopilot.
