Organization and Basis of Presentation	6 Months Ended
Jun. 30, 2015
Organization Consolidation And Presentation Of Financial Statements [Abstract]
Organization and Basis of Presentation	NOTE 1. ORGANIZATION AND BASIS OF PRESENTATION Organization inContact, Inc. (“inContact,” “we,” “us,” “our,” or the “Company”) is incorporated in the state of Delaware. We provide cloud contact center software solutions through our inContact^® suite, an advanced contact handling and performance management software application. Our services also provide a variety of connectivity options for carrying inbound calls and linking agents to our inContact applications. We provide customers the ability to monitor agent effectiveness through our user survey tools and the ability to efficiently monitor their agent needs. We are also an aggregator and provider of network connectivity services. We contract with a number of third party providers for the right to resell the various telecommunication services and products they provide, and then offer all of these services to the customers. These services and products allow customers to buy only the network connectivity services they need, combine those services in a customized enhanced contact center package, receive one bill for those services, and call a single point of contact if a service problem or billing issue arises. Basis of Presentation These unaudited Condensed Consolidated Financial Statements of inContact and its subsidiaries have been prepared in accordance with accounting principles generally accepted in the United States (“GAAP”) and the rules and regulations of the United States Securities and Exchange Commission (“SEC”). Such rules and regulations allow the omission of certain information and footnote disclosures normally included in financial statements prepared in accordance with GAAP, so long as the statements are not misleading. In the opinion of management, these financial statements and accompanying notes contain all adjustments (consisting of normal recurring adjustments) necessary to present fairly the financial position and results of operations for the periods presented herein. These Condensed Consolidated Financial Statements should be read in conjunction with the consolidated audited financial statements and notes thereto contained in the Annual Report on Form 10-K for the year ended December 31, 2014, filed with the SEC on March 4, 2015. The results of operations for the three and six months ended June 30, 2015 are not necessarily indicative of the results to be expected for the year ending December 31, 2015. Our significant accounting policies are set forth in Note 1 to the Consolidated Financial Statements in the 2014 Annual Report on Form 10-K and changes, if any, are included below. Revenue Recognition Revenue is recognized when all of the following four criteria are met: (1) persuasive evidence of an arrangement exists, (2) the fee is fixed or determinable, (3) collection is reasonably assured, and (4) delivery has occurred or services have been rendered. Determining whether and when some of these criteria have been satisfied often involves assumptions and judgments that can have a significant impact on the timing and amount of revenue we report. Our revenue is reported and recognized based on the type of services provided to the customer as follows: Software Revenue. Software revenue includes two main sources of revenue: (1) Software delivery and support of our inContact suite of cloud software solutions that are provided on a monthly subscription basis and associated professional services. Because our customers purchasing software and support services on a monthly recurring basis do not have the right to take possession of the software, we consider these arrangements to be service contracts and are not within the scope of Industry Topic 985, Software. We generally bill monthly recurring subscription charges in arrears and recognize these charges in the period in which they are earned. In addition to the monthly recurring revenue, revenue is also received on a non-recurring basis for professional services or on a recurring basis related to improving a customer’s contact center efficiency and effectiveness as it relates to utilization of the inContact suite of cloud software solutions. For subscription service contracts with multiple elements (hosted software, training, installation and long distance services), we follow the guidance provided in Accounting Standards Codification (“ASC”) 605-25, Revenue Recognition for Multiple Element Arrangements. In addition to the monthly recurring subscription revenue, we also derive revenue on a non-recurring basis for professional services included in implementing or improving a customer’s inContact suite of cloud software solutions experience. Because our professional services, such as training and implementation, are not considered to have standalone value, we defer revenue for upfront fees received for professional services in multiple element arrangements and recognize such fees as revenue over the estimated life of the customer. Fees for network connectivity services in multiple element arrangements within the inContact suite of cloud software solutions are based on usage and recognize revenue in the same manner as fees for telecommunication services discussed in the “Network Connectivity Services Revenue” below. (2) Perpetual product and services revenues are primarily derived from the sale of licenses to our workforce optimization suite of on-premise software products and services. For software license arrangements that do not require significant modification or customization of the underlying software, revenue is recognized when all revenue recognition criteria are met. Certain of our customers purchase a combination of software, service, hardware, post contract customer support (“PCS”) and hosting. For software and software related multiple element arrangements that fall within the scope of the software revenue guidance in Topic 985, Software, we allocate revenue to the delivered elements of the arrangement using the residual method, whereby revenue is allocated to the undelivered elements based on vendor-specific objective evidence of fair value (“VSOE”) of the undelivered elements with the remaining arrangement fee allocated to the delivered elements and is recognized as revenue assuming all other revenue recognition criteria are met. If we are unable to establish VSOE for the undelivered elements of the arrangement, including PCS, revenue recognition is deferred for the entire arrangement until all elements of the arrangement are delivered. PCS provided to our customers includes technical software support services and unspecified software upgrades to customers on a when-and-if available basis. PCS revenue is recognized ratably over the term of the maintenance period, which is typically 15 months. When PCS is included within a multiple element arrangement, we utilize the bell-shaped curve approach to establish VSOE for the PCS. Under the bell-shaped curve approach of establishing VSOE, we perform a VSOE compliance test on a quarterly basis to ensure that a substantial majority of our actual PCS renewals are within a sufficiently narrow range. Product revenue from customers who purchase our products for resale is generally recognized when such products are released (on a “sell-in” basis). We have historically experienced insignificant product returns from resellers, and our payment terms for these customers are similar to those granted to our end-users. If a reseller develops a pattern of payment delinquency, or seeks payment terms longer than generally accepted, we defer the revenue until the receipt of cash. Our arrangements with resellers are periodically reviewed as our business and products change. Through the quarter ended September 30, 2014, software revenue also includes the quarterly minimum purchase commitments from a related party reseller (Note 12). Network Connectivity Service Revenue. Network Connectivity Services revenue is derived from network connectivity, such as dedicated transport, switched long distance and data services. These services are provided over our network or through third party network connectivity providers. Our network is the backbone of our subscription software and allows us to provide the all-in-one inContact suite of cloud software solutions. Revenue for the network connectivity usage is derived based on customer specific rate plans and the customer’s call usage and is recognized in the period the call is initiated. Customers are also billed monthly charges in arrears and revenue is recognized for such charges over the billing period. If the billing period spans more than one month, earned but unbilled revenues are recognized as revenue for incurred usage to date. Long-term Debt We record debt issuance costs as a direct deduction from the carrying amount of our long-term borrowings, as well as costs incurred for subsequent modification of debt, incurred in connection with our long-term borrowings and credit facilities. We amortize these costs as an adjustment to interest expense over the remaining contractual life of the associated long-term borrowing or credit facility using the effective interest method for term loans and convertible debt borrowings, and the straight-line method for revolving credit facilities. When unscheduled principal payments are made, we adjust the amortization of our deferred debt-related costs to reflect the expected remaining terms of the borrowing. Recently Issued Accounting Standards In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2014-09, “Revenue from Contracts with Customers.” The guidance in the ASU supersedes existing revenue recognition guidance and the core principle behind ASU 2014-09 is that an entity should recognize revenue to depict the transfer of promised goods and services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for delivering those goods and services. This model involves a five-step process that includes identifying the contract with the customer, identifying the performance obligations in the contract, determining the transaction price, allocating the transaction prices to the performance obligations in the contract and recognizing revenue when (or as) the entity satisfies the performance obligations. In July 2015, the FASB ratified a one year delay in the effective date of ASU 2014-09, which makes the effective date for the Company the first quarter of fiscal 2018. The ASU allows two methods of adoption; a full retrospective approach where three years of financial information are presented in accordance with the new standard, and a modified retrospective approach where the ASU is applied to the most current period presented in the financial statements. We are currently evaluating the impact of adopting the new revenue standard on our consolidated financial statements. In April 2015, the FASB issued ASU 2015-03, “Simplifying the Presentation of Debt Issuance Costs,” which requires that debt issuance costs related to a recognized debt liability be presented in the balance sheet as a direct deduction from the carrying amount of that debt liability, consistent with debt discounts. This ASU requires retrospective adoption and will be effective in fiscal year 2016. Early adoption is permitted and the Company has elected to adopt this ASU in the first quarter of 2015 (Note 8). The early adoption has resulted in debt transaction fees to be recorded in the balance sheet as a direct deduction from the carrying amount of our debt liability. In April 2015, the FASB issued ASU 2015-05, “Intangibles - Goodwill and Other - Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement.” This ASU provides guidance regarding the accounting for fees paid by a customer in cloud computing arrangements. If a cloud computing arrangement includes a software license, then the customer would account for the payment of fees as an acquisition of software. If there is no software license, the payment of fees would be accounted for as a service contract. This ASU is effective in fiscal years beginning after December 15, 2015 and early adoption is permitted. The Company is currently assessing the impact of this new standard on our consolidated financial statements. We reviewed all other recently issued accounting standards in order to determine their effects, if any, on the consolidated financial statements. Based on that review, we believe that none of these standards will have a significant effect on current or future results of operations.

