Agent Setup & Scheduling
1. What is an “Agent” in AI Studio?An Agent is the AI (or AI-assisted) profile that represents your business in conversations. The agent profile stores business details, intro scripts, and availability so the system behaves correctly across channels. 2. What information should I add to an agent profile?
Recommended fields to keep accurate:
- Business name
- Email + phone
- Website URL
- Business type/category
- Address
- Company description
- Introduction script (used as a greeting)
Availability helps the system behave correctly around working hours and scheduling. It reduces missed handoffs and keeps routing and responses aligned with real hours. 4. Can I set different hours per day?
Yes. You can toggle availability per day and set start/end times individually. 5. What does “Apply on following days” do?
It copies the same schedule to multiple days so you don’t manually enter the same hours repeatedly.
Knowledge Base
6. What is the Knowledge Base used for?The Knowledge Base powers accurate AI and agent responses. You can store internal docs, FAQs, policies, pricing, and anything your AI should reference when responding to customers. 7. How can I add content to the Knowledge Base?
You have four main options:
- Create files manually
- Upload existing files
- Create folders for organization
- Scrape your website (fastest)
Sync updates the knowledge base so:
- agents use the latest content
- AI responses reflect new/updated data
- scraped content becomes usable
Website Scraping
9. How does website scraping work in Z360?When you click Scrape Website, you:
- enter your website URL
- Z360 crawls your site and extracts content
- content is organized into structured files/folders automatically
Scrape your website when:
- your main truth source is your public site
- you want a fast knowledge base without manual copy/paste
- your content changes frequently (you can re-scrape and sync)
Actions & Integrations
11. What are Actions in Z360?Actions let you automate workflows by calling external services or APIs. They can be triggered inside abilities and used to push/pull data. 12. What can I configure inside an Action?
An action typically includes:
- Name + description
- API endpoint URL
- Arguments (inputs)
- Headers (Authorization, Content-Type, etc.)
Integrated actions are actions made available once a third-party integration is connected. After connecting a tool, you can trigger actions for that tool directly inside workflows. 14. What third-party apps can be integrated?
Z360 supports 40+ integrations, including:
- Google services (Gmail, Calendar, Drive)
- QuickBooks
- ClickUp
- Trello
- Slack
- Salesforce
- Zendesk
- HubSpot
- Stripe
- Zapier (for thousands more)
- Sync data between systems automatically
- Trigger actions in other apps without leaving Z360
- Keep work centralized (tickets, tasks, scheduling, CRM updates)
Abilities (Create, Edit, Triggers, Registration)
16. What is an Ability in Z360?An ability is an automated workflow that runs when certain triggers are met. It can ask questions, route users, and execute actions like creating tickets or sending responses. 17. What are triggers and how do they work?
Triggers decide when an ability starts. Triggers are evaluated when someone interacts with AI through:
- Phone
- Live chat
- Only interact with registered users
- OR help users register first (by collecting their information)
- Work for anyone (registered or not)
- Best for public-facing tasks like FAQs, basic inquiries, info requests
Yes. Multiple triggers let the same ability run from different channels or different phrasing patterns.
Building Abilities (Ask, Speak, Act, Condition)
20. What do Ask / Speak / Act nodes do?- Ask: collects info and stores it in variables
- Speak: replies back to the user naturally
- Act: performs tasks (ex: create ticket)
- Condition: branches the workflow based on variable values
Condition nodes let you build different flows depending on user answers. Example:
- If appointment type is “follow up” → ask previous provider
- If appointment type is “new appointment” → ask reason for visit
Ask nodes store user responses into variables (e.g.,
{appointment_type}), which can be reused later in:
- Conditions
- Speak messages
- Ticket creation fields
- Actions
