Support AI Skill

Omnichannel Support

Unify customer support across all channels including email, chat, phone, social media, SMS, and in-app messaging into a single agent workspace with consistent context and routing. Use when configuring multi-channel integration, building unified agent views, implementing channel preference management, or creating cross-channel conversation continuity. Triggers on phrases like 'omnichannel', 'multi-channel support', 'unified agent view', 'channel routing', 'social media support', 'live chat integration', 'cross-channel context', 'channel preference', 'conversation continuity', 'in-app messaging'.

Omnichannel Support Operations

Unify customer interactions across email, live chat, phone, social media, SMS, and in-app messaging into a single agent workspace with consistent context, intelligent routing, and seamless conversation continuity.

Workflow

Phase 1: Channel Integration Setup

Connect all support channels:

Email: inbox integration (Gmail, Outlook, custom domain)
Live chat: website widget, mobile in-app chat
Phone: VoIP integration (Twilio, Aircall, RingCentral)
Social media: Facebook Messenger, Twitter/X, Instagram DM, LinkedIn Messaging
SMS: text messaging (Twilio, Bandwidth)
In-app messaging: product-embedded messaging (Intercom, Crisp, Zendesk Talk)
Self-service portal: web and mobile knowledge base

Build unified customer profile:

Aggregate contact data across all channels
Merge identities (email + phone + social + account ID)
Consolidate conversation history per customer
Track channel preference and usage patterns

Configure channel-specific settings:

Operating hours per channel (chat: 24/7, phone: business hours, email: 24/7)
Channel-specific SLAs (chat response: <2 min, email: <4 hours, social: <1 hour)
Auto-responders and away messages per channel
Channel routing rules (technical → chat, billing → email, urgent → phone)

Phase 2: Unified Agent Workspace

Single pane of glass:

All incoming conversations in unified queue (prioritized across channels)
Customer profile sidebar: history, tier, health score, open tickets, notes
Conversation view: full cross-channel history, not just current channel
Quick actions: macros, KB search, escalation, transfer, internal notes

Context preservation across channels:

Customer switches from chat to email → agent sees full context
Phone call follows email thread → auto-populate call notes with email content
Social media DM continues website chat → seamless transition
Channel switch notification: "Customer previously contacted via chat at 10:30 AM"

Smart channel routing:

Route based on: issue type, urgency, customer preference, agent skill + channel proficiency
Auto-suggest optimal channel to customer ("This is complex — would you prefer a phone call?")
Overflow routing between channels (chat → email when chat queue full)
VIP customers: always route to senior agents regardless of channel

Phase 3: Quality & Performance Monitoring

Cross-channel performance tracking:

Agent metrics by channel: handle time, resolution rate, CSAT
Channel metrics: volume, deflection rate, escalation rate, cost per contact
Consistency checks: same issue, same resolution regardless of channel

Channel optimization:

Identify underperforming channels (high volume, low resolution)
Adjust staffing based on channel demand patterns
Optimize self-service to reduce channel volume

Customer channel preference analytics:

Track preferred channel by customer segment
Monitor channel switch rate and reasons
Surface insights for channel strategy decisions

Templates

Channel Configuration Matrix

OMNICHANNEL CONFIGURATION MATRIX
=================================
Version: [3.0] | Last Updated: [Date]

