I think I understand where you're going with this, but I think you might be force feeding the wrong pattern. So, seeing as this will be a value from your database, you need to ensure a few things:
- That if a related item is there or not there, your app fails gracefully.
- That you're using convention over configuration to aid maintainability.
The pattern/technique I think you need is a mobile view engine. Take this example of Scott Hanselman's Mobile View Engine for MVC3 (source) as an example of this. Note how the engine looks for a .mobile.cshtml view and falls back to the plain .cshtml view if it doesn't exist. Obviously, this is now built into MVC4, but the technique is a viable one for a variety of purposes.
You could adapt this to your needs, looking to a session variable or similar (Singleton over Session would be my method) for your stored database value related to your customer to get the view prefix and provide a different view prefixed specifically for it.
The fallback is graceful and the pattern is all about convention and injection. It's certainly the approach I would take to solve your problem. I hope this has been of some help, whether you end up using the technique or not. Good luck and Godspeed!