Our Platform. Your Vision.

Customer Requirements

This article covers Customer Requirements. To see examples of common Customer Requirements in use, check out these here.

 

Customer Requirements Overview

Customer Requirements reference Customer Segments to restrict enrollment types to certain customers or restrict promo codes to certain contract holders.

Customer Requirement applied on an Enrollment type restrict customers added to that enrollment to those that meet the requirement. If the customer later becomes invalid, they will alert at check in if the check in guard is enabled. There are tools to bulk change enrollment types on invalid customers in Manage > Contracts > Bulk Recurring Changes

Customer requirement applied to Promo Code looks at the Contract Holder to see if they meet the customer requirement.  They can also optionally ask for an attachment to make the promo code valid.

If no attachment is required, apply both the Requirement AND the same segment to the promo code or just use a customer segment to restrict the promotion. See Examples here.

Contracts are NOT changed automatically when they fail a customer requirement, but there are tools to view and manage the changes.

A Check-in Guard can be configured to alert when customers do not meet the customer requirement.

 

Create a Customer Requirement

Before making a customer requirement:

  1. If your Customer Requirement involves an attachment (such as a student will submit active schedule) then create that attachment (with or without validation)
  2. Make sure you make a segment that will capture people who should QUALIFY. 

See Example for Student Schedule Requirement for Attachment and Segment Configuration example to set up your required attachment.

 

Go to Manage Menu > Customer Segments & Requirements >  ‘Customer Requirements’ (Tab) > New Customer Requirement

  • Select a Customer Segment - This segment should reflect people who are VALID for this customer requirement.

  • Resolution Action:
    • Select None if the customer cannot resolve themselves.
    • Select Attachment if a customer can upload a document to resolve (upload student info to be validated by staff). See Attachments and Validation settings

  • Enforcement
    • Warn will display a message but will not stop them from proceeding, however Prevent will stop them from proceeding.
      • Requiring an attachment? Use PREVENT customer to require that they add an attachment as part of their sign up process.  They must submit an attachment when signing up online. On a kiosk, it will not force an upload. It is best practice to use an Email Automation to trigger a reminder for missing attachment a few days after sign up.

    • Configure your staff facing and customer facing language here.
      • Staff Facing language is displayed in the alert on the contract AND in the check in screen messaging.
      • Customer facing language is displayed at sign up with where they upload the attachment

 

Assign a Customer Requirement to an Enrollment Type

In Build  > Plans > Manage Plans ‘Enrollment Types’ (Tab) > Create/Edit an Enrollment Type > Enable Customer Requirement (Toggle) > Define Requirement (Dropdown)



Assign a Customer Requirement to a Promo Code

Customer Requirements can be assigned to a Contract Promotion code. Customer segments alone can be used on Product Promotions.

For Contract Promotions, assign the requirement on the Customer Restrictions tab of Promotions.  Note that you will also see a segment can be applied on this tab in addition to the customer requirement.

If customer requirement asks for an attachment, leave the customer segment blank and only assign the requirement.  

If the customer requirement does NOT as for an attachment, add the segment to ensure that the promo code will not work if they don't meet the segment.  If the segment is not assigned in addition to the requirement, the promo code will still work, and they will alert after the fact.

See Promo Codes for more info

 

Alert on check-in for invalid customer requirements.

Add Check-in Guard to optionally alert for contracts with invalid requirements when checking-in.

  • Check-in Rule can be found in the list of check-in rules defined as: ‘Customer_Requirement_Rule.’ 
  • When added, it will alert on check-in for all contract holders and enrollees on a contract that has any missing customer requirements for that plan.

In Manage Menu > Organization & Facility Settings > Check-in Guards (dropdown) > Add Check-in Rule > Customer_Requirement_Rule



Adding Attachment to the Contract/Customer

See Attachments and pending validation for customer and staff views/workflows HERE

 

View/Manage Contracts with Invalid Customer Requirements

Go to Manage > Contracts > Invalid Contracts

There are two tabs here: Invalid Enrollments and Invalid Contract promotions where you can view everything that doesn't match an applied customer requirement.

 

Invalid Enrollment Types

Invalid Enrollment types do not change in their dues rate automatically.  They can either be:

  • moved to a new enrollment type (individually as need or in "batches" using customer segments), which will put them at a new dues rate
  • terminated (individually or in batches)
  • left as is.

Move an Invalid Enrollment to a Different Enrollment Type

On the individual Contract, Click Edit Membership/Edit Booking, go to Customer tab, remove from enrollment type, add to another (remove, then find in search under the Recent on Workstation tab)
_____

To do in bulk

1. Go to Manage > Contracts > Bulk Recurring Changes > Enrollment Type Changes

  • In the Enrollment Selector, Pick the plan, facilities, and enrollment type to/from and click Generate to view who that would change. No changes will be made at this step.

  • Once generated, you can review the list. Check the box at left to INCLUDE that enrollment in the change
  • Click to Add Enrollments to the change queue, then view them on the Change Queue tab
    • Here you can review the total impacts in counts and $ values.
    • Ensure you want to make the change and click Execute. THERE IS NO UNDO!

2. (Optional) Create a Customer Segment to use in the bulk change

If you want to limit the enrollment type change to just certain customers, you can do so with a customer segment.  Make the segment to capture the people you WANT to bulk change and use that in the filter above.

For example, create a segment that m
atches all of the following:

    • Use the Contracts/Enrollments condition in the Customer Activity tab. This will exclude people who started a membership in the last 30 days so you can give them a grace period before changing.
      • Set to DOES NOT match the following
      • Add the Membership plan type,
      • Check the box for Started status,
      • Set relative date to sub 30 days to end of day

    • Add second condition for Attachments in the customer activity tab. This will exclude people from the segment if their attachment expired in the last 30 days to give these folks a grace period as well.
      • Set to DOES NOT MATCH the following.
      • add your Student schedule attachment, expired dates and relative range of sub 30 days - end of day
      • set both conditions to DOES NOT match: this should exclude people

  • Use this segment in the bulk change tool

 

Invalid Contract promos

There is no bulk edit to remove promo codes.  If the invalid promo code should be removed, you must Edit Membership and:

  • remove the promo code
  • Review and Accept the Changes to Pricing
  • Optionally invoice prorated dues (toggle off to make change effective next biling without charging prorate)

To see examples of common Customer Requirements in use, check out these here.