Summary
- Introduction
- Add Your Crew in Crewhu
- Create the API User in Autotask
- General Autotask Permissions
- Permissions by Crewhu Product
- Create the Integration on Crewhu
- Resolved Surveys
- Reply Surveys
-
Introduction
The Autotask REST integration lets you run Crewhu surveys straight from your PSA, so your team keeps working in Autotask and the surveys go out on their own. It reads your tickets through an API user, so Crewhu knows who to survey and who to credit, with no manual work.
Setting it up has three parts:
- Create the API user in Autotask;
- Grant the permissions for the Crewhu products you use;
- Connect it in Crewhu.
The same integration also feeds Crewhu Explorer, Trends, contests based on Autotask metrics, and Project Surveys. Each of those needs its own permissions, to be detailed below.
Requirements
- Admin profile in Crewhu (What level am I?)
- Autotask access to create API users and to edit security levels
- The Crewhu integration vendor available in your Autotask instance
-
Add Your Crew in Crewhu
Crewhu matches each survey to an employee using data from Autotask, so your crew needs to exist in Crewhu first. Add them at Settings > Employees > Add, or upload them with a CSV file.
Two fields have to match Autotask exactly:
-
Employee ID: the 8-digit Resource ID from Autotask, found in ADMIN > Resources (users).
- First and Last name: identical to the Resource Name in Autotask. Keep the upper and lower cases and special characters the same, and avoid extra spaces before or after the name.
Email, Position and Profile are filled as usual. See Add your Crew for the full employee setup.
-
Create the API User in Autotask
Crewhu reads Autotask through a dedicated API user. Creating it also generates the credentials you’ll use when making the integration inside Crewhu.
In Autotask, go to ADMIN > Resources (users) > NEW API User and fill in:
- First Name: Crewhu
- Last Name: Bot
- Email address: use the email of the person responsible for the API connection — Autotask sends API warnings to this address.
- Security Level: API User (system)
- Primary Internal Location: select from the drop-down
- Integration Vendor: Crewhu - Customer Satisfaction
Click the buttons to generate the Key and the Password. Keep both saved in a safe place: the Key is your Integrator Username and the Password is your Integrator Password in Crewhu. Then Save & Close.
Note:
The API User (system) security level already includes every permission Crewhu needs, so you can go straight to the last step. Use the permissions section only if you prefer a custom security level with just what Crewhu uses. To learn more about the default level, see System security levels in the Autotask knowledge base, or contact Datto Support.
-
General Autotask Permissions
The permissions in the API user’s security level define which Autotask data Crewhu can read or update, and each Crewhu product needs its own set. You don’t need to grant everything: grant only what the products you use require, or all of it if you want every product ready to go. Many permissions are shared, so you only enable each one once.
-
Update the Crewhu Security Level in Autotask
- Go to Admin > Account Settings & Users > Resources/Users (HR) > Security > Security Levels.
- Find the security level used by the Crewhu API user and open it to edit.
- Set the permissions listed below for the products you use. Use the exact levels shown: lower levels such as Mine or My Territories usually make Autotask return no data, without any error.
- Leave every other permission as it is.
- Save the security level. Changes apply right away.
-
All Permissions
This table lists every permission Crewhu can need, with the level each product requires. An “X” means that product doesn’t need the permission. Metrics for Gamification uses the same permissions as Trends.
Items 1 to 7 are read-only. Items 8 to 10 let Crewhu write to Autotask and are needed only for CSAT Writeback & CNV (Legacy).
Keep in mind that some Autotask permissions give more access than Crewhu uses, because Autotask doesn’t offer a narrower option:
- Projects > Client & Internal > View: anyone with View on a project can also edit and delete it in the Autotask UI. Only the Client and Internal rows are needed; leave Proposals and Project Templates at None.
- Resources/Users (HR): unlocks the whole Resources/Users (HR) admin area, not just read access. Autotask has no read-only option, so this is the only way for Crewhu to read resources, availability and holidays. The API user can also change resources through the API.
- Tickets > Edit: only has Yes and No. With Yes, the API user can change any ticket it can see.
- Ticket Notes > Edit: with All, the API user can edit any ticket note, including your technicians’. All is recommended so Crewhu keeps updating its survey notes even if you change the Crewhu API user later.
- Application-Wide (Shared) Features (Full Access): a broad Admin checkbox. Per Autotask’s documentation it also gives access to System Settings, User-Defined Fields, Logos, Local Terms & Symbols, Note Types, Downloads and Site Usage.
-
Permissions by Crewhu Product
CSAT Writeback and Conversion Rate Report (Legacy)
Those permissions let Crewhu write the survey rating and notes to Autotask tickets and feed the CNV report. Crewhu also creates the Rating and Previous Rating user-defined fields on your tickets when they don’t exist.
- Service Desk > Tickets > View: All
- CRM > Account & Contact Access > Customer & Cancelation: All
- CRM > Account & Contact Access > Prospects, Leads, & Dead: All
- CRM > Account & Contact Access > Vendor & Partners: All
- Service Desk > Other Permissions > Can view non-billable time entries: Checked
- Service Desk > Tickets > Edit: Yes
- Service Desk > Ticket Notes > Edit: All
- Admin > Feature Access > Application-Wide (Shared) Features (Full Access): Checked
Keep Application-Wide (Shared) Features checked for as long as you use the writeback. Crewhu needs it every time it checks the Rating and Previous Rating fields, not only when you turn the writeback on.
-
Metrics for Gamification
These permissions let Crewhu use Autotask metrics to run contests. Contests use the same metrics as Trends, so the permissions are the same as the Trends group below.
-
Trends
These permissions let Crewhu read ticket, SLA, time entry and resource data, including resource availability and holidays, to build Trends reports.
- Service Desk > Tickets > View: All
- Service Desk > Other Permissions > Can view non-billable time entries: Checked
- Admin > Feature Access > Resources/Users (HR): Checked
-
Explorer
With these, Crewhu can read your tickets, their companies and contacts, and match them with CSAT surveys in Crewhu Explorer.
- Service Desk > Tickets > View: All
- CRM > Account & Contact Access > Customer & Cancelation: All
- CRM > Account & Contact Access > Prospects, Leads, & Dead: All
- CRM > Account & Contact Access > Vendor & Partners: All
-
Project Surveys
With these, Crewhu can read your Client and Internal projects, along with their companies and contacts, and send Project Surveys to the right contacts. Crewhu only reads project data; it doesn’t change your projects.
- CRM > Account & Contact Access > Customer & Cancelation: All
- CRM > Account & Contact Access > Prospects, Leads, & Dead: All
- CRM > Account & Contact Access > Vendor & Partners: All
- Projects > Permission Per Project Type > Client & Internal > View: All
-
Create the Integration on Crewhu
Go to Settings > CSAT Survey. In Integration Partner, select your Autotask integration if it already exists. If it doesn’t, click Create Integration.
In the Setup Integration window:
- Type: Autotask (REST)
- Name: something that makes clear what these credentials are for, you can store as many as you need
- Integrator Username: the Key generated in the first step
- Integrator Password: the Password generated in the first step
Click Test Integration, then save. When testing, Crewhu checks the API user’s security level and shows the result grouped by product: if a group you need is incomplete, adjust the security level in Autotask and test again.
Each group shows how many of its permissions are granted and a check mark next to each one in place. A product works only when its whole group is granted. If you don’t use a product, ignore its group.
When it succeeds, close the window and select the new integration in Integration Partner.
-
Set Up Your Survey
Still in Settings > CSAT Survey, check the following options:
- Logo: brands your 1-click survey. Use any size that respects the aspect ratio of 342px × 216px or larger.
-
Rating Type: select and customize your rating labels. See Custom Survey Faces.
- Survey Language: select from the drop-down.
- Unknown Label: how Crewhu names surveys that weren’t matched to an employee. See Employee marked as UNKNOWN.
- IP Restriction: blocks an IP from answering surveys, for example your office network. Don’t use it if you want to track surveys on internal tickets.
- Show employee picture: highly recommended. Shows the photo from the employee’s Crewhu record in the survey.
-
Mark as Reviewed Automatically: Always, When no Comments, or Never. Use it to automate your closed-loop process per rating.
-
Notifications: choose when each rating triggers a notification (Always, Only with comment, Never) and who gets notified.
- CSAT widget: makes your satisfaction score public. Add the widget HTML to your website or email signature.
Best practices:
Activate the CSAT widget 30-60 days after launching the Crewhu platform, so you are highlighting a good sample of survey feedback. For the notifications, start with Always for all ratings and add filters later, and let your employees receive notifications too.
Write Survey Back
Check Write Survey Back and Crewhu sends back to the Autotask ticket:
- the two most recent survey ratings;
- the survey feedback, as an internal note;
- Survey Notes.
Writeback needs the permissions in the CSAT Writeback & CNV (Legacy) group. Without them, Crewhu can’t create or update the Rating fields on your tickets.
To show the ratings on the ticket, create a section for them in Autotask:
- Go to ADMIN > Features and Settings > SERVICE DESK (TICKETS) > Ticket Categories and edit a category.
- On the Details tab, click New Section and name it; in the example below, Crewhu Ratings in position 4.
- Under Hidden Fields, find Rating (UDF) and Previous Rating (UDF) and drag them into the new section.
- Repeat for each ticket category you use.
Important:
The UDF fields can take up to 24h to appear after the integration is set.
This is how the ratings look on the ticket:
-
Resolved Surveys
Send the survey when a ticket is resolved. In Settings > CSAT Survey, turn on and configure your Survey Types, then press the View/Copy button. See Setup Resolved Reply Signature Surveys for more details.
The drop-down has two formats:
-
Image Snippet shows 3 faces.
-
Text only snippet won’t be blocked by an image filter.
Best practice:
The more popular option is the faces because they are more engaging. You can A/B test. Try the image snippet for one month and then try the text-only snippet for one month and see which option yields the best results.
After deciding which one to use, click on Copy to Clipboard:
-
Create the Notification Template in Autotask
- Go to Admin > Automation > Email Notifications & Surveys > Notification Templates.
- On the Service Desk tab, click New.
- Paste in a template following your company style, then switch to the HTML (source code) view.
- Paste the Crewhu snippet where you want the faces to appear. The middle of the email converts best.
- Switch back to Design view, adjust the layout, and click Save & Close.
Note:
For a template in another language, paste the English snippet and save, reopen it in edit mode so the placeholders convert automatically, then save again.
Create the workflow rule. Go to Automation > Workflow Rules to set when and to whom the email goes out.
On the General tab:
- Name the workflow rule.
- Check Edited by and select Anyone.
- Build the condition Status - Equal to - Complete.
- Select the queues that should send the email when a ticket is closed.
On the Notification tab:
- Check Ticket Contact.
- Choose the sender address.
- Select the template you created with the Crewhu snippet.
- Create a test ticket and you’re ready to roll.
Note:
The data will show "&" symbols. This is not an error but just part of the test data. Once you see that the data populates, you can go live.
-
Reply Surveys
Reply surveys let customers rate while the ticket is still open, from the emails your team sends during the conversation.
- In Crewhu, go to Settings > CSAT Survey and scroll to the Reply Survey section to copy the snippet.
- In Autotask, go to Admin > Automation > Email Notifications & Surveys > Notification Templates.
- On the Service Desk tab, find the template you want and click edit.
- Paste the snippet into the HTML section of the email body, then check the Design tab to confirm the layout.
- Repeat for each template that should carry a survey.
Comments
1 comment
Hi Jay, I'm having a problem authenticating my connection. How can I generate the Integration code in Autotask? Thanks!
Please sign in to leave a comment.