This is the thing to understand before anything else. A Task Template is a reusable checklist. It does not create work, schedule anything, or assign anyone. Three pieces have to be in place, in order:

Build the template and stop, and nothing happens. Build the template and the automation but skip assignments, and tasks appear unassigned. Almost every "my tasks are not being created" question is a missing link in that chain.

All three live under Operations, then the Configuration tab. They are not top-level tabs.

Configuration opens on Departments: "Organize work into departments and subdepartments. Built-in departments cannot be changed."

Four are built in and badged as such: Cleaning, Maintenance, Inspection and Guest Services. You can add subdepartments to any of them, and create your own departments with their own icon and colour. Every template belongs to a department, which is what drives the summary donuts on the Tasks page and much of the filtering.

+ Create Template adds one. The list shows each template with its department, its subdepartment, and a count of its requirements.

Requirements are the individual checklist items the person completes in the field. Supplies attached to a template are deducted from inventory as they are used, so a template is also how consumables get tracked.

Templates can be duplicated, which is usually faster than building a near-identical second one from scratch.

+ Create Automation adds a rule. Each automation shows its name with a plain-English schedule line beneath it, such as "on all check-outs", plus its trigger type, how many templates it uses, and whether it is active.

That subtitle is the fastest way to audit what actually fires. You can read down the list and understand your whole automation set without opening a single one, which is worth doing periodically.

"Configure assignment defaults across multiple listings at once." Each config is a card, and the useful way to read one is as a single sentence: for this listing scope, tasks in this category go to these people.

The three columns are Listing Scope, set to all listings, listing sets or specific listings; Category, toggling between a whole department or one specific template; and Assignment, holding the assignee chips with an Edit control. Assignees can be individuals or a company.

Skip this page and your tasks are created unassigned, which means somebody has to dispatch every one by hand from the Schedule.

"Control when Besty considers a listing ready." The default, All Tasks, means that if any task due before the next check-in is incomplete, the listing is not ready. Custom lets you define which task types actually count.

This setting does not stay inside Operations. Ready status feeds the Listing Ready condition available on journey messages, and it gates same-day early check-in offers, because Besty can be told not to sell an early arrival into a property that is not clean yet.

So an ops team keeping task status current is directly protecting upsell revenue and guest experience, not just tidying a list.

Under Operations, then Listings, opening a property and choosing Settings, then Data, gives you a notes area described as "Enter any information you want your team to have while they access this property".

Notes stack by scope, and each is labelled with where it came from: account-wide notes applying to every listing, listing set notes, and notes for that one property. All three surface together during task completion, so a cleaner sees the general rule and the property-specific exception side by side.

Template variables work here, so access codes and wifi details can be pulled in rather than copied and left to go stale.

Reach out via chat or at support@getbesty.ai.