Professional Tenant Communications at Scale

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In AppFolio, use its reporting/export tools or available AppFolio data access to identify tenants affected by each maintenance update, lease renewal, or policy change, including property, unit, lease dates, tenant names, and email addresses. 3. Draft messages from the approved tenant communication templates for maintenance notices, renewal reminders, and policy updates; personalize only factual fields such as tenant name, property, unit, dates, issue description, and next action, and avoid language that treats protected classes differently. 4. Compose the emails in MultiMail, grouping recipients by the exact notice they should receive and scheduling time-sensitive notices with enough lead time for review. 5. Run every message in gated_send mode so I can approve compliance and tone before delivery; ask me only for AppFolio access, the approved templates, brand voice, and permission to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Yardi, use standard resident, lease, work order, and property reports, or the available Yardi integration access already enabled for my account, to detect tenants affected by open maintenance events, upcoming lease expirations, and building-wide policy changes. 3. For each event, draft a tenant-ready email from the matching approved template, personalizing only verified facts such as resident name, property, unit, lease expiration date, maintenance window, policy effective date, and contact instructions. 4. Compose or schedule the messages through MultiMail, keeping renewal, maintenance, and policy communications in separate review batches with clear subject lines and consistent wording. 5. Use gated_send oversight for all outbound tenant communications; ask me only for Yardi access, approved templates, brand requirements, and final approval to activate sending.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Buildium, use resident, lease, task, and maintenance request data through its API or built-in exports to detect new maintenance updates, leases approaching renewal, and policy announcements that need tenant communication. 3. Draft each email from my approved fair-housing-safe templates, inserting only concrete details from Buildium such as tenant name, property, unit, maintenance status, appointment window, renewal deadline, rent terms, or policy effective date. 4. Prepare the emails in MultiMail and schedule non-urgent notices in practical batches, while leaving urgent maintenance updates ready for immediate review. 5. Run the workflow in gated_send mode so no tenant email is sent until I review it; ask me only for Buildium access, the approved templates, sender identity, and brand tone needed to go live.