composio-community

Analyze ticket history to identify patterns and generate reusable support macros/playbooks.

Rewrite a support response in a different tone - formal, casual, technical, empathetic, or concise.

Identify churned or at-risk customers and draft personalized winback emails

Analyze customer message text for sentiment, urgency, and emotional tone.

Check SLA compliance across open tickets and flag breaches or at-risk tickets

Pull open tickets from [Zendesk](https://composio.dev/toolkits/zendesk) and triage by priority, category, and SLA status

Set up customer outreach sequences via [Lemlist](https://composio.dev/toolkits/lemlist), [Reply.io](https://composio.dev/toolkits/reply-io), or [Woodpecker](https://composio.dev/toolkits/woodpecker-co)

Translate a customer message and draft a reply in their language.

Escalate a support ticket to a [Linear](https://composio.dev/toolkits/linear) issue and notify the team on [Slack](https://composio.dev/toolkits/slack).

Sync customer data between [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot) - find mismatches and missing contacts

Summarize a support ticket thread into key points and action items.

Bulk verify customer email addresses using [Clearout](https://composio.dev/toolkits/clearout) or [Mailcheck](https://composio.dev/toolkits/mailcheck)