This use case is ideal for an RIA firm that wants a higher level of automation than the Quik! App provides but wants to keep the workflow simple. The focus of this case is on a single custodian, but it could be extended to multiple custodians.

Workflow Overview

The ideal scenario is as follows:

1. From within the CRM, choose a client and then click on a button or link to initiate the forms workflow.

2. Still within the CRM, a custom screen asks the user to pick a form bundle from Quik!.

   1. Configure the form bundle directly within the Quik! Customer Central website (https://qcc.quikforms.com/QFE/)

   2. Call the Form Group API to get the forms:

      1. API guide: https://efficienttech.atlassian.net/wiki/spaces/QAG/pages/980975720

      2. Swagger: https://websvcs.quikforms.com/rest/formgroups/v1000/swagger/index.html

      3. Method: Get FormGroups

   3. Display the list of form groups to the user

3. The user clicks a button or link to generate the forms

   1. Call the Quik! authentication API (https://efficienttech.atlassian.net/wiki/spaces/QAG/pages/34144268)

   2. Pass the following info to the Quik! Forms Engine API (Execute HTML )

      1. FormGroupID = the form group the user selected

      2. Client Data Fields = all of the CRM fields for the selected client(s)

      3. Form Configuration Settings = all of the settings for e-sign, form viewer control, etc.

   3. Receive the HTML form to display to the user

4. Display the form to the user

5. User completes the form and either prints or sends for e-signature (using the SIGN button in the form viewer).

Assumptions

This workflow assumes the following:

1. Your CRM environment can call Quik! REST APIs

2. Your CRM environment can display the HTML form returned by the Quik! Forms Engine

3. Your user doesn’t need a complex form search and can rely only on form bundles.

   1. Form Bundles should be named intelligently, like (Custodian + Account Type, or Company + Form Bundle Purpose, etc.) “Schwab Individual Account”, “Fidelity IRA”, etc.

4. Your allows you to map your CRM fields to the Quik! Field Definition so you can prefill forms

   1. Field Mapping could be done directly in the Quik! API call or you could build a custom mapping interface in the CRM (which is more complex)