customer_support · saas · workflow
Frame.io uses Intercom to provide personalized support to 2M customers
Frame.io's customer base grew more than 11 times in size, creating pressure to scale support beyond the founding team. Previous tools Help Scout and Zendesk each fell short: Help Scout's ticketing wasn't suitable for their needs, and Zendesk required significant design and engineering resources to configure.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Customer reaches out
Customers initiate contact through Intercom's conversational support, generating 4,500 conversations each month.
Tools used
IntercomCustom BotsHelp ScoutZendesk
Outcome
First-response time was reduced from 3 hours to 15 minutes (an 87.5% reduction), the team now supports two million customers handling 4,500 conversations per month, and workload management improved team morale.
What failed first
Help Scout's ticketing solution was not suitable for Frame.io's needs, and Zendesk required design and engineering resources to configure rather than being a plug-and-play solution.
Results
Time saved87.5%
Volumetwo million
Grounding & classification
Source type: vendor customer story
33 fields verified against source quotes.
chatbotconversational aiknowledge basesupport ticketfailure mode describedhuman review describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedmediasoftwareemployee productivityresponse time reductionthroughput increasevendor customer storycustomer supportticket triageautonomous resolutionescalation workflow