CHANNEL SETUP:
┌──────────────┬────────────┬──────────────┬─────────────┬───────────────────┐
│ Channel      │ Platform   │ Hours        │ SLA (First  │ Routing Priority  │
│              │            │              │ Response)   │                   │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ Live Chat    │ Zendesk    │ 24/7         │ 2 minutes   │ P0/P1 only        │
│              │ Talk       │              │             │                   │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ Email        │ Gmail +    │ 24/7         │ 4 hours     │ All priorities    │
│              │ Zendesk    │              │             │                   │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ Phone        │ Aircall    │ Mon-Fri      │ Immediate   │ P0 only + VIP     │
│              │            │ 8am-6pm EST  │             │                   │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ Social Media │ Facebook,  │ 24/7         │ 1 hour      │ Public issues,    │
│              │ Twitter,   │              │             │ brand safety      │
│              │ Instagram  │              │             │                   │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ SMS          │ Twilio     │ 24/7         │ 30 minutes  │ Notifications,    │
│              │            │              │             │ 2FA, urgent alerts│
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ In-App       │ Intercom   │ 24/7         │ 5 minutes   │ Product questions,│
│              │            │              │             │ guided flows      │
├──────────────┼────────────┼──────────────┼─────────────┼───────────────────┤
│ Portal       │ Zendesk    │ 24/7         │ N/A         │ Self-service      │
│              │ Guide      │              │             │ (deflection)      │
└──────────────┴────────────┴──────────────┴─────────────┴───────────────────┘

AUTO-RESPONDERS:
  Chat (outside hours): "Our team is offline. Leave a message → email ticket created"
  Social (outside hours): "Thanks for reaching out! We'll respond within 4 hours."
  Email (received): "We've received your request. Expect a response within 4 hours."
  Phone (after hours): Voicemail → auto-email transcription to queue

CROSS-CHANNEL HANDOFF RULES:
  Chat → Email: Preserve full chat transcript; auto-attach to email ticket
  Email → Phone: Pre-populate call notes with email content; agent brief in <30 sec
  Social → Chat: Redirect to private chat for sensitive info; preserve social context
  Any → Escalation: Preserve all channel history; escalate with full context bundle

Unified Agent Workspace Layout

UNIFIED AGENT WORKSPACE — Ticket #48350
========================================

┌─────────────────────────────────────────────────────────────────┐
│  CUSTOMER PROFILE (sidebar)                                     │
│  ─────────────────────────────────                              │
│  Acme Corp | Enterprise | Health: 67/100                         │
│  Contact: Jane Smith, VP Operations                              │
│  Channels used: Email (12), Chat (3), Phone (1)                  │
│  Open tickets: 1 (this) | Closed (30d): 5                        │
│  Preferences: prefers email for complex issues                   │
│  Notes: "Escalated to phone last month for billing dispute"      │
├─────────────────────────────────────────────────────────────────┤
│  CONVERSATION HISTORY (cross-channel, chronological)             │
│  ─────────────────────────────────                              │
│                                                                  │
│  [Email] Jan 10 09:15 — Jane: "Our API integration keeps         │
│              timing out since the last update."                  │
│  [Agent] Jan 10 09:22 — Mike: "Let me check your API logs..."    │
│  [Agent] Jan 10 10:45 — Mike: "Found the issue. We've patched..."│
│  [Email] Jan 10 11:00 — Jane: "Still happening. Here's a log."   │
│  [Chat]  Jan 15 14:20 — Jane: "Is this fixed? Getting timeouts   │
│              again. This is urgent."                             │
│                                                                  │
│  Current channel: Live Chat                                     │
│  Agent: You (Sarah) | Assigned: 14:22 UTC                       │
│                                                                  │
│  ┌───────────────────────────────────────────────────────────┐  │
│  │ YOUR RESPONSE:                                            │  │
│  │                                                           │  │
│  │ "Hi Jane, I can see this has been frustrating. I have the │  │
│  │ full context from your email on Jan 10. Let me check the   │  │
│  │ current status of the patch right now..."                  │  │
│  │                                                           │  │
│  │ [Send] [Add internal note] [Escalate] [Transfer]          │  │
│  └───────────────────────────────────────────────────────────┘  │
│                                                                  │
│  Quick Actions:                                                  │
│  [🔍 KB Search] [📋 Macro] [📞 Transfer to Phone] [⚠ Escalate]   │
│  [📝 Internal Note] [🔗 Link Ticket] [✅ Resolve]                │
└─────────────────────────────────────────────────────────────────┘

Integration Points