NOTE 1. ORGANIZATION AND BASIS OF PRESENTATION

Organization

inContact, Inc. (“inContact,” “we,” “us,” “our,” or the “Company”) is incorporated in the state of Delaware. We provide cloud contact center software solutions through our inContact^® suite, an advanced contact handling and performance management software application. Our services also provide a variety of connectivity options for carrying inbound calls and linking agents to our inContact applications. We provide customers the ability to monitor agent effectiveness through our user survey tools and the ability to efficiently monitor their agent needs. We are also an aggregator and provider of network connectivity services. We contract with a number of third party providers for the right to resell the various telecommunication services and products they provide, and then offer all of these services to the customers. These services and products allow customers to buy only the network connectivity services they need, combine those services in a customized enhanced contact center package, receive one bill for those services, and call a single point of contact if a service problem or billing issue arises.

Basis of Presentation

These unaudited Condensed Consolidated Financial Statements of inContact and its subsidiaries have been prepared in accordance with accounting principles generally accepted in the United States (“GAAP”) and the rules and regulations of the United States Securities and Exchange Commission (“SEC”). Such rules and regulations allow the omission of certain information and footnote disclosures normally included in financial statements prepared in accordance with GAAP, so long as the statements are not misleading. In the opinion of management, these financial statements and accompanying notes contain all adjustments (consisting of normal recurring adjustments) necessary to present fairly the financial position and results of operations for the periods presented herein. These Condensed Consolidated Financial Statements should be read in conjunction with the consolidated audited financial statements and notes thereto contained in the Annual Report on Form 10-K for the year ended December 31, 2014, filed with the SEC on March 4, 2015. The results of operations for the three and six months ended June 30, 2015 are not necessarily indicative of the results to be expected for the year ending December 31, 2015. Our significant accounting policies are set forth in Note 1 to the Consolidated Financial Statements in the 2014 Annual Report on Form 10-K and changes, if any, are included below.

