📋 Reference
<aside>
💬
WHAT IT DOES
Copy-and-adapt prompts for the Designing Your Agent. Describe an agent in plain language, then keep chatting to connect your knowledge, systems, and channels. Every example is a starting point — swap in your own details.
</aside>
How to use these
- Say things in plain language — there's no special syntax to learn.
- Start with one clear job, then add capabilities one at a time.
- When a step needs a secret — an API key, a database login — the designer asks for it in a secure form. Never type credentials into the chat.
- Building and live-testing a change usually takes a couple of minutes (or seconds on Low effort — see Agent Effort).
Start an agent
Your first message describes the whole agent — say who it helps, what it does, and its tone.
- "Build a 311 assistant for the City of Riverton that answers questions about city services — trash pickup, park hours, permits — and lets residents report issues like potholes and downed trees. Friendly, plain-language, and never give legal advice."
- "Create a Permits & Licensing helper that explains how to apply for common permits and what each one costs."
- "Start a Parks & Recreation agent that shares park hours, closures, and how to book a pavilion."
Prefer to build piece by piece? Choose Start blank and add everything by chatting.
A starter prompt in the Agent Designer — your first message describes the whole agent: who it helps, what it does, and its tone.
Give it knowledge
Ground answers in your own content so the agent stops guessing.
- Add a quick fact — "Add this: bulk trash pickup is the 2nd Tuesday of each month."
- Add an exact answer — "Add a Q&A: 'How do I report a pothole?' → 'Tell me the location, or use the report form, and I'll log it.'"
- Connect a knowledge base — "Connect our Riverton Municipal Code knowledge base so it can answer code questions." Build the library first in Knowledge Bases; the designer links it.
Connect your systems & data