--- name: unified-inbox-management description: Manage customer support across all channels in a single unified inbox, including email, chat, social media, phone, and messaging apps. Use when setting up omnichannel support operations, configuring unified inbox tools, managing channel-specific workflows, balancing workload across channels, or improving agent efficiency through unified tools. Triggers on phrases like "unified inbox", "omnichannel inbox", "single inbox", "multi-channel support", "all channels one place", "inbox management", "channel consolidation", "support inbox". --- # Unified Inbox Management Manage all customer support channels from a single unified inbox. ## Workflow ### Unified Inbox Setup Trigger: New support tool implementation; channel consolidation; agent efficiency initiative: 1. **Channel audit**: Inventory all incoming support channels (email, live chat, WhatsApp, Facebook Messenger, Twitter/X, SMS, phone, in-app messaging, community forum); quantify volume per channel (tickets/hour, peak times); assess current tools per channel. 2. **Tool selection**: Evaluate unified inbox platforms (Front, Intercom, Zendesk, Help Scout, Freshdesk); compare features (channel integrations, collaboration, automation, reporting, pricing); select based on channel coverage and team size. 3. **Integration configuration**: Connect each channel to unified inbox — email (SMTP/IMAP or API), chat (widget or API), social (platform APIs), phone (VoIP integration), messaging (WhatsApp Business API, Messenger API); test each integration. 4. **Routing rules**: Define assignment rules per channel — email → round-robin; chat → available agent; social → social specialist; phone → phone queue; VIP customer → senior agent; combine with skill-based routing. 5. **Collaboration setup**: Configure internal collaboration features — @mentions, internal notes, ticket sharing, draft sharing, customer-facing vs. internal visibility; establish collaboration guidelines. 6. **Automation rules**: Set up auto-response, auto-assignment, auto-tagging, SLA timers, escalation rules, canned response suggestions; test rules to prevent conflicts. 7. **Agent training**: Train agents on unified inbox navigation, multi-channel handling, collaboration features, quick actions; practice with sample tickets from each channel. 8. **Go-live and optimization**: Soft launch with 50% of agents; monitor channel performance, assignment accuracy, SLA compliance; optimize routing rules; full launch. ### Channel-Specific Workflows ``` CHANNEL WORKFLOWS — UNIFIED INBOX CONFIGURATION ================================================== Channel 1: Email Volume: ~35% of total tickets Response SLA: 4 hours (business hours) / 8 hours (after hours) Routing: Round-robin within skill group Auto-tagging: By subject keyword (billing, technical, account) Templates: Yes — full canned response library Collaboration: Internal notes, @mentions, draft sharing Special rules: - VIP customer email → Priority: High + assign to senior agent - Reply to resolved ticket → reopen automatically - Attachment > 10MB → notify agent to check separately Channel 2: Live Chat Volume: ~25% of total tickets Response SLA: < 30 seconds to accept Routing: First available agent with matching skill Auto-tagging: By chat topic selection (if customer uses menu) or NLP Templates: Yes — quick reply snippets (shorter than email) Collaboration: Barge-in (agent joins active chat to help); handoff Special rules: - Wait time > 2 minutes → offer callback or email option - Chat abandoned → follow-up email within 1 hour - Sentiment negative → escalate to senior agent Channel 3: WhatsApp Volume: ~10% of total tickets (growing) Response SLA: 1 hour Routing: WhatsApp-specialized agents (if bilingual, assign bilingual) Auto-tagging: By keyword detection Templates: Yes — WhatsApp-approved templates (pre-approved by Meta) Collaboration: Internal notes, @mentions Special rules: - Message template approval required for outbound - 24-hour messaging window (must reply within 24 hours to continue) - Media files (images, voice notes) supported - Opt-out management required Channel 4: Social Media (Twitter/X, Facebook) Volume: ~8% of total tickets Response SLA: 1 hour (public visibility requires fast response) Routing: Social media specialist or rotating assignment Auto-tagging: By platform + keyword Templates: Yes — social-optimized (shorter, brand voice) Collaboration: Internal notes (customer sees only public reply) Special rules: - Public vs. private: Move to DM when sharing sensitive info - Brand mention monitoring (even without @mention) - Crisis mode: All social alerts to war room during incidents - Sentiment tracking: Negative public posts escalated immediately Channel 5: Phone/VoIP Volume: ~12% of total tickets Response SLA: < 20 seconds ring time; < 2 minutes wait Routing: Skill-based + round-robin within skill group Auto-tagging: Post-call summary by AI transcription Templates: Yes — call scripts, post-call email templates Collaboration: Warm transfer; conference call; call recording Special rules: - Call recording for quality assurance - Post-call summary auto-generated from transcription - Callback scheduling if queue wait > 5 minutes - Voicemail → auto-create ticket from transcription Channel 6: In-App Messaging Volume: ~10% of total tickets Response SLA: 2 hours Routing: Context-aware (feature-specific routing) Auto-tagging: By in-app context (page, feature, action) Templates: Yes — contextual quick replies Collaboration: Internal notes, screen context sharing Special rules: - Context capture: Screenshot of customer's current screen - Feature-specific routing: API question → technical agent - Push notification follow-up if message unanswered in 4 hours ``` ### Inbox Analytics Dashboard ``` UNIFIED INBOX PERFORMANCE METRICS =================================== Period: Last 30 days Volume by Channel: Email: 3,500 tickets (35%) Avg response: 3.2 hours Live Chat: 2,500 tickets (25%) Avg response: 22 seconds WhatsApp: 1,000 tickets (10%) Avg response: 45 minutes Social Media: 800 tickets (8%) Avg response: 38 minutes Phone: 1,200 tickets (12%) Avg response: 15 seconds ring In-App: 1,000 tickets (10%) Avg response: 1.5 hours ────────────────────────────────────────────── Total: 10,000 tickets SLA Compliance by Channel: Email: 94% (target: 95%) ← NEEDS IMPROVEMENT Live Chat: 98% (target: 95%) WhatsApp: 91% (target: 90%) Social Media: 88% (target: 90%) ← NEEDS IMPROVEMENT Phone: 97% (target: 95%) In-App: 96% (target: 95%) Agent Utilization: Average active tickets per agent: 12.5 Channel distribution per agent: 3.2 channels handled daily Most utilized channel: Email (agents spend 40% of time) Least utilized channel: In-App (agents spend 8% of time) Peak Hours Analysis: Highest volume: 10:00–11:00 AM EST (email + chat spike) Lowest volume: 2:00–4:00 AM EST (primarily phone + WhatsApp international) Staffing alignment: 80% match (need more agents 10–11 AM) Optimization Opportunities: 1. Add 2 agents for 10–11 AM peak (email + chat coverage) 2. Improve social media SLA (88% → 90%): Add social specialist or auto-response 3. WhatsApp growing 15% MoM: Plan capacity increase for Q2 4. Email SLA gap: Implement auto-categorization to speed routing ``` ## Edge Cases - **Channel conflict** (same customer contacts via email and chat about same issue): - Detection: Cross-channel duplicate detection (same customer, similar subject, within 2 hours) - Handling: Link tickets across channels; agent sees "related ticket" notification; consolidate communication - Prevention: Chat pre-screen: "Do you have an open ticket about this?" before starting new chat - Customer experience: Never make customer repeat themselves; agent has full cross-channel context - **After-hours channel management** (different channels need different after-hours handling): - Email: Auto-response with expected response time; SLA pauses until business hours - Chat: Route to chatbot or show "offline" message with callback scheduling - WhatsApp: Auto-reply within 24-hour window; or show business hours message - Phone: Voicemail with callback option; or route to international team (follow-the-sun) - Social: Auto-response acknowledging; or silence with monitoring for urgent mentions - **Agent channel specialization vs. generalization** (should agents handle all channels or specialize?): - Specialization: Higher quality per channel; faster response; deeper expertise - Generalization: Better workload balancing; cross-training; coverage flexibility - Hybrid approach: Core channel (primary) + secondary channel (backup); train all agents on email + chat; specialize for phone, social, WhatsApp - Metrics: Track performance by agent-channel combination; identify best-fit assignments - **Message threading** (maintaining conversation context across channel switches): - Example: Customer starts via chat, then emails follow-up, then messages on WhatsApp - Requirement: Unified thread shows all channel interactions in chronological order - Technical: Each channel interaction appended to same ticket; channel icon indicates source - Agent training: Read full thread before responding; acknowledge channel switch ("Thanks for following up via email") - Challenge: Some channels don't support rich formatting; adapt response format per channel - **Volume spike management** (sudden influx from incident, product launch, or viral social media): - Detection: Volume > 3× normal in 1-hour window; alert to support manager - Response: Pause non-urgent automations; redirect to self-service; activate overflow agents; extend SLAs temporarily - Communication: Update expected wait times on all channels; proactive incident notification if service-related - Recovery: Post-spike review — what caused it? Can it be prevented? Update capacity planning ## Integration Points - **Unified inbox platforms**: Front, Intercom, Zendesk, Help Scout, Freshdesk, Crisp - **Email**: Gmail, Microsoft 365, custom SMTP/IMAP — email channel integration - **Chat**: LiveChat, Tawk.to, custom widget — live chat integration - **Messaging**: WhatsApp Business API, Twilio, Facebook Messenger — messaging channels - **Social media**: Twitter/X API, Facebook Graph API, Instagram — social channel integration - **Phone**: Twilio, Aircall, RingCentral, Five9 — VoIP integration, call recording - **In-app**: Intercom, Crisp, custom SDK — in-app messaging integration - **CRM**: Salesforce, HubSpot — customer context, account data - **Knowledge base**: Zendesk Guide, Confluence — article suggestions, deflection - **Analytics**: Custom dashboard, Tableau, Power BI — multi-channel performance metrics - **Automation**: Zapier, Make, custom — routing rules, auto-tagging, escalation workflows