+2  A: 

Could you use subdomains and change the second URL to customerx.abc.com/customers/tx/Austin/5? What about tacking the customerx potion onto the end as an optional parameter like so? abc.com/customers/tx/Austin/5?customer=x

Tahbaza
@Tahbaza,That was one of the ideas that had crossed my mind. Alas, I can't do it that way though. We have an existing site that uses Webforms and all the urls are in production already. We are migrating this app in a piecemeal fashion to MVC. So, it's essential that we maintain the same url scheme :(
Praveen
In that case maybe redirecting permanently as described here would be a solution (http://haacked.com/archive/2008/12/15/redirect-routes-and-other-fun-with-routing-and-lambdas.aspx)
Tahbaza
+1  A: 

I would've made the route like this:

customers/{statename}/{marketname}/{customer}  

and do the pagenumber as a querystring. That way the url would be:

www.abc.com/customers/tx/Austin?pagenumber=1

or

www.abc.com/customers/tx/Austin/CustomerX

The construction of the url will also most likely follow the usagepattern of the site aswell:

  1. Click Customers
  2. Select a State
  3. Select a marketname
  4. Browse pages
  5. Click the customer
Yngve B. Nilsen
Unfortunately, I cannot go with a different URL scheme. We have to stick to our existing scheme for backward-compatibility as well as SEO.
Praveen