Get Started with Siesta AI
The Product Introduction explains how Siesta AI fits together. After signing in, choose the work surface you need: Chat, Agents, Tasks, Data, Workflows, Library, Tool Executions, Conversations, Recordings, or Memory. Start with the surface that already matches the job instead of trying to configure everything first.
First rule If you only need one answer, use Chat. If the work should follow a defined role or use approved tools, choose an Agent. If someone needs to review or continue the work, create a Task.
First Checks
- Confirm you are in the right organization or team.
- Open Profile if your personal details, locale, or account context look wrong.
- Open Connections if the agent needs Gmail, Calendar, Drive, Slack, Jira, HubSpot, Microsoft, or another external service.
- Check whether the work should use an existing Agent before creating a new thread from scratch.
The 10 Minute Setup Path
Start a clean chat
Ask a simple request and confirm the agent understands your role, source material, and desired output format.
Try one attached file
Attach a PDF, spreadsheet, image, or note and ask the agent to summarize, extract action items, or compare it with your instructions.
Use the right agent
Open Agents when you need a prepared role with its own prompts, data, tools, analytics, conversations, feedback, and history.
Track follow-up
Create a Task when the result needs ownership, review, or a status change before it is finished.
What You Do Not Need On Day One
You do not need to understand model connections, token limits, retrieval tuning, workflow internals, or every approval rule before using Siesta AI. Use the default agent setup, make the request clear, and inspect the result before anything is sent or changed externally.
Continue with Ask in Chat Effectively for a first request or Choose and Use Agents when the work needs a prepared role and approved capabilities.
When To Ask An Admin
Ask an admin when a needed agent is missing, a shared connection expired, a tool is unavailable, a workflow is blocked by permissions, or a data collection is not visible to the right team. Admins can follow Configure Shared and Private Connections or Govern Data Collections and Sources to resolve those shared setup issues.