Build kit / Client experience

Client service desk

Collect service requests, assign them to the team, and use an agent to answer questions from approved sources.

Your app idea

Describe the
app you want.

Tell your agent what you want the app to do. You can work through the details together. This page does not save your changes.

The business or clientWhat the app should doSoftware you use & tools you build with

Use a summary of the business. Keep credentials and sensitive client records out of prompts.

The maintained Swirls agent instructions

Help me design and build: Client service desk.

Intended outcome: A service application with request intake, triage, assignment, and an agent that can consult approved knowledge.
Business / client: [Describe the business or client]
Process and requirements: [Describe the process, people, rules, and exceptions]
Existing software and preferred frontend: [List existing software and preferred coding tools]

Use Swirls as the backend for workflows, agents, durable data, and integrations. Keep the frontend aligned with my chosen tools. Use the Swirls SDK for supported typed interfaces. Enforce business rules and authorization in the backend; do not rely on UI-only checks.

First read the maintained Swirls language skill at https://swirls.ai/.well-known/agent-skills/swirls-lang/SKILL.md and its referenced rules. Follow its complete-system design workflow before writing DSL. If you cannot access those instructions, stop and explain what is missing. Do not invent Swirls syntax, SDK methods, or platform capabilities.

Clarify these questions:
- Which requests should the team handle?
- What information may the agent access?
- When must a person take over?

Describe the complete system: interface, roles, access boundaries, data, workflows, agents, integrations, failure handling, and production responsibilities. Identify assumptions and missing capabilities. Present the plan for review before implementation. Treat the client details above as requirements to clarify, not permission to access external systems.

After approval, build in small verifiable steps. Validate .swirls files using the documented tooling. Keep credentials out of prompts and browser code. Assess hosting and networking against the actual runtime; do not assume private connectivity is already configured. Obtain explicit authorization before deploying or changing production resources.

Acceptance checks:
- Requests and knowledge respect client access boundaries.
- The agent escalates when it cannot safely resolve a request.
- The team can trace the actions taken on a request.

Report what works, what was tested, and what still requires configuration or review.

Things to test

Check the
app works.

Requests and knowledge respect client access boundaries.
The agent escalates when it cannot safely resolve a request.
The team can trace the actions taken on a request.

Client service desk

Describe theapp you want.

Check theapp works.

Describe the
app you want.

Check the
app works.