Claude subagent
Why this subagent
A shared inbox turns into a dumping ground fast. Sales replies, support tickets, and billing questions all land in the same place, and someone forwards each one by hand to the right team. Things get missed and response times slip.
The router reads every message as it arrives, decides what it is, and creates the right CRM record automatically. Support requests become tickets, leads become contacts, and the owning team gets a Slack ping with a short summary. Nothing sits unread waiting for a human to sort it.
How it runs
Used at step 01 to kick off the pipeline.
Used at step 01 to kick off the pipeline.
Used at step 01 to kick off the pipeline.
Used at step 01 to kick off the pipeline.
Sample output
json// Sample output // (generated when the pipeline finishes) Read an inbound email and return its category, a confidence score, and the CRM object type that should be created or updated.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.