To ensure your long-term success with Quik!'s forms processing solution, we spend a large amount of time and energy up front to get you set up and moving in the right direction from day one. We enjoy working closely with our customers and partners, diving deep into solving problems, and doing everything in our power to create a successful implementation that results in less work for your team both now and in the future.

Setting up Quik! for both a proof of concept (POC) and for your production usage includes a variety of services and capabilities from our team. This page highlights the various parts of an implementation and how Quik! supports it.

View Our Onboarding Presentation

To view an overview slide deck on this document, please view our PPT slides:

Table of Contents

Setup and POC Limits

During the setup and/or proof of concept phase, which can last for up to 6 months, there are no usage or per-user fees for up to 25 users or 2,500 forms per month. In addition, most, if not all, form building fees are included (subject to limitations, per the agreement).

Account Setup

For a checklist of what is needed to set up and use your Quik! account, please see our Onboarding Checklist. Account setup includes:

• Credentials - establishing your account

• Adding Forms - building and subscribing to forms in the library

• Form Settings - creating form groups, field rules, and field attributes

• E-Sign Settings - linking to your e-sign account and configuring options (E-Signature Setup and Enable E-Signatures on Forms)

Meetings

Our support and implementation team is here to help and is available for many different types of meetings to help you succeed. These meetings may include:

• Customer Success Kick Off: Our Director of Customer Success would love to meet with you, introduce the team, ensure you know how to get support, and ensure you’re happy with our team.

• Technical Kick Off Meeting - Meet with your technical team to discuss details of the implementation, review API guides, and ensure you get started on the right path. Technical Kick-off Guide.

• Form Setup - Our forms teams should meet with your team to hand off the forms and get them built the right way the first time.

• Ongoing Status Meetings - If you’d like us to participate in any of your periodic meetings, please invite us to join, and we will.

• Field Mapping Training - We recommend having your team sit down with us to review our field mapping methodology to ensure you implement Quik! in the best, lowest-cost way. Field Mapping Guide

• Form Group Setup - If you are going to set up a lot of form groups, let’s discuss how we can make that process easier for you by building the form groups in Excel and having us upload them into our system.

• Webinars and Training - To the extent we can assist with outreach to your field, our marketing and service team are happy to help with ideas, content, delivery and execution of training programs.

Training

All systems need some form of introduction, training and representation of how the new system will benefit the users - it helps to answer the question “what’s in it for me” for your users. We’d like to help.

The Quik! product you’re implementing (whether that’s our APIs and creating your own user experience or integrating with and deploying our Quik! App hosted solution) will play a factor in how much support we can provide directly to your users. In all cases our team is ready to help you with:

• Ideas - We can share what we know has worked for others and ideas for content and format.

• Benefits - Help your users see the benefits.
  We know the core benefits our solution can provide over alternatives (like progressive prefill, draft mode, householding, form copies, seamless and deep e-sign integration, higher data capture, etc.) to help your users see how your new forms solution will improve their lives.

• Content - We have content that may be useful and you can use at your convenience - videos, articles, FAQs, Powerpoints, etc.

• Webinars - When appropriate (especially for Quik! App users), we can host or co-host webinars to train your users on the features and usage of our products. (NOTE: We are not able to do this for your proprietary systems using our APIs, but we are happy to co-host to bring inspiration and insights and answer questions.)

Forms

Identifying the forms you want to use and how you want to use them is an essential component of using Quik!

Form Building

Working with our forms team (send forms to forms@quikforms.com or request access to the Quik! Forms Manager website), we will add and build any of your own proprietary forms to the Quik! library. Your personal library(s) will be private and only available to your account or accounts you authorize (e.g., sub-accounts). Our forms team will meticulously set up your forms to adhere to our field naming standards for use with Quik!.

If you need us to add forms for another company, please also send those requests to forms@quikforms.com.

Subscribe To Forms

Before you can generate or process forms, your account needs to have a subscription to the library or the individual forms. This process is fully explained here: Subscribe To Forms

We can help you subscribe to your forms, or you can do it yourself (Manage Account with the Quik! Forms Enterprise Manager).

Form Grouping

One option in how you help users find or use forms is to leverage our Forms Group API (or Forms Bundle feature in the Quik! App). See this article for full details: Create Groups & Form Groups

There are a few use cases that Form Groups solve for:

• User Bundles - allow users to build and manage their own form bundles

• Global Bundles - set up form groups that all users can use to find forms in packages

• Predetermined Form Packages or Workflow Outcomes - use form bundles as an outcome for a specific workflow that results in the right forms package without having the user find or select the forms individually

Field Mapping

One of the unique values that Quik! offers is our robust field definition that our team uses to build and maintain forms. With over a million fields that can be applied to forms, Quik! Forms are the most comprehensive forms built with a single definition of fields. Our team will help you figure out how to navigate, use, and determine which field in our definition is the right one to use in your implementation.

What this means to you…

