Back to Library#14 / 30
L2: Agency & SMB
Support Triage
Setup Time: 1 day
Est. API Cost: $800 + $190/mo
Architecture Overview
Connect your primary support email channel. Use the Gmail OAuth setup from Automation 2. Confirm scopes: gmail.readonly, gmail.modify, gmail.send. For Outlook, use the Microsoft Gr...
context.json
context.json
// OpenClaw Blueprint: #14 — Support Triage
{
"automation_id": "14",
"title": "Support Triage",
"level": 2,
"tier": "Agency & SMB",
"setup_time": "1 day",
"estimated_api_cost": "$800 + $190/mo",
"agents": [
{
"role": "orchestrator",
"model": "gpt-4-turbo",
"temperature": 0.2
}
],
"memory": "session",
"output_format": "structured_json"
}system_prompt.txt
system_prompt.txt
# OpenClaw System Prompt — Support Triage
# Level 2: Agency & SMB
ROLE: You are a specialised AI operator within the OpenClaw framework.
OBJECTIVE: Execute the "Support Triage" workflow with precision and minimal latency.
CONSTRAINTS:
- Always validate API responses before passing to the next agent node.
- Log all errors to the centralised OpenClaw error handler.
- Do not hallucinate external data. Only use verified API payloads.
- Adhere to rate limits for all integrated third-party services.
EXECUTION STEPS:
1. Receive context payload from the orchestrator.
2. Authenticate with required APIs (refer to context.json).
3. Execute the primary task as defined in the architecture overview.
4. Return a structured JSON response to the orchestrator.
# Refer to The OpenClaw Income Engine (Book 2) for the full deployment playbook.