customer_support · saas · workflow
Browserbase builds a generalized internal AI agent (bb) that automates knowledge work across engineering, ops, sales, and support
Browserbase had manual workflows for session investigation and PR writing, with no unified automation layer for knowledge work that happens in web apps without clean APIs.
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 · User invokes bb in Slack
Someone types @bb in a Slack channel and the Slack events handler dispatches to an internal endpoint.
Tools used
OpenCodeSlackSnowflake · partnerHubSpot · partnerPylon · partnerCirclebackGrafana · partnerTinybirdLokiNATSLinearGitHub CLITailscaleBrowserbase Platform
Outcome
The agent bb runs the feature request pipeline at 100% coverage with zero human effort, reduced first response time by 99% to under 24 hours, and cut session investigation from 30–60 minutes to a single Slack message.
Results
Time saved99%
Volume100%
Grounding & classification
Source type: technical build writeup
47 fields verified against source quotes, 1 dropped as unverifiable.
agentic workflowai agentcode generationdata extractioncode diff prknowledge basemeeting recordingsupport ticketbuilder submittedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwareautomation ratecycle time reductionemployee productivityresponse time reductiontechnical build writeupback office opscustomer supportit supportsales opsagentic task executionautonomous resolutionextract classify route