When you use Quik! to generate, prefill, and extract data from forms, you map your data fields to our definition, not our specific forms (there are exceptions to this rule, which will be explained).

Generally speaking, a value like “First Name” or “Date of Birth” is always the same value for the same person across any form in the world; thus, Quik! uses a single definition for each field that is built into each form. By mapping your data to the Quik! Field Definition (and not some custom field name specific to each form) you can be assured that your data will seamlessly flow to any form you choose to generate.

Obviously, there are nuances to our data model. For one, data can take on different roles (e.g. the first name could belong to an account owner vs. a beneficiary vs. a minor, etc.). To accommodate the different roles on forms, whether that be for people, companies, accounts, or other objects, every field has two parts - a role (or parent field) and a base field. This is fully explained in The Quik! Field Definition Guide.

Second, some forms have specific fields that require attention, like checkboxes that have specific lookup values that you’ll need to know.

Finally, the great thing about having a single definition is that once you map a field, you are essentially done. Many customers have had little or no maintenance to fields once they’re mapped, even as the form designs change.

Sub-Accounts

Quik! supports the concept of sub-accounts or Parent/Child account relationships. Parent / Child Accounts and User Setup

If your implementation includes offering groups of users (e.g. offices, branches, affiliated companies, or even customers) their own version of your solution that includes Quik!, it may be necessary to have more than one Quik! account. The main reasons for doing this are to keep form library subscriptions, form bundles, reporting, and/or billing separate for each group.

By adding a sub-account to your primary account, our reports will automatically roll up all the transactions, by account. so you can see which account is using the system and get a total of all usage.

In addition, settings can be applied to the parent account and pushed down to the child accounts. This is especially helpful for controlling what users are allowed to do, see, and/or configure on their child accounts.

API Architecture Support

One of the challenges in implementing any system is knowing which API endpoints to use for a given purpose. Although we provide extensive documentation about our APIs, we believe that personal touch in the form of meetings, chats, Slack messages, calls, etc., can greatly speed up a customer's implementation process. We are happy to talk about the APIs, figure out which ones are best suited for your particular purpose, and help troubleshoot issues that can sometimes arise.

Form Generation Options

When it comes to the point in your workflow(s) where you want to generate forms, there are over 200 different configuration options that you can leverage. The minimum options are the list of FormIDs you want to generate, and the second most important part is the list of fields and their values to prefill on the form. Beyond that, the rest of the options pertain to various user experiences, data management, and form options (some of which have been discussed earlier in this document). Below are additional concepts to review, and our team can help you determine how best to use them.

For a list of the most common configurations, please look at this section, which contains several detailed articles on each type: Configurations

E-Sign Configurations

Quik! supports Docusign and SIGNiX e-sign integrations. These integrations are very robust and include a lot of potential options and configurations (approximately 50 options each). Each configuration option has its own details.

Docusign

SIGNiX

Form Copies and Form Group Instances

A common use case with forms is to have multiple copies of the same form in a single form package or e-sign envelope. For example, multiple asset transfer forms when combining multiple accounts into a single account. To add duplicate copies of forms, please review this section of our documentation: Adding Duplicate Forms To A Package

Another common request is to create multiple form packages in a single request so users can sign all of them in a single envelope. For example, for households that have multiple accounts. This type of functionality is referred to as Form Group Instances and is detailed here: Configuring Form Group Instances

User Interface Changes

When using the Quik! API there are a variety of ways to change and affect the Quik! Form Viewer. The simplest and most common item is to change the Quik! logo with your own, yet you can also make very complex changes using CSS and JavaScript. See this section for details: https://efficienttech.atlassian.net/wiki/spaces/QAG/pages/53943427

Custom Javascript

One of the ways to enhance the user experience when using forms is to add custom javascripts that perform custom actions. For example, perhaps you want to look up an address and validate it. Javascripts can be added to the form when calling the Quik! Forms Engine API (execute/html method) in a variety of ways. Please see this section for more: https://efficienttech.atlassian.net/wiki/spaces/QAG/pages/53904688

Go-Live and Post-Live Support

When you’re ready to go live with your system, we want to know. Our internal project managers track your expected go-live dates and key milestones so we can be prepared to support you. We have provided support in many different ways, depending on what our customers ask of us.

For example, if you have a major release and tell us, we won’t schedule our own release for that night/weekend to ensure your update goes smoothly and is not impacted by some changes we’re making.

Another example: We provide a UAT (user-acceptance testing) environment so customers can test any new updates and features we roll out before our release date.

Whatever support you need, we will do our best to be present, responsive, and accountable to help you through it. Just ask us what you need, and our team will tell you what we can and cannot do.

Reporting

If you are interested, we can provide you with a reporting dashboard to give you visibility into how you’re using Quik!. Access to your reports is free, and all reports are updated monthly.

Alternatively, we offer a reporting API (the same API our dashboard uses) so you can run reports yourself and integrate them into your own system. Again, reports are updated monthly.