CloudLink Ideas Portal

Phase 1

Background

• Modern is a communications technology that we want to utilize to maintain two way communication

• Many of our Dealers already use Modern

• Modern is a basic technology that allows for the massing and management for 2-way communication via TXT between customers and dealers, including photos and attachments

• Since ServiceLink already does email, phone and TXT, sending messages via modern is a good start. Phase 2 is a much larger stage where we will achieve 2-way communication including the management of attachments (photos & video)

• Modern messaging must link their record to the svl ticket/work order

Acceptance Criteria

The following functions will need to be created to integrate with Modern:

1. To push a Work order to Modern the following information will need to be pushed (See payload example attached)

   1. work_order (required) - Object containing all of the relevant work order information

      1. number (required) - The work order number. This is used as a unique identifier with dupe checking.

   2. Message to be communicated

2. Trigger to send one way communications

1. On the Work Order Overview screen, we can . set the default method of communications, which for Modern enabled dealers will feature option for automated communication

2. On the work order, clicking the communication button for manual communications, add an option for Modern enabled dealers to select Modern

3. We will assume that Modern is a black box, and thus will send contact, customer, asset and work order information on every send

4. Need to work with Modern to find out if we send a message to a customer via Modern, if the message automatically relays to the customer

3. Enable Modern with the ability to link their record with a SVL ticket / Work Order

• Need to work with Modern to get a return identifier for the create or relevant work order

*Note: The API is currently structured as:

1. ## ### dashboard_id - (required) Determines which dashboard a work order will open up on.

   1. ### store_id - The store or warehouse number/id. Will be used to filter unwanted work orders.

      1. order_date - When the work order was created in the ERP. Will be used to filter unwanted older work orders. (any parsable format is OK)

   2. advisor - Assigns an advisor to the work order. Though this is optional, it's highly recommended. If you don't pass advisor data, a random admin advisor will be selected.

      1. id - Unique identifier. This can be anything unique and is configurable by the account owner within Modern.

      2. email_address - Email address the advisor uses to log in. This can be used in lieu of the ID.

   3. work_order (required) - Object containing all of the relevant work order information

      1. number (required) - The work order number. This is used as a unique identifier with dupe checking.

      2. overview - A place to put customer complaint or other repair related information that's visible to the asset owner.

      3. internal_overview - Same as the overview, only not visible to the asset owner.

      4. dashboard_indicator - Will select a dashboard indicator if one matches this value. Example of dashboard indicators are Cash, Credit and Warranty.

      5. promise_time - A date time string used to set an estimated time of completion value. The format of this value must be yyyy/mm/dd hh:mm:ss. Example: 2018/12/09 12:33:24

      6. priority - A value of either "0", "1" or "2' that indicates the priority of the work order. 0 being normal priority, 1 being medium priority and 2 being high priority.

      7. dupe_check - Used to turn on or off work order number duplication checks and the statuses checked against.

      8. enabled - This defaults to true. If you don't want to perform any duplication checking on work orders, set this to false.

      9. statuses - This defaults to open, closed, deleted. If you only want to perform duplication checking on open work orders, set this to ["open"].

   4. customer_business - The asset owner company information

      1. id - (required) The unique identifier for the customer business. If an existing customer business for the current dashboard is found with the ID, it will be used. If one cannot be found, it will be created.

      2. name - (required) The name of the customer business.

   5. customer_contact - (required) The asset owner contact informatio

      1. id - (required) The unique identifier for the customer contact. If an existing customer contact for the current dashboard is found with the ID, it will be used. If one cannot be found, it will be created.

      2. first_name - (required) The first name of the customer contact.

      3. last_name - (required) The last name of the customer contact.

      4. mobile_phone - The phone number that updates will will be texted to.

      5. email_address - The email address that updates will be sent to..

   6. asset (required) - Object containing all of the relevant equipment information.

      1. id - (required if serial_number is blank) The unique identifier for the equipment. If an existing equipment record for the current dashboard is found with this ID, it will be used. If one cannot be found, it will be created.

      2. serial_number - (required if ID is blank) The equipment serial number and secondary unique identifier. If an ID is not provided, the serial number will be used as the unique ID.

      3. stock_number - Internal stock number.

      4. description - Equipment description.

      5. year - Equipment year.

      6. make - Equipment make.

      7. model - Equipment model.

      8. hours - Equipment hours.

   7. technician - Assigns a technician to a work order

      1. id - (required) The unique identifier for the technician. If an existing technician record for the current dashboard is found with this ID, it will be used. If one cannot be found, it will be created.

      2. first_name - First name of the technician

      3. last_name - Last name of the technician

   8. department - Assigns a department to a work order

      1. name - (required) Will select a department if one matches this value. Example of departments are Field Service, Component Rebuild, etc.