Omnichannel platform: Zendesk, Front, Intercom, Freshdesk, Salesforce Service Cloud
VoIP/Phone: Twilio, Aircall, RingCentral, Plivo
Social media: Facebook Graph API, Twitter API, Instagram API, LinkedIn API
SMS: Twilio, Bandwidth, MessageBird
Chat: Zendesk Talk, Intercom Messenger, Crisp, Tidio
Email: Gmail API, Microsoft Graph API, SendGrid, Postmark
CRM: Salesforce, HubSpot (customer profile enrichment)
Analytics: Tableau, Power BI (channel performance dashboards)
CTI integration: Computer Telephony Integration for screen pop on incoming calls
IVR system: Auto-attendant with ticket status check and self-service options

Edge Cases

| Scenario | Handling | |----------|----------| | Customer starts on chat, switches to email mid-conversation | Preserve full chat history in email ticket; agent sees complete context | | Social media public complaint | Immediate public acknowledgment → move to private DM → create ticket | | Phone call while agent handling chat with same customer | Screen pop with full context; offer callback if agent busy | | Channel-specific compliance (GDPR on social, HIPAA on phone) | Channel-specific data handling rules; PII masking where required | | Multi-language customer switches channels | Language detection persists across channels; route to language-capable agent | | Channel outage (chat platform down) | Auto-route to backup channel; customer notification; SLA extension | | Spam/bot traffic on social media | Bot detection filters; auto-archive; rate limiting | | Customer messages on closed ticket via new channel | Reopen ticket with new channel thread; preserve resolution history |

Output

Omnichannel Performance Dashboard

OMNICHANNEL PERFORMANCE — Weekly Report
=========================================
Period: Jan 8-15, 2025

CHANNEL VOLUME DISTRIBUTION:
  Email:        1,247 contacts [34.2%] ██████████████████████
  Live Chat:      892 contacts [24.5%] ████████████████
  Phone:          423 contacts [11.6%] ████████
  Social Media:   312 contacts [ 8.6%] ██████
  In-App:         287 contacts [ 7.9%] ██████
  SMS:            156 contacts [ 4.3%] ████
  Portal (self):  389 contacts [10.7%] ████████ (deflected, no agent)
  ────────────────────────────────────────
  Total:        3,688 contacts

CHANNEL PERFORMANCE:
┌──────────────┬────────────┬────────────┬────────────┬──────────────┐
│ Channel      │ Avg Handle │ First Res. │ Resolution │ CSAT Score   │
│              │ Time       │ Time       │ Rate       │              │
├──────────────┼────────────┼────────────┼────────────┼──────────────┤
│ Live Chat    │ 8.2 min    │ 1.4 min    │ 71.3%      │ 4.4/5.0      │
│ Email        │ 22.5 min   │ 3.1 hours  │ 82.1%      │ 4.2/5.0      │
│ Phone        │ 11.8 min   │ Immediate  │ 76.8%      │ 4.5/5.0      │
│ Social Media │ 15.3 min   │ 42 min     │ 68.4%      │ 4.1/5.0      │
│ In-App       │ 6.4 min    │ 2.1 min    │ 79.2%      │ 4.6/5.0      │
│ SMS          │ 3.2 min    │ 12 min     │ 65.3%      │ 4.3/5.0      │
└──────────────┴────────────┴────────────┴────────────┴──────────────┘

CROSS-CHANNEL METRICS:
  Channel switch rate: 12.3% (customer uses 2+ channels per issue)
  Context preserved on switch: 94.7%
  Average channels per resolved issue: 1.4
  Cost per contact (by channel):
    Self-service: $0.08 | Chat: $2.10 | Email: $3.40 | Phone: $5.80 | Social: $4.20

SELF-SERVICE DEFLECTION:
  Portal articles viewed before contact: 67%
  Deflected contacts (no agent needed): 389 (10.7%)
  Top deflecting articles: "Reset Password", "API Rate Limits", "Export Guide"

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.