Integration Examples

Notes:

1. Caller calls over PSTN to IVR System running in Client data center or cloud.
2. IVR System checks internal database or system for Caller info.
3. Internal database or system returns VBG UserID to IVR System.
4. IVR System create transaction in VBG Platform and prompts Caller for speech sample using IVR dialog.
5. IVR System records Caller's speech sample.
6. IVR System RESTfully POSTs sample to VBG Platform which performs verification scoring; transaction is closed. VXML, SOAP, or Streaming APIs could also be used.
7. IVR System makes pass/fail decision and initiates next steps as appropriate.

** This configuration requires IVR developers to handle all audio prompting, capture, sending to VBG Platform, etc.

Notes:

1. User engages with Client Application or System.
2. Client Application determines that User needs voice authentication and creates transaction in VBG Platform.
3. Client Application instructs User to place call into IVR System running built-in VBG IVR Dialogs.
4. User calls into IVR System and responds to prompt for speech sample.
5. IVR System RESTfully POSTs sample to VBG Platform which performs verification scoring; transaction is closed. VXML, SOAP, or Streaming APIs could also be used.
6. During IVR call, Client Application is periodically monitoring status of call.
7. Client Application makes pass/fail decision and initiates next steps as appropriate.

** This configuration saves developers significant time as VBG handles all IVR logic, speech capture and transmission, integration to platform, etc.

Notes:

1. User engages with Client Application or System.
2. Client Application determines that User needs voice authentication and creates transaction in VBG Platform.
3. VBG Platform takes instruction from Client Application and places outbound call to User. User responds to prompt which is RESTfully POSTed to VBG Platform. Verification sample is scored and transaction is closed. VXML, SOAP, or Streaming APIs could also be used.
4. During IVR call, Client Application is periodically monitoring status of call.
5. Client Application makes pass/fail decision and initiates next steps as appropriate.

** This configuration saves developers significant time as VBG handles all IVR logic, speech capture and transmission, integration to platform, etc.

Notes:

1. Client Application determines that User needs voice authentication and creates transaction in VBG Platform.
2. VBG Platform takes instruction from Client Application and places outbound call to User. User responds to prompt which is RESTfully POSTed to VBG Platform. Verification sample is scored and transaction is closed. VXML, SOAP, or Streaming APIs could also be used.
3. During IVR call, Client Application is periodically monitoring status of call.
4. Client Application makes pass/fail decision and initiates next steps as appropriate.

** This configuration saves developers significant time as VBG handles all IVR logic, speech capture and transmission, integration to platform, etc.

Notes:

1. Caller calls over PSTN to IVR System running in Client data center or cloud.
2. IVR System checks internal database or system for Caller info, then creates transaction in VBG Platform.
3. IVR System prompts Caller using VBG's built-in IVR dialogs and records sample.
4. IVR System RESTfully POSTs sample to VBG Platform which performs verification scoring; transaction is then closed. Streaming API could also be used for Steps 3 and 4.
5. IVR System sends result to Call Center Agent indicating pass/fail status.
6. With passing result, Call Center Agent initiates 2-way authenticated communications with Caller and engages as usual.

** In this situation, VBG's IVR Dialogs help to greatly simplify the integration.

Notes:

1. Caller calls over PSTN to IVR System running in Client environment.
2. IVR System creates transaction in VBG Platform.
3. IVR System sends transaction ID to Call Center System in Client environment.
4. IVR System connects Caller with Call Center Agent.
5. Caller and Call Center Agent engage in conversation as normal.
6. Call Center System monitors transaction within VBG Platform.
7. IVR or Call Center is streaming audio to VBG Platform throughout call (or can send periodic recordings).
8. Call Center Agent can refer to Call Center System to determine pass/fail status.

** This configuration requires some setup of Media Streaming between Client and VBG environments.

Notes:

1. Computer User logs into VPN Server using appropriate client software and their UserID and Password as usual.
2. VPN software for Computer User is configured for Multi-Factor Authentication, so VBG RADIUS Server is contacted.
3. VBG RADIUS Server first performs LDAP authentication with User ID and Password.
4. If successful, VBG RADIUS Server creates Transaction on VBG Platform to initiate voice biometric authentication.
5. VBG Platform can trigger authentication using Mobile Push or Outbound IVR Call, depending on configuration. Mobile push via the VBG Authenticator™ is often preferred, as usage costs are lower and VBG's phone authentication provides an additional factor of security.
6. VBG RADIUS Server monitors Computer User's authentication Transaction on VBG Platform.
7. VBG RADIUS Server sends "pass" or "fail" result back to VPN Server as appropriate.
8. VPN Server either logs Computer User into VPN or denies access.

** This configuration requires NO development -- only installation of components and configuration!

Notes:

1. Computer User logs into ADFS enterprise SSO portal with their UserID and Password as usual.
2. ADFS first checks Computer User's credentials in Active Directory.
3. If successful, ADFS policy for Computer User is configured for Multi-Factor Authentication, so VBG ADFS Adapter is contacted.
4. VBG ADFS Adapter creates Transaction on VBG Platform to initiate voice biometric authentication.
5. VBG Platform can trigger authentication using Mobile Push, Outbound IVR Call, or WebRTC depending on configuration. Mobile push via the VBG Authenticator™ is often preferred, as usage costs are lower and VBG's phone authentication provides an additional factor of security. However, if operating in a corporate environment, WebRTC authentication via headset provides even greater cost savings.
6. VBG ADFS Adapter monitors Computer User's authentication Transaction on VBG Platform.
7. VBG ADFS Adapter sends "pass" or "fail" result back to ADFS as appropriate.
8. ADFS either logs Computer User into enterprise system or denies access.

** This configuration requires NO development -- only installation of components and configuration!

Notes:

1. Computer User logs into Windows 10+ computer with their UserID and Password as usual.
2. Windows Login Provider checks Computer User's credentials in Local Credential Storage.
3. If successful, Computer User is configured for Multi-Factor Authentication, so VBG Credential Provider is contacted.
4. VBG Credential Provider creates Transaction on VBG Platform to initiate voice biometric authentication.
5. VBG Platform can trigger authentication using Mobile Push or Outbound IVR Call, depending on configuration. Mobile push via the VBG Authenticator™ is often preferred, as usage costs are lower and VBG's phone authentication provides an additional factor of security.
6. VBG Credential Provider monitors Computer User's authentication Transaction on VBG Platform.
7. VBG Credential Provider sends "pass" or "fail" result back to Windows Credential Provider as appropriate.
8. Windows Credential Provider either logs Computer User into Windows 10 computer or denies access.

** This configuration requires NO development -- only installation of components and configuration!

Notes:

1. User with Smartphone, and ideally the VBG Autenticator™ mobile app, logs into Computer System with multi-factor authentication (MFA). Note that VBG Authenticator™ users go through external, 3rd party phone validation and have a unique token assigned prior to usage, effectively adding another layer of security.
2. Computer System determines User needs voice authentication as one of the security factors and sends request via RESTful API to VBG Platform.
3. VBG Platform initiates mobile "push" to User's smartphone, which displays one-time passcode in VBG Authenticator™. Alternatively, in the absence of VBG Authenticator™, VBG Platform could initiate outbound phone call and use IVR Dialogs to achieve similar result.
4. User repeats one-time passcode, which is then sent back via RESTful API to VBG Platform for content-checking and voice biometric analysis.
5. VBG Platform communicates pass/fail result to Computer System.
6. Authenticated User is allowed to proceed.