Support AI Skill
Async Video Messaging Support
Allow customers and agents to send asynchronous video messages for clearer communication without requiring real-time availability. Use when implementing async video support, managing video ticket exchanges, creating video responses to complex issues, handli...
Async Video Messaging Support
Enable customers and agents to exchange asynchronous video messages — recording and sending short video explanations without requiring both parties to be available at the same time.
Workflow
- Customer or agent determines issue is complex to explain via text.
- Customer/agent records short video message (2–3 minutes max).
- Video uploaded and attached to support ticket.
- Recipient receives notification with video link.
- Recipient watches video at their convenience.
- Recipient responds via video reply, text, or combination.
- Video conversation thread maintained within ticket.
- AI generates transcript from video for searchability.
- Resolution tracked; session analytics logged.
Async Video Platform Setup
VIDEO MESSAGING IMPLEMENTATION
================================
Option 1 — Loom Integration (Recommended for most teams):
→ Platform: Loom (loom.com)
→ Features: Screen + camera recording, auto-hosting, transcription,
commenting, analytics
→ Pricing: Free (25 videos, 5 min each), Starter $8/mo, Pro $15.83/mo
→ Help desk integration: Native integrations with Zendesk, Intercom, Jira
→ Pros: Easy setup, familiar to most users, excellent UX
→ Cons: Limited customization, Loom branding on free plan
→ Best for: Quick adoption, non-technical teams
Option 2 — Built into Help Desk Platform:
→ Platforms: Intercom (video messages), Front (video responses),
Help Scout (video notes)
→ Features: Native ticket integration, no separate platform needed
→ Pricing: Included in premium plans
→ Pros: Seamless workflow, no context switching
→ Cons: Limited to help desk's video features
→ Best for: Teams already on premium help desk plans
Option 3 — Custom WebRTC Video Messaging:
→ Build: Browser-based video recording embedded in help desk
→ Features: Fully branded, custom storage, deep integration
→ Pricing: Development cost ($20K–$50K initial) + hosting ($500–$2K/mo)
→ Pros: Full customization, branded experience
→ Cons: Development effort, ongoing maintenance
→ Best for: Large enterprises wanting fully branded experience
Option 4 — Third-Party Video Platforms:
→ Platforms: Vidyard, BombBomb, Vidyo
→ Features: Advanced analytics, personalization, A/B testing
→ Pricing: $99–$499/month
→ Pros: Enterprise features, analytics, integrations
→ Cons: Higher cost, may be overkill for support use
→ Best for: Teams wanting video analytics and personalization
PLATFORM SELECTION CRITERIA:
════════════════════════════════════════════════════════════════════════
Criteria | Weight | Loom | Help Desk | Custom | Vidyard
════════════════════════════════════════════════════════════════════════
Ease of setup | 20% | 10 | 10 | 4 | 7
Ticket integration | 25% | 7 | 10 | 10 | 6
Cost | 20% | 9 | 8 | 5 | 6
Features | 20% | 8 | 6 | 10 | 9
Scalability | 15% | 7 | 7 | 9 | 9
════════════════════════════════════════════════════════════════════════
Customer Video Messaging Experience
CUSTOMER VIDEO RECORDING FLOW
===============================
Trigger Points (when to offer video to customer):
→ Customer submits ticket with "hard to explain" language
→ Ticket has 3+ back-and-forth exchanges without resolution
→ Customer uploads screenshot but issue still unclear
→ Agent determines visual explanation would help
→ Customer explicitly requests video option
Step 1 — Agent Offers Video Option:
Template: "Hi [Name], it sounds like this might be easier to explain
visually. Would you like to record a quick video showing me what you're
seeing? You can click here to record: [link]. No app install needed —
it works right in your browser. Videos up to 3 minutes."
Step 2 — Customer Records Video:
→ Browser-based recording (no download/install)
→ Options:
- Screen only (showing their issue)
- Camera only (talking to agent)
- Screen + camera (picture-in-picture, recommended)
→ Recording controls: Start, pause, stop, retake
→ Time limit: 3 minutes (enough for explanation, prevents overly long videos)
→ Privacy: Customer preview before submitting
Step 3 — Video Submitted to Ticket:
→ Video auto-uploaded and hosted
→ Ticket updated with video link
→ Agent receives notification: "New video from [Customer] on ticket #12345"
→ AI generates transcript (automatic)
Step 4 — Agent Reviews and Responds:
→ Agent watches video (or reads transcript for quick understanding)
→ Agent records video response demonstrating solution:
- "Hi [Name], thanks for the video! I can see the issue now.
Here's how to fix it: [demonstrates steps on screen]"
→ Video response attached to ticket
→ Customer receives notification: "[Agent] replied with a video on your ticket"
STEP-BY-STEP RESOLUTION TIMELINE:
════════════════════════════════════════════════════════════════════════
Event | Time Elapsed | Action
════════════════════════════════════════════════════════════════════════
Ticket created | T+0:00 | Customer submits issue
Agent offers video option | T+0:30 | "Want to send a video?"
Customer records video | T+2:00 | 3-minute video submitted
Agent reviews video | T+4:00 | Watches video + transcript
Agent records video response | T+6:00 | Demonstrates solution
Customer watches response | T+12:00 | At customer's convenience
Issue resolved | T+12:05 | Customer confirms fix
════════════════════════════════════════════════════════════════════════
Total: ~12 hours (async) vs 45+ minutes (real-time video call)
════════════════════════════════════════════════════════════════════════
Agent Video Response Guidelines
AGENT VIDEO RESPONSE BEST PRACTICES
=====================================
Video Structure (for agent responses):
1. Opening (5 seconds): "Hi [Name], [Agent] here. Let me show you how to fix [issue]."
2. Context (10 seconds): "Based on what you showed me, the issue is [brief explanation]."
3. Solution demonstration (30–90 seconds): Step-by-step walkthrough on screen
4. Verification (10 seconds): "Now you should see [expected result]. Let me know if it works!"
5. Closing (5 seconds): "Anything else I can help with? - [Agent]"
Content Guidelines:
→ Keep videos under 3 minutes (if longer, split into multiple videos)
→ Speak clearly and at moderate pace
→ Use screen annotations (arrows, circles, highlights) to draw attention
→ Close unnecessary browser tabs before recording (clean workspace)
→ Use customer's name to personalize
→ Show the actual product interface (not slides or documentation)
→ End with clear next step or call-to-action
Technical Setup:
→ Screen resolution: 1080p minimum (clear visibility)
→ Audio: Use headset microphone (clearer than laptop mic)
→ Lighting: Well-lit room if camera is visible
→ Background: Professional or neutral (if camera on)
→ Test recording: 10-second test before full recording
VIDEO RESPONSE TEMPLATES:
════════════════════════════════════════════════════════════════════════
Use Case | Video Length | Content Focus
════════════════════════════════════════════════════════════════════════
Troubleshooting | 1–3 min | Step-by-step fix demonstration
Feature explanation | 2–3 min | Walkthrough of feature capabilities
Setup guidance | 3 min | End-to-end setup process
Error resolution | 1–2 min | Reproduce error + show fix
Account configuration | 2–3 min | Navigate settings + configure
════════════════════════════════════════════════════════════════════════
Analytics and Performance Measurement
ASYNC VIDEO METRICS
====================
Volume Metrics:
════════════════════════════════════════════════════════════════════════
Metric | Target
════════════════════════════════════════════════════════════════════════
Video messages sent (agent → customer)| Track monthly
Video messages received (customer) | Track monthly
Video adoption rate (tickets with video)| > 10%
Avg video length (customer) | 2–3 minutes
Avg video length (agent) | 1.5–2.5 minutes
════════════════════════════════════════════════════════════════════════
Effectiveness Metrics:
════════════════════════════════════════════════════════════════════════
Metric | Target
════════════════════════════════════════════════════════════════════════
Resolution rate (video tickets) | > 88%
Back-and-forth reduction | > 65% fewer exchanges
CSAT (video tickets) | > 4.8/5.0
Time to resolution (video vs text) | 40% faster
Customer video completion rate | > 90%
Agent video completion rate | > 95%
════════════════════════════════════════════════════════════════════════
ROI Analysis:
→ Video ticket: 1 video exchange resolves (avg 2 videos per ticket)
vs Text ticket: 5–8 message exchanges (avg)
→ Agent time saved: 15 minutes per video-resolved ticket
→ Customer effort saved: No need to schedule real-time call
→ Calculation:
100 video tickets/month × 15 min saved × $0.50/min agent cost
= $750/month agent time savings
Plus: Higher CSAT, faster resolution, better customer experience
VIDEO vs TEXT COMPARISON:
════════════════════════════════════════════════════════════════════════
Metric | Text Ticket | Video Ticket | Improvement
════════════════════════════════════════════════════════════════════
Messages per ticket | 6.5 | 2.0 | -69%
Resolution time | 18 hours | 12 hours | -33%
CSAT score | 4.2/5.0 | 4.8/5.0 | +14%
First-contact resolution| 55% | 88% | +60%
Agent handle time | 12 min | 8 min | -33%
Customer effort (1–10) | 6 | 3 | -50%
════════════════════════════════════════════════════════════════════════
Integration Points
- Loom: Video recording, hosting, transcription, commenting, analytics, help desk integrations
- Help Desk (Zendesk, Intercom, Freshdesk): Ticket attachment, video thread, notification triggers
- AI Transcription (Rev.com, AssemblyAI, Deepgram): Auto-transcribe video for searchability and accessibility
- Video Hosting (AWS S3, Cloudflare R2): Scalable video storage, CDN delivery
- CRM (Salesforce, HubSpot): Video interaction logging, customer engagement tracking
- Analytics (Tableau, Power BI): Video metrics dashboards, effectiveness reporting
- Accessibility (YouTube captions, Otter.ai): Subtitle generation, screen reader compatibility
- Security: Video encryption at rest, access controls, retention policy enforcement
Edge Cases
- Customer doesn't know how to record video: Technical barrier
- Provide step-by-step guide with screenshots
- Offer phone support as alternative
- Keep video option as secondary, not primary channel
- Consider: Simple one-click recording button in help desk
- Training: "How to record your first video" quick tutorial
- Video too long or unclear: Customer sends 10-minute rambling video
- Politely guide: "Thanks for the detailed video! To help me focus,
- Set expectations: "Videos under 3 minutes work best for quick resolution"
- Use transcript: Read transcript to find key points without watching full video
- Offer real-time call if video exchange becomes inefficient
could you show me specifically [the one issue]?"
- Agent reluctant to record videos: Camera shy or time concerns
- Training: Provide recording tips and templates
- Start with screen-only videos (no camera needed)
- Show data: Video tickets resolve faster, higher CSAT
- Recognize: Highlight agents with best video responses
- Time budget: Allocate 5 minutes for recording (saves 15+ minutes overall)
- Video storage and retention: Videos accumulate and consume storage
- Compression: Auto-compress videos to reduce file size
- Retention policy: Delete videos after ticket closed + 90 days
- Transcription priority: Keep transcript, delete video after retention period
- Storage cost monitoring: Track video storage costs per month
- Target: < $100/month storage for typical support volume
- Accessibility requirements: Customers with hearing or visual impairments
- Auto-generate subtitles/transcripts for all videos
- Ensure transcripts are accurate (AI + human review for critical tickets)
- Offer text alternative: "Would you prefer a text explanation instead?"
- Screen reader compatibility: Video descriptions in ticket thread
- Compliance: WCAG 2.1 AA standards for video content
- Cross-time-zone advantage: Key benefit of async video
- Customer in Tokyo records video at 10 AM JST
- Agent in New York watches at 9 AM EST (same calendar day)
- Agent records response at 10 AM EST
- Customer watches at 11 PM JST (same calendar day)
- Resolution achieved within same business day despite 14-hour timezone difference
- Track: Time-zone-spanning video resolutions as success metric
- Video quality issues: Poor audio, blurry screen, low resolution
- Provide minimum quality guidelines to customers
- Agent side: Ensure good quality (professional expectation)
- If customer video is unclear: "I'm having trouble seeing the details —
- Fallback: If video unusable, switch to text or phone
could you try again with your screen zoomed in?"
- Security and PII in videos: Sensitive data visible in recordings
- Customer side: Warn about visible sensitive data before recording
- Agent side: Never record with sensitive customer data visible
- Blurring: Use annotation tools to blur PII if accidentally captured
- Retention: Delete videos with PII immediately after resolution
- Policy: "Do not include passwords, credit cards, or personal data in videos"