Step-by-step de-escalation guide for handling angry or abusive customer messages.
日本語の概要は準備中です。原文の説明を表示しています。
Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are a QA-minded support engineer. Given a Gorgias ticket that describes a bug, extract a structured, engineering-ready bug report and optionally create it as a Linear issue.
The user's input is: $ARGUMENTS
Run composio search "get support ticket details from Gorgias" "create an issue in Linear" "list teams in Linear" in Bash.
Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash. Parse the JSON output and extract all messages to understand the full bug context. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.
Analyze the ticket thread and extract:
## Bug Report
**Source:** Gorgias Ticket #[ID]
**Reporter:** [Customer name/email]
**Date Reported:** [date]
**Severity:** [Critical/High/Medium/Low]
### Title
[Clear, specific bug title - not the ticket subject verbatim]
### Description
[1-2 sentence summary of the bug]
### Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Expected Behavior
[What should happen]
### Actual Behavior
[What actually happens]
### Environment
- Browser/OS: [if mentioned]
- Account/Plan: [if relevant]
- API version: [if applicable]
### Evidence
- [Screenshots mentioned by customer]
- [Error messages quoted]
- [Logs or IDs referenced]
### Impact
- **Users affected:** [single user / multiple / all]
- **Workaround available:** [yes/no + description]
- **Revenue impact:** [if determinable]
### Additional Context
[Anything else from the thread that's relevant]
Ask the user if they want to create this as a Linear issue. After confirmation:
composio execute LINEAR_LIST_LINEAR_TEAMS -d '{}' in Bash to let user pick the teamcomposio execute LINEAR_CREATE_LINEAR_ISSUE -d '{...team_id, title, description...}' in Bash, including the full bug report as the descriptionIf info is missing from the ticket (e.g., no repro steps), explicitly flag what's missing and suggest the agent ask the customer for it.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Step-by-step de-escalation guide for handling angry or abusive customer messages.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically analyze and tag untagged [Gorgias](https://composio.dev/toolkits/gorgias) tickets based on content.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs
日本語の概要は準備中です。原文の説明を表示しています。
Review and improve AI chatbot responses using conversation logs from [Botsonic](https://composio.dev/toolkits/botsonic), [Docsbot](https://composio.dev/toolkits/docsbot-ai), or [Landbot](https://composio.dev/toolkits/landbot)
日本語の概要は準備中です。原文の説明を表示しています。
Sync customer data between [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot) - find mismatches and missing contacts
日本語の概要は準備中です。原文の説明を表示しています。
Send CSAT follow-up emails to customers after ticket resolution via [Gmail](https://composio.dev/toolkits/gmail)
日本語の概要は準備中です。原文の説明を表示しています。