Overview

When a guest mentions a broken faucet or a dirty bathroom, the right next step usually isn't a Sparrow Intel reply — it's a work order in your operations platform. Conversations connects directly to Breezeway, Guesty, Hostaway, Track, Asana, and webhooks, so an issue surfaced in a message can become an assignable task in seconds.

This lesson covers the two paths to task creation and points you to the deeper reference for each integration's specifics.

Two paths to task creation

Manual: from a conversation

When you're reading a conversation and want to spin up a task:

1. Click Create Task on the conversation (or the equivalent action in your UI)

2. Pick the destination integration (Breezeway, Guesty, Hostaway, Track, Asana, or webhook)

3. Pick the department (Cleaning / Maintenance / Inspection)

4. Fill in title, description, optionally assignee, scheduled date, template, tags

5. Submit

The task is created in the integration of your choice, with a link back to the originating Sparrow Intel conversation. The conversation gets a record that a task was created from it.

Automatic: via a rule

Far more leverage. A rule like:

When a new conversation post arrives AND has maintenance issues, create task in Breezeway

…will automatically generate Breezeway work orders every time Chirp AI detects a maintenance issue in a guest message. No agent needs to click anything.

This is one of the highest-ROI rules you can set up. See Rules for Conversations for how to build it.

Issue-based task creation (the important part)

Here's what makes Conversations + Tasks special: when a rule fires on a "Has Maintenance Issues" or "Has Cleaning Issues" condition, Sparrow Intel doesn't create one generic task. It creates one task per detected issue, each with the correct department, a focused title, and a checklist item.

So if a guest says:

"The dishwasher won't drain, the porch light is out, and the upstairs bathroom faucet is dripping."

…and a rule is configured to create maintenance tasks, you get three Breezeway tasks — one for each issue — assigned to the right department, with the issue text as a checklist item, and titled clearly so a maintenance tech sees exactly what to do.

This per-issue enumeration applies to:

• Cleaning issues → tasks routed to your Cleaning department

• Maintenance issues → tasks routed to your Maintenance department

• Both can fire on the same rule — you'll get separate cleaning and maintenance tasks

Read the Task Creation Guide for the full mechanics, including the title formats, checklist behavior, and per-integration field mapping.

Picking a destination integration

Each integration has its own strengths:

If you don't have any of these connected, the in-product Integrations tab is where you start. Each integration has its own setup guide.

What gets sent and what doesn't

Field-level coverage varies by integration. The summary table:

The full per-integration breakdown is in the Task Creation Guide.

Avoiding duplicate tasks

A few patterns that prevent task spam:

• Don't run two rules that both create a task on the same condition. Pick one source of truth.

• Be careful with broad conditions. A rule that fires on "any negative sentiment" could create dozens of tasks per day on a noisy property — narrow with a category or property filter.

• Use status changes thoughtfully. A rule that creates a task on every inbound post (without filtering) will create tasks even after the issue is acknowledged. Add a "post sender = guest" condition or similar.

When in doubt, use the test pattern from Rules for Conversations: build the rule with a label-only action first, watch what it would have done for a day, then switch on the real action.

Up next

You're done with Power Maneuvers. The last lesson is for admins — Admin Setup Checklist & Tuning for High-Volume Operations — and walks through the full configuration that makes everything you've learned work for a team at scale.

Related

• Task Creation in Sparrow Intel (full reference)

• Asana Integration

• Rules & Automations collection