Adding New Units: Preparation Phase

Prior to obtaining Sprinklr access, units need to complete a memorandum of understanding, or MOU, to agree to payment terms. The unit also needs to provide some basic information to University Communications and Marketing that will be used to build that unit’s workflows in Sprinklr. 
 

MOU Completion

1. University Communications and Marketing issues an MOU to the unit. The purpose of the MOU is to:
   1. confirm the number of Sprinklr seat(s);
   2. quote the amount for the current year;
   3. confirm the annual rate moving forward;
   4. note dates pertaining to account activation and renewal;
   5. document features granted through seat(s) access;
   6. confirm the account information for billing purposes.
2. Unit representative signs and returns the MOU to University Communications and Marketing.
3. University Communications and Marketing countersigns the agreement.
4. One copy goes to the unit for records. Another copy is sent to the University Communications and Marketing budget officer so that the unit can be billed.
5. Update the seat bill tracking spreadsheet, as necessary, and notify budget officer of need to send bill.

Build Reference Data Collection

The account relationship manager then requests initial information from the unit’s Sprinklr principal user to confirm setup needs.

• How should user(s) and account(s) be grouped?
• What accounts/platforms will be used?
• How should account dashboards be structured?
• What Tier 1 and Tier 2 tags are needed?
• What custom fields, if any, are necessary for launch?
• For units with multiple seats, what permission and approval workflow needs are required?
• Account login MSU NetID (one per seat)

Submit Ticket to Create User Seat

1. Account relationship manager confirms Sprinklr seats are available.
2. If none are available, a seat purchase agreement must be initiated with Sprinklr.
3. Once seats are available, the account relationship manager submits a ticket to the platforms group to have the unit’s workflows and the user seat(s) created. 

Documentation updated: Nov. 1, 2024