Revenue Recognition

Revenue is recognized when all of the following four criteria are met: (1) persuasive evidence of an arrangement exists, (2) the fee is fixed or determinable, (3) collection is reasonably assured, and (4) delivery has occurred or services have been rendered. Determining whether and when some of these criteria have been satisfied often involves assumptions and judgments that can have a significant impact on the timing and amount of revenue we report.

Our revenue is reported and recognized based on the type of services provided to the customer as follows:

Software Revenue. Software revenue includes two main sources of revenue:

(1) Software delivery and support of our inContact suite of cloud software solutions that are provided on a monthly subscription basis and associated professional services. Because our customers purchasing software and support services on a monthly recurring basis do not have the right to take possession of the software, we consider these arrangements to be service contracts and are not within the scope of Industry Topic 985, Software. We generally bill monthly recurring subscription charges in arrears and recognize these charges in the period in which they are earned. In addition to the monthly recurring revenue, revenue is also received on a non-recurring basis for professional services or on a recurring basis related to improving a customer’s contact center efficiency and effectiveness as it relates to utilization of the inContact suite of cloud software solutions.

For subscription service contracts with multiple elements (hosted software, training, installation and long distance services), we follow the guidance provided in Accounting Standards Codification (“ASC”) 605-25, Revenue Recognition for Multiple Element Arrangements. In addition to the monthly recurring subscription revenue, we also derive revenue on a non-recurring basis for professional services included in implementing or improving a customer’s inContact suite of cloud software solutions experience. Because our professional services, such as training and implementation, are not considered to have standalone value, we defer revenue for upfront fees received for professional services in multiple element arrangements and recognize such fees as revenue over the estimated life of the customer. Fees for network connectivity services in multiple element arrangements within the inContact suite of cloud software solutions are based on usage and recognize revenue in the same manner as fees for telecommunication services discussed in the “Network Connectivity Services Revenue” below.

(2) Perpetual product and services revenues are primarily derived from the sale of licenses to our workforce optimization suite of on-premise software products and services. For software license arrangements that do not require significant modification or customization of the underlying software, revenue is recognized when all revenue recognition criteria are met.

