Email rules that are setup within the client or service restrict filtering to contact, folder, content (in some cases). We can react to data that's outside of your inbox, anything from your relationship to the contact based on another web service, to accessing, storing, and sharing with services you use regularly. Beyond this triggers such as time, email load (driven from analytics), location can all come into play. We are really just getting started with the possibilities, a way to interact with custom web apps would be great for developers/companies that use bespoke tools.
The ease of this tool is inversely related to the need for it. i.e. — the more complex/high volume your inbox, the more you suffer while trying to set it up.
Maybe it would be worth implementing some "starter rules" or a "wizard" that allows the first-timer to leverage many basic rules at once, immediately.
It's the Pinterest approach, if you will. :) "Pick 5 things you like" and then they auto-follow 50 people based on your choices. Voilá! Good first experience.
Remember that features ≠ power ≠ satisfaction.
I apologize for the unsolicited suggestions; you hit my area of interest right in the middle. ;) Good luck with everything and congrats on getting to the alpha in the first place!
If you have 100 common contacts (as opposed to the other 900 who email once and a while) and I need, say, a rule or two for each to cover the basics... and a rule or two to cover groups of people (because one-to-one emails are the exception in business not the rule)... isn't that hundreds and hundreds of rules?
Not having seen the alpha, that feels like an insurmountable first threshold, UX-wise.
Also, just out of curiosity, other than general ease-of-use (which seems much nicer in your 3 examples), how is this better than typical filters (which I don't use)?