Skip to main content
For errors or missing data, start with Troubleshooting.

Getting started

Connect and verify one property and recent reservation, then test one message channel. Prepare the agent in review mode and invite the teammate who will handle the work. Follow Quickstart before expanding.
Confirm an imported stay, an incoming message and reply, and a task completed from the assigned worker’s account. Follow Quickstart.
Choose the channel your team already uses for the conversations you want to handle. Follow Email, WhatsApp, or Phone and SMS. Use Slack for internal alerts.

AI Agent and knowledge

Put property facts on the property, handling rules in Policies, reference material in Documents, and operational procedures in Skills. Keep the agent’s role and tone in its instructions. See AI Hub.
Review suggested replies first. Test a property question, policy, procedure, and human handoff, then check sources and the notification destination before enabling the intended scope. Follow Launch your AI Agent.
Inspect the source or trace, give a precise correction through Teach AI or edit the source directly, and verify the saved change. Repeat the same question and a related case. See Fix wrong AI information.
No. Behavior depends on tool permissions, autonomy, and the configured workflow action. Use Ask first or an Approval block where a person must decide. See Agent permissions and Message approvals.

Tasks, teams, and workflows

Check the property and checklist, assign and schedule the task, complete it from the worker’s view, and review its photos and notes. Follow First cleaning operation.
A task is one job. A visit groups tasks at one property for the same day and assignees. A shift is the person’s working period. See Tasks and visits.
Open the vendor setup in Settings > Team & Permissions, check the contact and permitted work, and review the invitation status before resending. See Set up a vendor.
Use controlled inputs and inspect each run’s matching, skipped, approval, rejection, and expiry paths as relevant. Check the resulting record or delivery separately from a simulated test. See Workflow testing.
Choose the role’s actions, departments, and property scope, then inspect individual overrides. Test from the invited person’s account. Follow Roles and property access.

Connections and troubleshooting

Compare a recent record and a known change in Trellis and the source system. Check the connection, property mapping, sync range, and provider-specific refresh process. See Integrations.
Check the workspace, filters, record, and connection before retrying. If an external action has an uncertain outcome, inspect the original attempt first. Use Troubleshooting for the relevant checks.
Send the affected record or integration, time and time zone, expected result, visible error, and checks already completed. Hide unnecessary private data in screenshots. Contact [email protected].