Vacasa.com email ingest + reply

Operators with listings distributed through Vacasa.com receive guest correspondence as email rather than through a native OTA messaging API. Today that email either doesn't land in Sparrow Intel's Conversations inbox or lands without a reliable reply path, so agents have to leave Sparrow to read and respond — breaking the unified-inbox workflow and the AI-assisted reply tooling (Chirp). For example, an agent handling a Vacasa.com guest inquiry must work outside Sparrow to read and answer it, losing threading, reservation context, and Chirp draft assistance.

Requested Enhancement:

• Ingest inbound Vacasa.com guest email into the Conversations inbox, threaded correctly so multiple emails for one reservation group into a single conversation.

• Associate each conversation with the correct guest and reservation/property where data permits (confirmation code, guest name, listing), and label the source clearly as Vacasa.

• Allow agents to reply from within the conversation, delivered back to the guest via the correct email path, with confirmed deliverability (avoiding the "failed to send via Mailgun" class of failures).

• Respect existing email-conversation rules — manual draft, not auto-send — and support Chirp AI draft-on-demand once the thread is captured.

• Build on the in-flight email-conversations capability (attachments, forward, body rendering, guest-name-in-from-line) rather than a parallel path.

Benefit: Treating Vacasa.com email as a first-class conversation source would keep agents in a single unified inbox, preserve threading and reservation context, extend Chirp AI assistance to Vacasa threads, and ensure reliable two-way communication with guests — without forcing agents out of Sparrow.