This process is designed to move calls from e-automate to ConnectWise to be worked; when the service call in e-automate is assigned to a specified technician, the sync will create a service ticket in ConnectWise. Use ID965 to sync the closed ticket from ConnectWise back to e-automate.
This process will take pending service calls from e-automate that are assigned to a specified "dummy" technician and create service tickets in ConnectWise. The service call in e-automate will be updated with the ConnectWise ticket number in the call description field and will be placed on hold while the ticket is being worked in ConnectWise. As the ticket is worked in ConnectWise, call notes are added to the e-automate call when the status of the ticket in ConnectWise changes or a note is added to the ticket. When the call is closed in ConnectWise, you can use ID965 to add the time entries from ConnectWise to the original call in e-automate. If you do not use ID965, you will need to manually release the call in e-automate from hold and close the call.
You will need to be subscribed to ID747 (ConnectWise Customer Sync) for the customer mapping as that is required for this integration to work. In addition, you will need to be subscribed to ID965 to update the call in e-automate when the ticket is closed in ConnectWise. The ID964 agreement sync is not required but is highly recommended, as it removes manual work in assigning agreements to the tickets created in ConnectWise.
Run Schedule: Every 15 minutes
Type of Output: Sync
* * *
e-automate Service Call
1. Technician - call is set to technician indicated in variable W. Details on creating the technician record here.
2. The call in e-automate will be placed on hold once it has been created in ConnectWise. You specify the on-hold code to use in Variable 8. More information on on-hold codes here.
3. Once the ticket has been created in ConnectWise, the call in e-automate will have the call description updated with the ticket number from ConnectWise.
ConnectWise Service Ticket
Red shaded areas - pulled from eAutomate service call
1. Summary - The first 100 characters of the problem description will be entered into the summary field.
2. Company - The company will be the matching customer from e-automate.
3. Site - The site will show as Main when the location in e-automate matches the parent customer. If the location on the service call in e-automate is a child location, the linked site for that child location will be used.
4. Contact information - The contact name, phone, and email will be updated, provided that information is included on the ticket in e-automate.
5. Agreement - If you are using the ID964 agreement sync, and the contract used on the service call in e-automate has a linked agreement in ConnectWise, that agreement will be used. Otherwise, the agreement field will be blank and you will need to assign an agreement manually to the ticket.
Yellow shaded areas - set in ID912 defaults
6. Board - The board is set in Variable 1.
7. Status - The status is set in Variable 2.
8. Type - The type is set in Variable 7.
9. Impact/Urgency - The impact and urgency are set in variables 4 and 5.
10. Priority - The priority on the ticket is set in variable 6.
**The sync does not assign a member to the ticket in ConnectWise**
When the ticket is created in ConnectWise, the sync will add an internal note (1) with the call number, call type, and caller information from e-automate:
The full problem description from the call in e-automate is also added as a discussion/external note.
As the ticket is worked in ConnectWise, the call notes will be updated in e-automate:
1. When the status of the ticket changes in ConnectWise.
2. When the ticket is created in ConnectWise, an internal note is added with the call details.
3. When notes are added to the ticket in ConnectWise.
The email notification lists calls created on the last sync and any calls that are still pending sync due to errors.
See here for details on potential errors.
* * *
Variable 1: Board - The name of the service board in ConnectWise that the ticket will be created on. Details on how to find the ConnectWise boards here. **Required by the ConnectWise API to create a new ticket.
Variable 2: Status Name - The status from ConnectWise that the newly created ticket will use. Details on where to find the ConnectWise statuses here. **Required by the ConnectWise API to create a new ticket.
Variable 4: Impact - The assigned impact on the newly created ticket in ConnectWise. Options are Low, Medium or High. More details on the ConnectWise impact settings here. **Required by the ConnectWise API to create a new ticket.
Variable 5: Severity - The assigned severity on the newly created ticket in ConnectWise, options are Low, Medium or High. More details on the ConnectWise severity settings here. **Required by the ConnectWise API to create a new ticket.
Variable 6: Priority - The assigned priority on the newly created ticket in ConnectWise. Details on where to find the ConnectWise priority list here. **Required by the ConnectWise API to create a new ticket
Variable 7: Ticket Type - The ticket type from ConnectWise to be used on the newly created ticket. Details on where to find the ConnectWise ticket types here. **Required by the ConnectWise API to create a new ticket
Variable W: EA Dummy Technician - Technician to use in e-automate to indicate that the service call should be created in ConnectWise. Enter the employee number from e-automate. Only to be used with the ConnectWise integration, not a technician assigned calls for any other purpose. Details on how to create this technician here. **Required.
Variable 8: OnHold Code for EA Call - On Hold code from e-automate to be used to place service call on hold once ticket has been created in ConnectWise. Details on creating an on hold code here. **Required
Variable 9: NoteType - Note type from e-automate to use for notes added based on ConnectWise ticket status changes and notes added. See details on note types here.
* * *
1. Create the "dummy" technician that will be used as the trigger to create calls in ConnectWise. See here for instructions on how to create the technician. This technician should only be assigned to tickets that should sync to ConnectWise. You'll add the number for the technician into variable W.
2. Determine an on-hold code to be set on the call while it is being worked in ConnectWise. See here for notes on creating on-hold codes. The on-hold code will go in variable 8.
1. Determine the board to use in ConnectWise, all tickets created by ID912 will be added to this board. See more details on boards here.
2. All tickets created by the sync will have the same ticket status, see details here on where to find the ticket statuses on the board the sync will create the tickets on.
3. The priority of the tickets created in ConnectWise will be the priority specified in variable 6. See details on the priorities in ConnectWise here.
4. The ticket impact and severity are both settings that you set in the variable settings, all tickets created by the sync will have the same impact and severity. See more details on these options in ConnectWise here.
5. All tickets created by the sync will have the same initial ticket type. See details here on how to find the ticket type in ConnectWise.
Subscribe to Alerts
1. Once you have the settings in ConnectWise and e-automate determined, subscribe ID912 on our website. If you don't have a login to our subscription site, you can email firstname.lastname@example.org to have us set you up with a login.
3. ID965 is not required for ID912, but if you want to "close the loop" and update the service call in e-automate with the time entries from the linked call in ConnectWise, you'll need to subscribe to ID965. Additionally, once the ticket is closed in ConnectWise, ID965 will release the call from hold in e-automate and move it to the Ok to Invoice status.
Next, you’ll need to determine which testing option to use. Regardless of which option you chose, you'll need to provide a list of companies from ConnectWise to test with. These should be companies that DO NOT have automatic emails set up to send when a new ticket is created in ConnectWise.
**If you have ID965 currently running in production, the option that you chose for testing will affect how you can test using ID965 to bring the time entries from the completed ticket back into e-automate**
Option 1: Move calls from a test e-automate database to a test ConnectWise database.
Having a test ConnectWise database is not always an option, but going from a test eAutomate to a test ConnectWise is the cleanest test of the sync that won't affect your production data. If you have ID965 running in production, using a test ConnectWise database is the only option that allows a clone of ID965 to run in test mode and push the completed time entries from ConnectWise back to the service call in e-automate on the regular automated schedule.
Option 2: Move calls from a test e-automate database to the production ConnectWise database.
Using a test e-automate database to create the calls to move to ConnectWise allows for the creation of service calls without the worry of the test calls getting mistaken for “real” service calls in e-automate. These test tickets will be pushed to production ConnectWise, we would recommend using the XYZ Test Company in ConnectWise for testing. Once testing is done, you'll need to delete the test tickets from ConnectWise. If you are running ID965 in production and chose this option, CEOJuice will have to manually trigger ID965 to push just the test calls from ID912 to the test e-automate database.
Option 3: Move calls from the production e-automate database to the production ConnectWise database.
If you would like to, you can do your testing from your production e-automate database to the production ConnectWise database. This option requires the most care to ensure tickets and invoices do not get accidentally sent to your customers!! In addition to carefully selecting your customers to test with, you need to be cautious of not invoicing the service calls in e-automate. If you are running ID965 in production, setting the test ConnectWise tickets to the status to sync will "close the loop" and bring the time entries from ConnectWise back to e-automate. You must take extreme care to ensure that these tickets do not send invoices out to your customers!! Once testing is complete, you'll need to delete the test tickets from ConnectWise and cancel the test calls in e-automate.
Depending on the testing option chosen, you’ll need to set up one or more of the following:
1. API Keys in ConnectWise – required for all options, these may already be in place if you are using other portions of the ConnectWise sync. New keys do not need to be created. If you are going to use a test ConnectWise database, you’ll need to create a set of API keys for that database. Details on creating API keys here.
2. ConnectWise test Database – required for option one. If using a test ConnectWise database, you’ll need to create a set of API keys for that database.
3. e-automate test Database – required for options one and two. See this link for notes on creating a test e-automate database.
4. CEOJuice test database – required for options one and two. See this link for notes on creating a test CEOJuice database.
Once these setup steps have been completed, please let us know and we will install the process for testing.
To test the functionality of ID912, follow these steps:
1. Create one service call in e-automate under one of the specified test customers and assign the "dummy" technician specified in variable 1.
The test customer used is extremely important...you need to make sure that the mapped company in ConnectWise is not set to automatically email the user of a new service ticket entered and cause confusion.
2. Verify that the ticket is created in ConnectWise, within 15 minutes of assigning the call in e-automate to the "dummy" technician.
3. Check that the call in e-automate has been updated to show the ConnectWise ticket number in the description field and placed on hold with the on-hold code from variable 8.
4. Change the status of the ticket in ConnectWise, within 15 minutes, the call notes in e-automate should update with the status change from ConnectWise.
If you are running ID965 in production and testing calls in the production ConnectWise database, it's VERY important that you do not change the test ticket to the status that is used to sync calls to your production eAutomate.
5. Add both internal and external discussion notes to the tickets in ConnectWise and verify that within 15 minutes a new call note is added to the service call in e-automate.
6. Test a couple of tickets moving from e-automate to ConnectWise to verify how the process works.
Once you have finished your testing, let us know and we can move the sync to production for you.
Prior to moving to production, you must delete all test tickets from ConnectWise to ensure none of those tickets gets imported into the production e-automate!!
In e-automate, calls that should be moved to ConnectWise are assigned to a "dummy tech" (variable W) to indicate the call should be created in ConnectWise. A new ticket will be created on the specified ConnectWise service board (variable 1) with the specified status (variable 2). The priority, impact, and severity from the alert variables will be used on each ticket created.
To have the time entries from the ticket in ConnectWise sync back to e-automate, you need to be subscribed to ID965. Once the call is completed in ConnectWise, the time entries will be added as labor records on the original call. The call will then be removed from on hold and be set to Ok to Invoice.
All tickets created by the sync will post to the service board specified in variable 1. You can see the list of boards in ConnectWise by going to the setup tables - service boards:
Choose one board to be used for all calls created by ID912.
All tickets created by the sync will have the same initial status. Status is found in ConnectWise by going to the specific service board and clicking on the Statuses tab. Go to the setup tables - Service board and select the correct board. Then click on the Statuses tab:
Choose one status to use for all tickets created.
ConnectWise Ticket Priority
Priorities in ConnectWise are used on Service Level Agreements (SLAs) to determine the impact/urgency and priority of a service ticket. Priorities can be found in the setup tables, under Service:
Choose one priority to be used on all tickets created by the sync.
ConnectWise Ticket Severity/Impact
Severity and Impact each have three different options: Low, Medium, and High. You can view these designations in the setup tables, under Severity:
You will enter either Low, Medium or High for the Severity and either Low, Medium or High for the Impact. The values will be used for all calls created by ID912.
ConnectWise Ticket Type
Each ticket created by the sync will have the same ticket type used. The ticket types are specific to each service board. To find the list, go to the setup tables and open the specific service board where the tickets will be created. Then click on the Types tab:
Select one type from the list to be used for all tickets created by ID912.
e-automate Dummy Technician
A new technician will need to be created in e-automate for this process. This "dummy" technician will be used to trigger the sync to create a ticket in ConnectWise. To create the technician in e-automate, go to the People menu and select Employees/Contractors. Then click on New to create a new employee:
The value entered in the Number field (CWTech in this example) is the value to enter into the variable on the alert. This employee will also have to be set as a technician, click on the Positions tab and check the box for Technician. When the technician box is selected, you will also need to set a territory, delivery method, warehouse, and bin:
While the ticket is being worked in ConnectWise, the call in e-automate will be placed on hold. We'd recommend creating a new status in eAutomate that would indicate that the call is being worked in e-automate:
1. The On hold code will be what is entered into variable 8.
2. Check the box for service so that the code is available to be used on service calls.
3. Check the box to Calculate response time using release date and time so that the time on hold while the call is worked in ConnectWise won't be included in response time.
As the ticket in ConnectWise is worked, specific activities can post back to e-automate as a note added to the service call. The status of the ticket changing and notes being added to the ticket will both trigger notes to be added to the service call in e-automate.
To create a new note type to use for this, in e-automate, go to the Tools menu and Lists and Codes - Note Types:
Enter the note type in Variable 9 on the alert.
To see the notes on the service ticket in e-automate, right click on the call and choose the Call Notes option:
Notes are added when:
1. The call status changes.
2. An internal note is added.
3. A discussion/external note is added.
Calls that fail to import into ConnectWise will show on an email alert, the main reason a call won't create a ticket is that the customer on the call in eAutomate is not mapped to a company in ConnectWise. When you get an error report for a call, check these things:
1. The company RecID from ConnectWise is populated in the custom property ZCJ_CW_CompanyID on the e-automate customer record. See details here on how to link customers between the two systems.
2. If the service call in e-automate has a location set that is not the parent location, verify that the location customer is mapped to a site in ConnectWise. Details here on how to map sites to locations.
3. Verify that the variable settings for the ConnectWise values are all valid: Board name, status, ticket type, priority, severity, and impact.
If all of the above are set correctly, please email email@example.com with the service call number from eAutomate that won't sync.
This alert can be cloned, which means creating multiple subscriptions of the same ID# (ID912). This function will ONLY work if at least ONE of the variables on each subscription is different. Just select + sign to create multiple subscriptions.
See this link for an overview of cloning features.
* * *
Best Practices & Tips
Best Practices & Tips
The ID965 service sync is not required to be running, but we do recommend that you have this sync running to close the loop and bring the finished work from ConnectWise back to e-automate. Without running ID965, you will need to manually release the call from hold in e-automate and close it once the work is done in ConnectWise.
The ID964 agreement sync is not required to be running, but if you would like to have the tickets in ConnectWise linked to an agreement, you will need to have ID964 running and use the linked contract for the agreement on the e-automate service call.
* * *
ID747 - ConnectWise Customer Sync
ID964 - ConnectWise Agreement Sync
ID965 - ConnectWise Service Call Sync
* * *