Home / Blog / Can you auto-reply to rental inquiries without a Fair Housing problem? A checklist

Can you auto-reply to rental inquiries without a Fair Housing problem? A checklist

Questions and answers on automating replies to rental inquiries: what the Fair Housing Act says about statements, why every prospect should get the same reply, how to handle accommodation questions, and what our mock test checked.

By (@MattRonnX on X) · Published · 4 min read

You list a unit and the inquiries come in all evening. Some ask about pets, some about parking, a few tell you their life story. Answering fast is good business. Answering differently depending on who's asking is how small landlords get into Fair Housing trouble without meaning to. This Q&A walks through how our rental inquiry auto-reply recipe is built, and ends with a checklist you can use with or without it. The other four recipes are on the property management hub.

We're not lawyers, and this isn't legal advice. The official sources are linked throughout; read them, and ask a local attorney about your state and city.

What does the law actually say about what I write?

The Fair Housing Act makes it unlawful "to make, print, or publish, or cause to be made, printed, or published any notice, statement, or advertisement, with respect to the sale or rental of a dwelling that indicates any preference, limitation, or discrimination" based on a protected class (42 U.S.C. 3604(c), Cornell LII). An email reply to a prospect is a statement about a rental.

HUD lists the seven protected classes under the Act as race, color, national origin, religion, sex, familial status and disability (HUD Fair Housing Act overview). Many states and cities protect additional classes; check yours.

Why does an identical reply matter so much?

Because the risky part of answering by hand is the variation. One prospect mentions kids, and the reply quietly suggests a different building. Another sounds like a good fit, and gets the showing link first. An automated reply can remove that variation, but only if it's built to.

Our recipe uses a fixed template filled from your listings sheet: rent, deposit, availability, pet policy, a link to your written rental criteria (the same for every applicant), a showing link and an application link. Only the first name changes. The prospect's own message is never used to choose or change the answer; it goes to your office as-is.

In test scenario PM5-04, two invented prospects wrote very different messages (one mentioned kids, one mentioned retirement and church). They got word-for-word the same reply except the first name, and neither message appeared in it.

Does the bot screen anyone?

No, on purpose. There's no scoring, ranking or "qualified lead" flag. Screening belongs in your application process, under written criteria applied the same way to everyone. The reply links to those criteria so every prospect sees them before applying.

What about my listing text?

The recipe checks each listing description against a list of red-flag phrases before anything is sent: "adults only", "no kids", "perfect for a young couple", "English only", "able-bodied" and similar. In PM5-06, a listing with "perfect for a young..." and "no kids" stopped the reply entirely; the manager was told which words and pointed to HUD. The list catches common phrases. It is a safety net, not a review by someone who knows the law.

Someone asks about a support animal or wheelchair access. Now what?

A person answers. Refusing reasonable accommodations needed for a person with a disability to use a dwelling is unlawful (42 U.S.C. 3604(f)(3)(B); 24 CFR 100.204). In PM5-07, an inquiry mentioning an emotional support animal still got the standard reply, unchanged, and the manager was flagged to answer personally. A bot shouldn't decide those questions, and it shouldn't send a "no pets" line to someone asking about an assistance animal. HUD's disability rights page links its current guidance.

What if the unit is already leased?

Every prospect gets the same answer: it's gone, followed by every available listing in a fixed order, each with criteria, showing and apply links (PM5-05). The order doesn't depend on who asked.

Can I text prospects?

Only if they ticked a consent box on your form, and only between 8 a.m. and 9 p.m. their time; an 11:10 p.m. inquiry got its email right away and the text at 8 a.m. (PM5-10). STOP ends texts across all recipes. The federal rule is 47 CFR 64.1200; our texting consent page explains how we design around it.

The checklist

Use it whether you automate or not:

  • One reply template, filled from listing data. Only the name changes.
  • The prospect's message never changes what they're told.
  • A link to written rental criteria, the same for every applicant.
  • Every available unit listed in a fixed order when the requested one is gone.
  • Listing text checked for preference words before it goes anywhere.
  • Accommodation questions go to a person, promptly.
  • No screening, scoring or ranking in the auto-reply.
  • "Equal Housing Opportunity" in the footer.
  • Texts only with consent, 8 a.m. to 9 p.m., STOP honored.
  • Your state and city protected classes checked, not just the federal seven.

What we tested

The recipe ran end to end in n8n against local mocks of Twilio, the email API and Google Sheets: 11 of 11 scenarios passed on October 31, 2026, with invented prospects and listings only. Details on how we test.

The recipe for this problem

  • Rental inquiry auto-reply: the same facts to every prospect, in the order they asked
    A web form (or a listing's link to it) takes name, email, optional phone and text consent, the listing and a message. Every prospect gets one email with the same facts from your listings sheet: rent, deposit, pet policy, availability, and links to your written rental criteria, showing times and the application. The reply template is identical for everyone except the first name; what the prospect wrote never changes it. Leased or unknown listings get every available listing in a fixed order. If your listing text reads as a preference ('no kids', 'perfect for a young couple'), nothing goes out and the manager is told which words to fix, with HUD's page. Questions about accommodations or assistance animals still get the standard reply, and the manager is flagged to answer personally.
    Verified with mocks · last tested 2026-10-31 · setup, cost and test results

Found an error or a better source? Corrections policy. More articles on the blog.