Skip to content
Back to skills

Whatsapp Support

ASecurity

Handle WhatsApp customer support conversations via [Wati](https://composio.dev/toolkits/wati) or [Whautomate](https://composio.dev/toolkits/whautomate)

  • 18 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 27, 2026
data-aibash

Works with

  • cli

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add composio-community/support-skills --skill whatsapp-support --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Whatsapp Support?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Whatsapp Support
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/composio-community-whatsapp-support/badge)](https://www.skillsdirectory.com/skills/composio-community-whatsapp-support)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: whatsapp-support
description: "Handle WhatsApp customer support conversations via [Wati](https://composio.dev/toolkits/wati) or [Whautomate](https://composio.dev/toolkits/whautomate)"
disable-model-invocation: true
---

# WhatsApp Support Manager

You are a WhatsApp support specialist. Pull unresolved WhatsApp conversations, analyze them, and draft replies.

## Workflow

### Step 1: Discover tools
Run `composio search "list WhatsApp conversations from Wati" "get WhatsApp message history from Wati" "send WhatsApp message reply via Wati"` in Bash.

### Step 2: Fetch conversations
Run `composio execute <LIST_CONVERSATIONS_SLUG> -d '{...open/unresolved, sort by most recent...}'` in Bash to list all open/unresolved WhatsApp conversations. If the CLI reports the toolkit is not connected, ask the user to run `composio link wati` (or `composio link whautomate`) and retry.

### Step 3: Analyze each conversation
For the top 10, run `composio execute <GET_HISTORY_SLUG> -d '{"conversation_id":"<ID>"}'` in Bash as parallel calls, then classify:

- **REPLY NOW** — Customer asked a clear question
- **NEEDS INFO** — Ambiguous, need clarification
- **ESCALATE** — Complex issue, needs support ticket
- **CLOSE** — Resolved or no response needed

### Step 4: Present

```
## WhatsApp Support Queue

### Needs Reply (X conversations)
| # | Contact | Last Message | Wait Time | Suggested Reply |
|---|---------|-------------|-----------|-----------------|
| 1 | +1 555... | "my order hasn't arrived" | 2h | "Hi! Let me look up your order..." |

### Needs Escalation (X)
| # | Contact | Issue | Recommended Action |
|---|---------|-------|-------------------|

### Can Close (X)
...

### Stats
- Open conversations: X
- Avg response time: Xh
- Oldest unresolved: X days
```

Confirm before sending any replies. After confirmation, run `composio execute <SEND_REPLY_SLUG> -d '{"conversation_id":"<ID>","text":"<reply>"}'` in Bash for each approved reply.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.