LogoLogo
Back to studio
  • Formsort documentation
  • ⏩Quickstart
    • 🟒Get started with Formsort
    • 🍎Core concepts
    • ℹ️Question and content reference
    • πŸ“•Key terms
    • 🏞️Create your first flow
    • πŸ“–Add content and collect answers
      • 🀳Capture demographic data
      • ℹ️Add informational content
      • πŸ” Review your variable schema
    • 🎨Create a theme
      • Set brand guidelines
    • 🀹Personalize your flow
      • 🌟Template your variables
      • 🧠Add conditional logic
      • πŸ’«Using conditional logic with Calculated and API variables
      • πŸ”šEnd the flow
    • πŸ”€Set up integrations
    • πŸš€Go live
      • Auditing your flow for content, functionality, and design
    • πŸ’ΌCommon use cases
      • πŸ’”Disqualify responders
      • πŸ—“οΈAdd a scheduling option
      • πŸ“„Allow responders to read and accept your company policies
  • πŸ—οΈBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • πŸ’ΎHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • πŸ“ΊGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • 🏒Teams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page

Was this helpful?

  1. Quickstart
  2. Go live

Auditing your flow for content, functionality, and design

Along with our pre-launch checklist to ensure your flow is technically ready to go live, we recommend doing an audit of your flow in a staging environment - both on a desktop in different browsers and on different mobile devices.

This can be a solo review, or you can send a deployed variant out to others in your company to test. The more folks you have going through a β€œlive” flow, the easier it will be to catch edge cases β€” especially if your testing group is on different devices.

Here’s what we look for to ensure a great responder experience:

Instructions

Adding clear instructions on how to complete your flow can help the responder understand what is needed from them, reduce error rates, and increase form completion rates.

Redundancy

It is important not to ask for the same information twice. Pre-populating answers with information you already have will lead to a better responder experience.

Sensitive information

Explaining why you are asking for a piece of sensitive information will help increase the likelihood of responders giving you the information you need'

Question order

Grouping and ordering the questions in a logical sequence will create a better experience for the responder.

Personalization

Personalizing the flow based on previous answers may improve overall flow completion rates.

Question types

Using the appropriate question types can help improve the responder experience. For example, having a structured address question with different fields for Street, State, Country and Zip Code as opposed to one text question will help the responder save time.

Returning responders

Allowing the returning responders to start from where they left off improves flow conversion rates, especially in longer and more complicated flows.

Navigation

Ensuring that clicking the back button and refreshing does not take the responder out of the flow is important for creating a good responder experience.

Submit/success page

Giving clear visual feedback to the responder that a flow is successfully submitted will help avoid duplicate submissions and improve the responder experience.

Error messages

Including helpful error messages will improve the quality of the data you will receive and increase flow completion rates. Communicating why a certain input is not valid or indicating clearly when a responder is missing a required field will help improve responder experience.

Optional fields

Indicating which fields are optional will improve the overall responder experience. Indicate which fields are optional or indicate are required or both

Progress bar

Showing responder’s progress will help responder stay motivated to complete the survey and improve completion rates.

Single column

Laying out all the information in a single column (as opposed to multiple) will improve the website readability and the responder experience.

Multi-step flows

Having too much information on a page can be overwhelming for the responder. If possible, consider having fewer questions per page.

Input fields size

Input field sizing can be used to communicate your expectations of how lengthy the responses should be.

Dropdown menus

If there are less than six options, using buttons (instead of dropdown menus) might be a more effective way of communicating the available options to the responder.

Responsiveness

Responsive design allows your flow content to be viewed in an optimal manner across all screen solution and sizes, and ensures that it looks great on all devices. This will improve the overall responder experience.

Placeholder text

Placeholder text can be used to provide responders with examples of valid answers and can improve responder experience, while reducing errors.

Accessibility

Creating accessible flows is crucial for improving the experience of all responders. This includes having appropriate color contrast, screen-reader friendliness, and keyboard navigation, etc.

Style

Having a consistent style across your flow and reflecting your brand perfectly through fully customized form elements not only creates a better visual experience but also reinforces trust.

PreviousGo liveNextCommon use cases

Last updated 2 years ago

Was this helpful?

Example:

Example:

Article:

Article:

Example:

Example:

Article:

Doc:

Doc:

Doc:

Doc:

Article:

Doc:

Example:

Coming soon:

Doc:

Example:

Example:

Example:

Example: Example:

Doc:

Doc: Doc:

Example: Example:

Example: Guide:

⏩
πŸš€
CareOf
Capsule
Designing effective tooltips
Passing data into flows
Tomo social security number collection
BetterHelp phone number collection
Best practices for designing a client intake form
Templating variables
Adding conditional logic
Content types
Returning responder behavior
Leveraging partial form responses
Previous button
Murad results page
Custom validators
Optional questions
BarkBox progress bar
Bright flow
Future flow
StitchFix style field
Everybody β€œAnything else?” field
Dropdown examples
Inputs and dropdowns
Dimension variables
Preview window viewport
BarkBox dog name
Lemonade signup
Illustration examples
Create a theme