Certain of our customers purchase a combination of software, service, hardware, post contract customer support (“PCS”) and hosting. For software and software related multiple element arrangements that fall within the scope of the software revenue guidance in Topic 985, Software, we allocate revenue to the delivered elements of the arrangement using the residual method, whereby revenue is allocated to the undelivered elements based on vendor-specific objective evidence of fair value (“VSOE”) of the undelivered elements with the remaining arrangement fee allocated to the delivered elements and is recognized as revenue assuming all other revenue recognition criteria are met. If we are unable to establish VSOE for the undelivered elements of the arrangement, including PCS, revenue recognition is deferred for the entire arrangement until all elements of the arrangement are delivered. PCS provided to our customers includes technical software support services and unspecified software upgrades to customers on a when-and-if available basis. PCS revenue is recognized ratably over the term of the maintenance period, which is typically 15 months. When PCS is included within a multiple element arrangement, we utilize the bell-shaped curve approach to establish VSOE for the PCS. Under the bell-shaped curve approach of establishing VSOE, we perform a VSOE compliance test on a quarterly basis to ensure that a substantial majority of our actual PCS renewals are within a sufficiently narrow range.

Product revenue from customers who purchase our products for resale is generally recognized when such products are released (on a “sell-in” basis). We have historically experienced insignificant product returns from resellers, and our payment terms for these customers are similar to those granted to our end-users. If a reseller develops a pattern of payment delinquency, or seeks payment terms longer than generally accepted, we defer the revenue until the receipt of cash. Our arrangements with resellers are periodically reviewed as our business and products change.

Through the quarter ended September 30, 2014, software revenue also includes the quarterly minimum purchase commitments from a related party reseller (Note 12).

Network Connectivity Service Revenue. Network Connectivity Services revenue is derived from network connectivity, such as dedicated transport, switched long distance and data services. These services are provided over our network or through third party network connectivity providers. Our network is the backbone of our subscription software and allows us to provide the all-in-one inContact suite of cloud software solutions. Revenue for the network connectivity usage is derived based on customer specific rate plans and the customer’s call usage and is recognized in the period the call is initiated. Customers are also billed monthly charges in arrears and revenue is recognized for such charges over the billing period. If the billing period spans more than one month, earned but unbilled revenues are recognized as revenue for incurred usage to date.

Long-term Debt

We record debt issuance costs as a direct deduction from the carrying amount of our long-term borrowings, as well as costs incurred for subsequent modification of debt, incurred in connection with our long-term borrowings and credit facilities. We amortize these costs as an adjustment to interest expense over the remaining contractual life of the associated long-term borrowing or credit facility using the effective interest method for term loans and convertible debt borrowings, and the straight-line method for revolving credit facilities. When unscheduled principal payments are made, we adjust the amortization of our deferred debt-related costs to reflect the expected remaining terms of the borrowing.

Recently Issued Accounting Standards

In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2014-09, “Revenue from Contracts with Customers.” The guidance in the ASU supersedes existing revenue recognition guidance and the core principle behind ASU 2014-09 is that an entity should recognize revenue to depict the transfer of promised goods and services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for delivering those goods and services. This model involves a five-step process that includes identifying the contract with the customer, identifying the performance obligations in the contract, determining the transaction price, allocating the transaction prices to the performance obligations in the contract and recognizing revenue when (or as) the entity satisfies the performance obligations. In July 2015, the FASB ratified a one year delay in the effective date of ASU 2014-09, which makes the effective date for the Company the first quarter of fiscal 2018. The ASU allows two methods of adoption; a full retrospective approach where three years of financial information are presented in accordance with the new standard, and a modified retrospective approach where the ASU is applied to the most current period presented in the financial statements. We are currently evaluating the impact of adopting the new revenue standard on our consolidated financial statements.

In April 2015, the FASB issued ASU 2015-03, “Simplifying the Presentation of Debt Issuance Costs,” which requires that debt issuance costs related to a recognized debt liability be presented in the balance sheet as a direct deduction from the carrying amount of that debt liability, consistent with debt discounts. This ASU requires retrospective adoption and will be effective in fiscal year 2016. Early adoption is permitted and the Company has elected to adopt this ASU in the first quarter of 2015 (Note 8). The early adoption has resulted in debt transaction fees to be recorded in the balance sheet as a direct deduction from the carrying amount of our debt liability.

In April 2015, the FASB issued ASU 2015-05, “Intangibles - Goodwill and Other - Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement.” This ASU provides guidance regarding the accounting for fees paid by a customer in cloud computing arrangements. If a cloud computing arrangement includes a software license, then the customer would account for the payment of fees as an acquisition of software. If there is no software license, the payment of fees would be accounted for as a service contract. This ASU is effective in fiscal years beginning after December 15, 2015 and early adoption is permitted. The Company is currently assessing the impact of this new standard on our consolidated financial statements.

We reviewed all other recently issued accounting standards in order to determine their effects, if any, on the consolidated financial statements. Based on that review, we believe that none of these standards will have a significant effect on current or future results of operations.