Customer and Factless Fact Table(s)

Have just started looking at the design of the Customer dimension and some "related" dimensions.
As Customers can have > 1 address, am planning to have separate Customer and Address dimension tables - and then a Factless fact table for dimensional reporting.

but
in the source database, there are several other relationships from the Customer table in addition to the CustomerAddress - e.g. CustomerName, CustomerPhone etc... (there are over 10 in total)
should i be creating a separate Factless fact table for each / every one of these combinations - or is there some other possible solution ??

Customer Name table?? I would just put "domain" type entities into the customer dimension table. The same for phone as well. I have also been known to snowflake the addresses off of customer dim as well.