---
title: "Live Support Module"
module_id: "liveSupport"
version: "1.0.0"
category: "communication"
autonomy: "view-required"
generated: true
generated_at: "2026-05-04"
---

# Live Support

> Human agent takeover for escalated chat conversations

Ships with **3 agent skills**, an **admin UI**.

## Quick Facts

| Property | Value |
|----------|-------|
| **Module ID** | `liveSupport` |
| **Version** | 1.0.0 |
| **Category** | communication |
| **Autonomy** | view-required |
| **Core** | No |
| **Capabilities** | `data:read`, `data:write` |
| **MCP-exposed skills** | 3 |
| **Owns tables** | — |

## Skills

These skills are seeded into `agent_skills` when the module is enabled and exposed via MCP.
External operators (FlowPilot, OpenClaw, Claude Desktop, custom MCP clients) can call them directly.

| Skill | Scope | Description |
|-------|-------|-------------|
| `support_list_conversations` | internal | List support conversations filtered by status. Returns customer name, email, priority, sentiment, and escalation reason. Use when: reviewing support queue; monitoring overall support load; identify… |
| `support_assign_conversation` | internal | Assign or reassign a support conversation to an agent. Use when: a customer query needs agent attention; re-routing a conversation to a specialist; ensuring no support ticket is unassigned. NOT for… |
| `support_get_feedback` | internal | Retrieve chat feedback ratings and comments. Useful for monitoring customer satisfaction and identifying knowledge gaps. Use when: pulling raw feedback data; building satisfaction reports; reviewin… |

## Module API Contract

**Actions:** `list_conversations`, `assign`

**Input fields:** `action`, `conversation_id`, `agent_id`

**Output fields:** `success`, `message`, `error`

## File Map

| Purpose | Path |
|---------|------|
| Module definition | `src/lib/modules/live-support-module.ts` |
| Admin page | `src/pages/admin/LiveSupportPage.tsx` |

## Contributing

To enhance this module, see [Contributing Guide](../contributing/contributing.md).

Key rules:
- Follow `ModuleDefinition<I, O>` contract pattern
- All schema changes require idempotent migrations
- Skills must be self-describing ([Law 2](../concepts/openclaw-law.md))
- Blocks are interfaces, not pipelines ([Law 3](../concepts/openclaw-law.md))
- New skills must pass the [Agent Contract Integrity](../architecture/agent-contract-integrity.md) checklist (`bun run lint:skills`)

---

*This file is auto-generated by `scripts/generate-module-docs.ts`. Do not edit manually — re-run the script after changing the module definition.*