My 2 Cents worth.
If in doubt, create your tables to reflect the entity that it models and use the proper identity, primary and foreign keys to keep the data in line.
As already stated, it sounds like your table is likely to contain lots of Phone1, Phone2, ... Phone(n) type fields.
These should be in a table of contact details
ContactMethodID (PK),CustomerID(FK to customer), ContactTypeID (FK to contactTypes),ContactDetails
This would mean you could have 0, 1 or 100million contactMethod records for each customer. You have very little wasted space in the database and queries are simpler because you are extracting data against one table/column instead of against several.
select CustomerID, ContactDetails from ContactMethods where ContactTypeID = 'Phone' and ContactDetails begins ('+44')
select CustomerID, Phone1 as 'Phone' where Phone1 begins ('+44')
select CustomerID, Phone2 as 'Phone' where Phone2 begins ('+44')
select CustomerID, Phone3 as 'Phone' where Phone3 begins ('+44')
select CustomerID, Phone_n as 'Phone' where Phone_n begins ('+44')
The way the data is diaplyed on the screen for the user to fill in, and the validation done on that data may bear no reflection on the representation of that data in the database