Use cases
Use cases
Worked examples that show how Flexday AI's components come together to solve a real business problem, end to end.
- Everyone
Last reviewed
The component pages explain each part of Flexday AI on its own. The use cases show them working together: a business problem, the Solution that solves it, how data moves, how people sign in, and how the team builds and runs it. Each one uses a fictional company, so the names and addresses are illustrations, but every capability shown is real.
Service Desk Copilot
A medium-complexity Solution for an IT service desk. Employees get IT help in Microsoft Teams from an assistant that answers from the company's own knowledge, raises tickets in ServiceNow and reports their status. ServiceNow pushes every incident change into a live dataset that powers a dashboard for IT staff, who sign in with the company's SAML provider through Amazon Cognito. A priority 1 incident alerts on-call engineers in Teams, updates the status page and emails managers.
| Business problem | Slow first response, tickets raised with missing details, managers without a live view |
| Components used | Bot, Agent, Doc Base, Fact Base, LaunchPad, Flows, Integration (ServiceNow), two Flex Gateways, two Identities, a Connection, Variables |
| Data from outside | ServiceNow pushes incident changes; a nightly Flow pulls open incidents |
| Sign-in | Teams (Microsoft's signature), SAML through a Cognito user pool, and an API key for ServiceNow |
Start with the Service Desk Copilot overview, then read:
| Page | What it covers |
|---|---|
| Solution design | Every resource in the Solution and how it is configured |
| Data flows | The four flows of data, step by step, with diagrams |
| Authentication | How each kind of caller proves who they are, including SAML through Cognito |
| Teams experience | What employees see, and the rules the Bot follows |
| Build and operate | Building it with the Builder, going live, and running it day to day |