Technical Support Overview

FaceTec's Support Pledge

FaceTec pledges to provide fast, thorough, and enthusiastic support when comprehensive information about FaceTec-related behaviors are reported.


Key Requirements for Submitting Support Requests

  1. Providing detailed information about your observation, question, or request:  The most important method of receiving comprehensive support from FaceTec is to provide detailed information to FaceTec in your initial request.  Please take care to provide all context about your observation or question, please provide all information that you have gathered about your observation or question, and please provide any and all logs, screenshots, conversation snippets, videos, code, and background about your observation or question.
  2. Searching the Developer Documentation: The FaceTec Developer Documentation is quite comprehensive and the answers to most common questions can be found in our guides. To learn more, please see our Getting Started Guide, FaceTec Server Integration Guides, UI Customization Guide, FAQ, and Technical Support Home Page.
  3. Using the Support Form: The Support Form has been specifically designed to ensure that FaceTec has all of the information necessary to promptly and thoroughly investigate and resolve your request. We ask all Users to completely follow the instructions in the Support Form, so we can properly reproduce the behavior reported, understand the intended behavior of your code, and determine the appropriate fix.
  4. Update Policies: FaceTec SDKs must be kept up-to-date for Security and Usability purposes. In order to Request Support from FaceTec, you must first ensure the behavior occurs on the latest versions of the SDKs. Before creating a Support Request, please make sure you have Read & Understand our Update Policies and Processes.
  5. Reproducing the Behavior: The vast majority of problems or unexpected behaviors are not truly intermittent - there is usually some set of steps to perform that will reproduce the behavior. FaceTec can only diagnose behaviors that can be reproduced. Please ensure you have clearly documented the steps to reproduce the behavior reported in your Support Request. If you send us a Support Request with a behavior that cannot be reproduced, we will unfortunately not be able to assist you.
  6. Proprietary Code: FaceTec will never request proprietary code that contains any of your important internals or trade secrets. However, in order to provide Support, we will need access to the exact commands, code, and logs related to FaceTec Software, so we may accurately reproduce the behavior in our investigation.
  7. How to Share Data: Logs, files, and videos can be shared with us in either a shareable link or as a ZIP file attachment. If your ZIP file is larger than 10 MB, please send the ZIP file as a shareable link and specify the link in the Support Request Form.
  8. Meeting Requests: 99% of the time, Support Requests are more-quickly resolved by providing FaceTec with all of the requested information and completing the Support Request form.

Scope of FaceTec Support

FaceTec will provide assistance for any behavior regarding the FaceTec software itself. However, as FaceTec integrates into numerous other client and server technologies, we can only provide high level assistance and make suggestions for behaviors not directly related to FaceTec’s SDKs. Developers themselves are responsible for integrating, debugging, and maintaining their systems that connect to the FaceTec Software.

Bahaviors Related to 3rd Party Software

Behaviors related to 3rd party software are generally out-of-scope for FaceTec Support, except for the few instances where we can provide general guidance. This means that behaviors related to the following technologies must be debugged and owned by the Developer integrating FaceTec:

  • Behaviors related to 3rd Party Mobile Frameworks (React, React Native, Flutter, Cordova, Angular, etc.).
  • Behaviors related to Database integrations like MongoDB, SQL, AWS S3.
  • Behaviors related to cloud platforms, cloud platform technologies, and orchestration technologies -- i.e. AWS (EC2, ECS, EB, S3, etc.), Google Compute, Azure, Kubernetes, etc.
  • Any other 3rd party software, libraries, frameworks, or technologies.

FaceTec Server Support

FaceTec is fully committed to investigating FaceTec Server Initialization-related behaviors where the FaceTec Server has been configured with Wizard Configuration and is using in memory stub db. However, when you introduce code customizations to the FaceTec Server, you are responsible for fully investigating behaviors related to your own customizations, and as such, we can only provide high-level, general guidance in these scenarios.

