As Persona scaled, engineers were overwhelmed by a firehose of technical questions in the #ask-engineers Slack channel, sales and compliance teams wasted hours manually compiling lengthy RFP responses from scattered past materials, and solutions engineers lost significant time writing SRDs from call transcripts.
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 · Question submitted in Slack
Employees submit questions in the #ask-engineers Slack channel.
Tools used
DustPersonaEngineerRFPNerdSRDNerd
Outcome
Within six months, AI agent adoption reached more than 80% of Persona's employee base across 11 of 13 departments. Fraud analysts reduced SQL query work from hours to under 30 minutes, and RFP responses that previously took days are now generated in a fraction of the time.
What failed first
Persona's first Dust deployment was a brittle v0 multi-agent system chained with Zapier that was too complex and still relied on engineers to self-triage questions, providing context but not reducing the interruption load.