T-Mobile Startup Verification Demands Documents That Do Not Match Business Reality
A software firm was blocked from getting business data plans after the carrier requested utility bills and bank history that did not fit the company's specific circumstances.
By Andrew Hayes ·

A small software startup applied for business data plans from T-Mobile so its staff could stay connected on laptops, iPads and phones. The company provided standard formation records, including articles of formation, an Employer Identification Number and business bank details. Instead of moving forward, T-Mobile flagged the application for further review. The owner described the subsequent steps not as a simple request for missing information but as a series of demands that ignored the specific nature of the business applying.
The first major hurdle involved a request for utility bills in the company's name. The software firm operated without physical company utilities under its own name. Consequently, the carrier asked for documents that did not exist. The owner noted that legitimate formation and tax records had already been submitted. Yet the process stalled on utility bills that the business did not have. For an applicant trying to prove its existence, this created a bureaucratic dead end where the proof required was impossible to produce.
The carrier also required recent statements from a newly opened bank account. This created a circular problem. T-Mobile wanted statements from an account that had just opened, yet it made those statements a condition for approval. The company could not make the account older or produce a history that had not yet had time to develop. A requirement presented as verification became an obstacle that the applicant could not clear on demand. The gap between the age of the account and the demand for established history left the business stuck.
T-Mobile also demanded that the company add a phone number to its website to prove ownership. The owner called this requirement absurd for a software company. The demand had no clear connection to the formation documents, tax identification or banking information already supplied. It created another condition that had to be satisfied before the application could move forward. The carrier added a website requirement that the owner says had no reasonable link to the business it was supposed to verify. This added step further delayed the process without resolving the initial questions.
The owner said support workers in India followed rigid scripts during the process. This criticism targets the corporate system rather than the workers' nationality. The responses stuck to the checklist even when the checklist did not fit the company. A software business with no utility bills in its name was still asked for utility bills. A newly opened bank account was still treated as a source of established records. The process had a script, but it lacked an adequate answer for the facts in front of it.
The company was denied access to the requested data plans until it provided documentation the owner says was impossible for its circumstances. The initial documents were treated as insufficient, while requirements that did not fit the business were added. Employees needed connections for laptops, iPads and phones, but the application remained blocked by demands for utility bills, bank statements and a website phone number. The owner considers this an inversion of what verification should accomplish.
A verification process should assess the business in front of it, not force it into a mold that does not fit. This owner says the process produced an absurd bureaucratic barrier. The carrier had formation papers, tax identification and bank details. Yet its response was to demand utility bills the company did not have, statements from an account that had just opened and a phone number on a website. That is not a sensible way to verify this software company. It is a corporate checklist that lost sight of its purpose.
More Business · Consumer Alerts · Report a business · Got a Story?