FaceTec provides Sample Code for some of the above-mentioned libraries, technologies, and frameworks, but developers are responsible for owning the integration code. The FaceTec Sample Code is provided as-is, and you are encouraged to modify it as needed depending on your use case, and as needed depending on unexpected integration behaviors that may arise.

Behaviors Related to Specific User Cases

FaceTec will investigate specific Device Compatibility Behaviors and other related topics where Users are unable to Prove 3D Liveness or successfully perform ID Scans. However, FaceTec requires at least 5 3D FaceScans, 5 3D FaceMaps, and/or 5 ID Scans from these types of User Cases in order to perform investigations to ensure that Users have been provided with the ability to perform enough Scans to overcome environmental behaviors or problems with Users not following on-screen guidance provided by FaceTec.

The Scope of FaceTec Support in these types of cases covers investigating data that has been sent in order to uncover potential problems, unepexted behaviors, and/or improvements. FaceTec cannot provide customized reports on each and every piece of data that is sent, and generally will only provide information back in terms of whether or not an unexpected behavior or improvement was found, as well as general guidance about how to handle the reported behavior.


Support Request Severity Levels

Severity 1 - Minor Integration-Related Behaviors, Upgrade Assistance, Encryption Key or Usage Log Questions with No Impact to Live Applications

Severity Level 1 refers to non-critical topics arising during development, integration, or upgrades, general questions, requests for enhancements, and all other topics where a Live Production App is not actively impacted.

FaceTec Support will handle Severity 1 Requests as soon as possible, but as these behaviors types are typically non-blocking and have little to no impact on End Users or Production Environments, they will be responded to in the order they are received.

Severity 2 - Moderate Behaviors Impacting Live Applications / Production Systems

Severity Level 2 refers to errors or behaviors that have been identified but do not prevent normal operation of the Customer’s system, or to a situation that may be temporarily circumvented using an available workaround.

FaceTec Support will handle Severity 2 Requests with an urgency dependent on the behavior being reported and will strive to resolve the behavior quickly.

Severity 3 - Major Behaviors Impacting Live Applications - Critical Errors in Production Systems

Severity Level 3 refers to errors or behaviors that directly impact the Customer’s Production Environment. Even when Customer services are operational, performance is highly degraded to the point that there is a major impact on usage. Services are either moderately or severely impaired and if the Customer’s system is functioning, it is only in a reduced capacity without a feasible workaround available.

FaceTec Support will handle Severity 3 Requests with high urgency and use all commercially reasonable efforts to resolve the behavior quickly.


Support Request Types & Severity Level Examples

Severity LevelSeverity 1Severity 2Severity 3
Pre-Upgrade BehaviorsAll Pre-Upgrade Behaviors  
Integration & Pre-Production Behaviors (Development Mode)Most Integration & Pre-Production Behaviors  
Specific Case Reports - Liveness Not Proven, Match Rejections, IDScan Rejections, OCR-related BehaviorsMost Specific Case Reports of Rejections  
General Behavior QuestionsMost General Behavior Questions  
Questions and Errors for non-FaceTec SoftwareMost Behaviors in this category.  Please see Scope of FaceTec Support for more info.  
UI/UX BehaviorsMost other UI/UX BehaviorsBehaviors causing significant UI degradations for significant volumes of End Users in Live Apps 
Device SDK Exceptions/CrashesTesting & All Other Crashes Live App Crashes
FaceTec Server Exceptions/Crashes Live Environment Occasionally CrashingLive Environment Crashing & Unable to Stay Online & No Workaround
Memory Leaks Most leak reports that are non-blocking, intermittent, or not largeLarge, proven leaks that eventually cause a crash
Encryption Key Renewals & Billing-related topicsRequests for Encryption Key Renewal for Apps that are not In-Compliance with FaceTec Update PoliciesRequests for New Encryption Keys when All Production Apps are In-Compliance with FaceTec Update PoliciesMost Billing-related Behaviors
Success Rate BehaviorsAll Success Rate Questions that fall within Documented Ranges 3rd Try Success Rate is < 90% 
5th Try Success Rate is < 95%
Security-related Reports  Most Security-related Reports