customer-360
Build a comprehensive customer profile from Intercom data, including conversation history, account context, and interaction timeline. Use when the user asks to "look up a customer", "customer profile", "customer 360", "tell me about this customer", "summarize a customer's history", or provides a customer email or company name and wants a full picture.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- customer-360
- license
- MIT
- description
- Build a comprehensive customer profile from Intercom data, including conversation history, account context, and interaction timeline. Use when the user asks to "look up a customer", "customer profile", "customer 360", "tell me about this customer", "summarize a customer's history", or provides a customer email or company name and wants a full picture.
- argument-hint
- [email or company name]
- disable-model-invocation
- true
03 SKILL.md 正文
Customer 360
Produce a comprehensive customer profile by aggregating data from across the Intercom workspace.
Workflow
Step 1: Identify the Customer
- Parse the user's input for an email, name, or company
- Use
search_contactsto find the contact (by email is most reliable) - If company name given, search contacts by email domain
- Use
get_contactto fetch the full profile (attributes, tags, segments, companies)
Step 2: Gather Conversation History
- Use
search_conversationsfiltered to this contact's conversations - Paginate to get all conversations (not just the first page)
- For the most recent/relevant conversations, use
get_conversationfor full threads
Step 3: Build the Profile
Produce a markdown profile with these sections:
Contact Summary
- Name, email, role (user/lead), company
- Location, timezone, last seen
- Plan/tier (if available via custom attributes)
- Tags and segments
Conversation History
- Total conversation count
- Table: ID | Subject | State | Channel | Date
- Highlight any currently open/snoozed conversations
Key Themes
- Common topics across conversations
- Recurring issues or feature requests
- Sentiment signals (escalations, positive feedback)
Timeline
- Chronological list of significant interactions
- First contact → most recent activity
Open Items
- Unresolved conversations
- Pending questions or follow-ups
Step 4: Present and Offer Next Steps
- Present the profile
- Offer to dive deeper into any conversation
- Offer to search for similar customers (same company, same issues)
Best Practices
- Always cite conversation IDs so the user can find them in the Intercom inbox
- Note data freshness — states may have changed since events occurred
- If the contact has many conversations, summarize the most recent 10-15 and note the total count
- Handle cases where the contact exists but has no conversations
Troubleshooting
Contact Not Found
Symptom: No results for the provided email or name. Solution: Check for typos. Try searching by email domain to find related contacts. Ask the user to confirm the identifier.
Too Many Conversations
Symptom: Contact has 50+ conversations, making full analysis impractical. Solution: Focus on the most recent 10-15 conversations. Summarize older ones by theme rather than individually. Note the total count.
04 同仓库更多 Skills
business-data
暂无简介
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.