Listing Quality Rules

i.e. trigger an action for a listing quality status change

Problem / context

The rule triggers on a listing quality status change and creates a task. But a task that only says a listing has entered pending removal isn't actionable on its own. The recipient still has to go find out what Airbnb flagged, what the appeal requires, and when it's due, which means leaving the task and logging into the Airbnb account. That defeats the point of routing the task to them.

This matters most for pending removal, where the appeal is the work. Operators build appeals by taking each cited issue, explaining why it happened, and documenting the resolution. The person doing that needs the citations in front of them.

Requested capability

When a listing quality status change generates a task, write the appeal detail into the task body so the recipient can act without leaving it.

Detail / spec

Include, where available from the platform:

• Appeal due date

• Reservation issues cited

• Specific reasons flagged (e.g., check-in, communication, host-encouraged cancellation)

• Current listing quality status and the date it changed

The data is already surfaced on the Listing Quality page, so this is a matter of carrying it into the task payload rather than sourcing anything new.

Detail should scale to severity. A suspension notice is largely informational, while pending removal needs the full appeal context.

Acceptance criteria

• A task generated from a pending removal status change includes the appeal due date, cited reservation issues, and flagged reasons.

• A recipient with no Sparrow access can understand what needs to be addressed from the task alone.

• Fields absent from the platform response are omitted cleanly rather than rendering blank or erroring.