What about containing customer contacts?
I still that one Customer_Contact table that contains something like Customer_ID, Contact_Type, Contact_Code columns (Entity-Attribute-Value ???) is better than seperate Customer_Phone, Customer_Fax, Customer_Email, Customer_Tweet, ad nauseam tables.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho