Agreed. Other than a complicated N8N or Zapier flow with lots of if thens and multiple automated messages back and forth the workflow doesn't lend itself to email. Interesting potential use case for a theoretical FF workflow bot tho. 🙂
Please login or Register to submit your answer
<p><p>I would create a form. That’s where you add all the info for the building, landlord, property id etc. Add in a repeater for the units info. Inside the repeater put the type of unit and the availability radio button. Then email the landlord a link to edit that individual entry.</p></p>
Could create their accounts and onboard them. Either scheduled with live support or automate it with walkthroughs, Maybe create tiered roles: housing manager, landlord, RA (resident assistant) Maintenance, Applicant, Resident, etc. Limit who can see and do what.
To do something new, give them a management portal that handles the status, availability, dynamic pricing for them. Do a user journey of what they need, map it out, build it, and test with a few landlords, one at a time. I've built and iterated FF-based student housing solutions and the time it takes is so worth it. I've solved a *ton* of stuff - especially around units, availability, different rent payment types, and housing change requests. One person easily manages up to 256 beds from application to roommate matching. Dynamic PDF applications, contracts, etc.
Definitely worth the time and effort. I've had success with overworked, minimally-technical housing admins and students who rarely read before clicking and I've taken my lumps. So good when you can dial it in.
Tip: The Formidable Pro Elite version and its API can be one of your very best friends, LOL.