Use Cases
Every one of these is work a company is already doing — usually by hand, usually by someone who should be doing something else. Each page below is a complete build: the problem, the architecture, the configuration that matters, what happens at run time, and what you get back.
Pick the one closest to your own annoying Tuesday and follow it end to end. The first eight are built inside Studio with Flows; the last four put a Studio peer inside your own product with the Client SDK.
The catalogue
| Use case | What it stops | Built from |
|---|---|---|
| Support ticket triage | Outages buried under password resets; SLA misses nobody noticed until the customer did | Task trigger, Smart Agent, Condition, Approval, Track Event |
| Invoice and expense processing | A finance analyst reconciling a spreadsheet for two days a month | Task trigger, Node.js, Each loop, Track Event, Publish File |
| Contract review and renewal tracking | Auto-renewals nobody caught, contract terms nobody can find | Sandbox, Smart Agent, Flow Memory, scheduled digest |
| Security questionnaires and RFPs | A week of an engineer's life per deal, answering the same 300 questions | Data sources, Smart Agent, Skills, Each loop |
| Employee onboarding assistant | The same forty questions in Slack, every single month | Peer, data sources, Slack/Teams channels, Evaluation |
| The weekly executive report | Three people copy-pasting from four systems every Monday | Schedule trigger, HTTP steps, Smart Agent, PDF output |
| Lead qualification and CRM hygiene | Sales working stale leads while good ones go cold | Peer with tools, agent approval, enrichment flow |
| Customer feedback analysis | 4,000 survey comments nobody has read | Classifier, Each loop, Track Event, Reports |
| HR self-service widget | Employees filing HR tickets for answers that already live in the policy | Peer, Client SDK, hookId, client tools |
| Expense upload and approval widget | Receipts emailed around and retyped into the finance system | Peer, Client SDK, client tools |
| Mobile peer embedded in the app | A chatbot that can talk about the app but cannot open a screen in it | Peer, Client SDK, native client tools |
| Website product advisor widget | Visitors leaving the pricing page with a question nobody answered | Peer, Client SDK, client tools |
Customer-facing
Support ticket triage that escalates safely
Tickets arrive faster than anyone can read them. The genuine outage sits behind eleven password resets, and nobody wants an AI deciding on its own to tell a customer their data is gone.
This build classifies every ticket, routes it, and stops at a human before anything consequential leaves the building — then records what it decided so you can prove the SLA later.
Customer feedback that someone finally reads
Four thousand free-text survey answers, one product manager, zero chance. This build turns them into a categorised, quantified picture — with the actual quotes attached, so the number and the evidence arrive together.
Back office
Invoice and expense processing
The monthly export lands, and a finance analyst spends two days turning it into a reconciled spreadsheet. This build does the pass in one run, records one event per line item, and hands back a CSV — plus a spend breakdown by customer that nobody had to build.
Contract review and renewal tracking
Contracts live in a folder nobody opens until something auto-renews. This build reads them in a sandbox, extracts the terms that matter, remembers them, and tells you sixty days before a renewal instead of sixty days after.
Knowledge and internal
The onboarding assistant that knows your policies
Every new joiner asks the same forty questions, and every answer costs a senior person twenty minutes. This build answers them from your own documents, in Slack or Teams, citing the source — and says "I don't know" rather than inventing a policy.
Security questionnaires and RFPs
Every enterprise deal ships with 300 questions you have answered before, in slightly different words. This build drafts the answers from your existing documentation and flags the ones a human must actually decide.
Revenue and reporting
Lead qualification and CRM hygiene
Sales works whoever is at the top of the list, which is rarely whoever is most likely to buy. This build enriches and scores inbound leads, writes back to the CRM — and asks before it writes anything.
The weekly executive report
Monday morning, three people pull numbers from four systems and paste them into a deck. This build assembles the whole thing on a schedule and fails loudly when a source is down, instead of quietly producing a report with a hole in it.
Embedded in your product
These four are not Flows. Each one puts a Studio peer inside an application you already own, using the Client SDK and a hookId, and lets the peer trigger real actions in your UI through client tools. Every page links runnable code on GitHub.
HR self-service widget
Policy questions and leave requests land in the HR queue even though the answers are written down. This build embeds a peer in the employee portal, reuses the identity your portal already has, and lets the peer open the leave form instead of describing where it is.
Expense upload and approval widget
Receipts arrive as photos in chat and get retyped by hand. This build lets the peer ask the follow-up questions, open the native picker, and create the expense draft in your finance system through client tools.
Mobile peer embedded in the app
A field app needs more than chat. This build runs a peer inside the mobile shell so it can open a customer screen or start the camera, and carries one conversation across those native actions.
Website product advisor widget
A public site gets traffic but no conversation. This build embeds a peer that qualifies visitors, answers pricing questions, and opens the demo form or scrolls to a plan, without a separate bot backend.
How to read these
The eight Flow scenarios follow the same shape (the four embedded-widget pages above are shorter and code-first):
- The problem — what it costs today, in hours and in misses.
- What you build — the architecture in one diagram.
- Implementation — step by step, with the configuration that actually decides whether it works.
- What happens at run time — the walkthrough, including the parts that pause.
- What you get — outputs, files and reporting.
- Extensions and pitfalls — where teams take it next, and where they get burned.
If you are new to Flows, read Projects & Flows first — every scenario assumes you know what a project, a trigger and a final step are.