Perception is king, too bad it often mislead! Let's attempt to talk you out of creating a custom line of business application for basic electronic forms scenarios. If we really examine the large majority of line of business applications we spend time creating, deploying, and monitoring, I think we can all agree there are large number of applications that are designed around the same core requirements which include providing the ability to capture, retrieve, edit and submit, data to an API, service or storage repository (i.e. a database or content management system). Think about the amount time, money and energy creating the most basic of applications, using technologies like .NET, Java, PowerBuilder VB6, etc. This where I have spent a far amount of time recommending InfoPath to our customers, only to meet the same objection time and time again. InfoPath is just another technology I have deploy, and support on the client. So, if it is so great, then why isn’t everyone using and deploying InfoPath solutions? The most common customer objection to using InfoPath is the requirement to deploy the InfoPath client. Let's just take a minute to think about this, in order to fill out an offline form you have to install something on the client. The form requires a container, in other vendor solutions and even your custom solution. Let’s take a look at a few alternatives and discuss how InfoPath helps to solve this problem of increasing the number of applications your call center and It team need to support.