The Problem

Instagram DMs mix everything together: high-value brand deals, customer questions, fan messages, and spam.

A creator shouldn't have to manually decide what deserves attention.

The Solution

DM Triage Agent gives an Instagram inbox an AI-powered operations team.

It classifies every incoming DM and routes it through Caspian to the right place:

  • 🔥 Hot leads → Telegram → human approval → Instagram
  • 📦 Customer inquiries → Discord team
  • 💬 Fans & spam → Email digest

The key idea is simple:

Important messages interrupt humans. Unimportant messages don't.

How It Works

Instagram DM
     ↓
Meta Webhook
     ↓
Featherless AI
     ↓
Smart Router
  ↙    ↓     ↘
Telegram Discord Email
  ↓
Human action

Caspian provides the communication layer across Telegram, Discord, and Email, allowing the agent to reach people instead of simply generating text.

A Real Example

A real Instagram DM said:

"Hi, we'd like to collaborate on a campaign. Our budget is $50,000."

The agent classified it as a hot_lead with 0.95 confidence.

Instead of automatically responding, it sent a Telegram alert to the owner.

The owner replied YES.

The agent then sent the approved response back to Instagram.

Instagram → AI → Caspian → Human → Instagram

This was tested end-to-end with real connected services.

Built For Reliability

The agent includes:

Webhook deduplication
Echo filtering
Human approval for high-value actions
Approval authorization
Pending-action recovery
Email delivery verification
AI classification with keyword fallback
What I Learned

The hardest part wasn't getting an LLM to classify a message.

It was making the agent reliably do something after understanding it.

Managing asynchronous webhooks, persistent state, human approvals, channel-specific behavior, and real message delivery taught me that an agent needs reliable infrastructure as much as it needs intelligence.

Why Caspian

Caspian gives the agent its hands.

Instead of building separate communication logic for every channel, the same workflow can reach the owner, the team, or the inbox through different channels.

The result is an agent that doesn't just understand messages.

Built With

Share this project:

Updates

Submission history