The solution is able to accept generic emails as visitors, but most of users won't allow badges for example, or formal check-in with generic names.
One suggestion would be:
- detect generic emails (could be hard), and if possible raise a warning to the owner
- allow the modification by check-in team or organizer, to edit/modify/suppress a visitor in an invitation before printing badges
- prevent printing of badges with generic emails
- allow organizer himself to edit the form (plugin/Web) during the invitation registration, to complete the visitor information, by adding at least Lastname/firstname/society/email fields so that at least a formal name is associated to a generic email