Prokeep SMS Integration Setup Instructions

The Innovo Delivery Notification Trigger integration was built by Innovo and Epicor. The setup is quick and easy and takes place within those systems.

Before Getting Started:

• Work with your Epicor Eclipse rep to enable the “Prokeep SMS” trigger in your account
• Ensure you are on the Eclipse version released in May 2022 or later (22.1; 9.2.1.0) with Solar Eclipse APIs enabled. 
• Additionally, coordinate with your Innovo rep to ensure your API version is at least 1.9.16

Once you have completed the following steps you are ready to proceed with setting up your integration. 

Note: All Prokeep accounts must be  Prokeep Plus to utilize the Messaging API.

In Prokeep: 

1. Navigate to Settings > API > Generate Application. 
2. Name the application “Innovo Delivery Notifications” or something similar.  
3. Click “Generate Credentials.” 
4. Store the Credentials somewhere you can access them later like a notepad. 
5. Click “Confirm"

In Eclipse:  

1. Verify you are on the updated version of the May 2022 release or later.  
2. If you’ve not done so already, work with your Epicor rep to enable the Prokeep SMS Trigger on your account. 
3. Navigate to System> System Programming > Add On Products> API Maintenance> API  Configurations. Select “Prokeep Service”. Click on the “Global Settings” Tab.  
4. Input your Prokeep URL into the “URL” field under “Connection Settings”. For example https://testcompany.prokeep.com
5. Copy and paste the credentials from Prokeep to the Username and Password fields in Global  Settings.  
6. Click Create Trigger Activity

7. Under Branch Settings, set up the numbers that each branch will be texting from. You can ask your Prokeep CSM for a list of Group Phone Numbers if you need clarification on which groups use which numbers.  

In Innovo:  

1. Contact Innovo Support: After completing the Eclipse configuration, reach out to the Innovo Support team via email at support@goinnovo.com. Inform them of your intention to enable Prokeep for SMS text notifications. They will assist you in transitioning to Prokeep for handling SMS notifications and ensure your Innovo account is seamlessly integrated with Prokeep's messaging capabilities.
2. Setting up Triggers: Once your Innovo account has been switched to work with Prokeep for SMS messages, you can work with your Innovo rep to determine the best activity triggers to setup for your use case. 

Most of our customers are using the following triggers: 

• Out for Delivery - The Out for Delivery notification is sent for all enabled stops when the driver breaks a 0.2-mile geofence from the originating branch and the manifest has been started.
• Next Stop - The Next Stop notification is sent when the previous stop or break has been completed.
• X Minutes Away - The X Minutes Away notification is sent when the driver is X minutes from the delivery address (may or may not be the next stop). This notification will only be sent once, so if the driver is delayed after the notification is sent it will not be sent again, when the driver is X minutes away.
• Delivered - The Delivered notification is sent when the driver completes the stop.

1. Integration Testing: After enabling Prokeep for SMS notifications, collaborate with Innovo's support team to conduct thorough testing. This testing phase ensures that notifications are sent accurately and promptly, providing a seamless experience for your users.

Note: 

• Outbound text messages sent programmatically via our API will be billed on a monthly basis, at $0.01 per SMS and $0.03 per MMS. Customers are currently charged for Twilio, so this would be either no change or nominal. Customers with API usage are required to provide an electronic payment method to account for monthly API messaging payments.
• All messages related to orders will be appended with the Order ID to provide context to the contact. 
• An error will occur if a contact does not have a valid mobile number on their contact record.