client-intake

Automate client request intake into structured tasks with routing and escalation.

2|Updated Dec 13, 2025

Search Tags:#automation #routing #requirements #multi-channel #classification #escalation #intake

Ready to run

npx skills add https://github.com/truchot/claude-skills-test --skill client-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: client-intake
Source: https://github.com/truchot/claude-skills-test/tree/main/.web-agency/skills/client-intake
Command: npx skills add https://github.com/truchot/claude-skills-test --skill client-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end intake, qualification and routing of client requests into structured, actionable workflows for the agency.

Core Features & Use Cases

Reception: capture and parse messages from multiple channels (email, forms, chat, webhooks) into structured input
Qualification & Extraction: classify intent, estimate effort, extract requirements and identify stakeholders
Routing & Orchestration: match with the right skill, assign priorities and hand off to the correct pipeline
Output & Escalation: create intake records, emit automatic acknowledgments and escalate critical cases when needed

Quick Start

Convert a new client message into a structured intake and route it to the task orchestrator.

Frequently Asked Questions about client-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate client intake from multiple channels like email and chat?▼

Automating client intake involves capturing multi-channel inputs from email, forms, chat, and webhooks, then parsing them into structured tasks. The skill classifies intent, estimates effort, and routes requests to the appropriate pipeline automatically.

What is the best way to route client requests to the correct workflow pipeline?▼

Routing client requests requires classifying intent, extracting requirements, and matching the request with the appropriate skill. This approach assigns priorities and hands off the structured intake record to the correct pipeline for orchestration.

How do I handle ambiguous client requests during automated intake processing?▼

Handling ambiguous client requests requires enforcing validation and ambiguity handling policies during intake. The system identifies unclear requirements, escalates critical cases when needed, and ensures timely and accurate orchestration of the workflow.

Can I use automated intake to estimate effort and identify stakeholders from raw messages?▼

Yes, automated intake qualifies raw client messages by classifying intent, estimating effort, extracting requirements, and identifying stakeholders. This transforms unstructured inputs into structured, actionable workflows for the agency.

What escalation policies are needed for critical client intake cases?▼

Escalation policies for critical client intake cases enforce validation, emit automatic acknowledgments, and escalate when requirements are ambiguous or urgent. This ensures timely and accurate orchestration of the routed tasks.

Why do I need to structure client messages before task orchestration?▼

Structuring client messages before task orchestration ensures raw multi-channel inputs are converted into actionable workflows. Qualifying the intake by extracting requirements and classifying intent prevents routing errors and pipeline bottlenecks.