CreatiSoul Agency OS treats AI as a layer that runs across the whole customer journey, not a single feature. This map places every realistic AI use-case on the stage where it earns its keep — from capturing a lead to expanding a customer — and tags each one with how soon we can ship it (Near-term vs Later) and the capability that powers it (Claude, MCP tools, the existing platform creative engine, or CRM data). The point is to be honest about what's a quick win vs. what needs more data and trust first.
From an inbound email / domain, fill in the Company (industry, size, location, likely GST status) and find the right service lines to pitch. Pre-populates fields a rep would otherwise google by hand.
A hot / warm / cold score + one-line rationale from form content, budget signals and fit. Starts rules + Claude judgement; sharpens into a learned model once we have won/lost history.
Dedup against existing Companies, classify intent (new business vs. support vs. spam), and suggest the owner + pipeline. Suggest-first; only flips to auto-assign once routing accuracy is trusted.
First-touch emails, reply drafts and scoped proposals built from the Deal's service line, budget and the account's history — in CreatiSoul's voice. Human edits and sends; AI never sends blind.
Paste a call note or email thread; AI writes a clean Activity on the timeline plus a next-step checklist. Turns messy notes into a structured, searchable account history.
Flags deals that have gone quiet, stalled in a stage, or skipped a step — and suggests the next best action (call, re-quote, drop). Needs enough closed-deal patterns to be trustworthy.
Video / image creative is produced on the live platform (app.csoul.cloud): campaigns → briefs → AI generation via the Higgsfield engine. A Meta-ads or Social Engagement in the CRM opens the platform for the actual creative work; the CRM stays the system of record for the client, the engagement and the deliverable status. No duplicate creative tooling in the CRM.
AI video & image for Meta/Social campaigns via the platform's brief → generation engine. From the CRM, a creative Engagement deep-links to the matching campaign / brief on app.csoul.cloud rather than copying the workflow.
Draft a monthly social calendar per Engagement — themes, post cadence, hooks — that becomes Deliverables & Tasks. The team approves and edits; AI removes the blank-page work each cycle.
Headlines & primary text for Meta / Google ads, plus SEO page titles, metas, briefs and keyword groupings — tied to the client's brand profile and service line. The text layer beside the platform's visual layer.
Roll up an Engagement's tasks + ad results into a plain-English monthly client report and an internal status digest. Later because it depends on ad-performance feeds being wired in first.
Generates the due / +3 / +7 / +14 reminder ladder, escalating politely — warmer for long-standing retainers, firmer for late one-offs. Pulls the right amount, currency and invoice number; a human approves before it goes.
Watches for short-pays, wrong-currency receipts, duplicate or unusually late payments and a subscription that should have renewed but didn't — and raises a flag for review. Needs a payment history to learn "normal." Flag-only, never auto-adjusts the ledger.
A health score per customer from signals like slipping deliverables, slowing replies, late payments and falling ad spend. Later — it needs real churn history before its warnings can be trusted.
When a customer trips a risk flag, suggest the retention play — a check-in call, a re-scope, a results recap, or a goodwill concession — drawing on what saved similar accounts before.
Spots customers buying one service who'd benefit from another — a Social client with no SEO, ads running with a weak site — and drafts the pitch + a Renewals & Expansion deal. The rules version is buildable now.
A side panel on any record: "ask about this account," "draft anything," "summarize." It's scoped to the open Company / Deal / Engagement, so it answers with that record's real context — the single front door to every use-case on this page.
Researches a prospect or client from their website & public presence and builds a brand profile — tone, audience, positioning, competitors. This profile feeds proposals, ad-copy, content calendars and the platform's briefs, so every output sounds on-brand.
Cross-account questions in plain English — "which retainers are at risk this quarter?", "total overdue in ₹ & USD?", "which clients have no SEO engagement?" Sits above the whole CRM; Later because it needs the full data model populated to be reliable.
The same use-cases, sequenced. The principle: ship the assist-first writing & summarizing wins early (low risk, instant time-savings), wire scoring & risk models after data accumulates, and keep all auto-actions human-approved until trust is earned.
How AI behaves across all of the above — so it stays useful and trustworthy in a single-tenant, owner-run agency.
AI drafts and suggests; a person reviews before anything is sent to a client or changes the ledger. Auto-actions earn their autonomy.
Outputs are scoped to the real record — this Company, this Deal, this brand profile — not generic. No hallucinated facts about an account.
GST splits (CGST/SGST vs IGST), LUT exports, currency totals and balances are computed by code. AI writes about money, never calculates it.
Creative video / image generation is not rebuilt in the CRM — it links out to the live engine at app.csoul.cloud. One place for creative production.
Read the map as a menu, not a mandate. The only thing that exists today is the platform's creative engine (Deliver stage) — everything else is a proposal. The owner's job here is to rank what matters most and confirm the Near-term / Later split: which Wave-1 wins do we want first, and how aggressive should auto-actions ever get?
Real vs. proposed: the brief → AI video/image engine on app.csoul.cloud is live. Every other use-case, and the entire horizon ordering, is PROPOSED — confirm. The CRM objects each one writes to (Company, Contact, Deal, Activity) are live in CRM-1a; Lead, Engagement, Deliverable, Task, Invoice, Payment and Subscription are planned — so use-cases that depend on those land after the objects do.