Summary
- Introduction
- Plan Limits
- Accessing Project Surveys
- Creating a Setting
- How a Setting Works
- Survey Templates
- Categories
- PSA-Specific Details
- Project Survey Analytics
- When an Integration Stops Working
- Best Practices
-
Introduction
Project Surveys measure how your clients felt about an entire project, not a single ticket. Differently from ticket CSAT, projects run longer, involve more people, and carry more value. Project Surveys give you a read on that bigger picture, such as timeline, budget, communication and team, at the moment the project wraps up.
Crewhu helps you send an automatic survey when a project reaches the status you choose in your PSA, and contacts rate the project on a 1 to 7 scale across up to five categories you define.
Everything lives in a setting: the project status that triggers it, optional conditions that filter which projects it covers, and the survey it sends. Once a setting is active, surveys go out on their own, with no manual follow-up.
Requirements
- Admin role in Crewhu.
- An active integration with ConnectWise, Autotask, or Halo PSA, with the permissions Project Surveys requires.
-
Plan Limits
Project Surveys is available on the Listen, Listen+, Recognize, and Grow plans. What you can configure depends on your plan:
| Plan | Max settings | Available conditions |
|---|---|---|
| Listen / Listen+ | 1 | Project Type |
| Recognize | 3 | Project Type |
| Grow | 8 | All conditions available for your PSA |
The limit counts all settings, active and inactive. Deleted settings don’t count. Which conditions are actually available also depends on your PSA, see PSA-Specific Details below.
Note:
Upgrades apply new limits immediately. Downgrading doesn’t remove or turn off anything; your settings keep their configuration and status, and continue sending surveys. You can still edit, activate, deactivate, and delete them. While you’re above the new limit, you can’t create or duplicate settings.
-
Accessing Project Surveys
To access Project Surveys, first go to Crewhu Pulse. There, click Project Survey in the left sidebar, then click Settings:
If your account has no settings yet, you’ll see a card with a short overview and two options: Create Your First Setting and View Documentation.
Once you have at least one setting, this screen lists every setting you’ve created:
- Name: the setting’s name.
- When: the project status that triggers the survey.
- Conditions: one tag per condition type used (hover to see selected values).
- Actions: the survey the setting sends.
- Status: Active or Inactive, with a selector to change it.
A dash in any column means that part isn’t configured yet. The header also holds Categories, Survey Templates, and Create.
-
Creating a Setting
Click Create in the header (or Create Your First Setting, if this is your first one).
In the Create Setting window, fill in:
- Name: a name that tells your team what the setting does, such as “Closed projects” or “Installation.”
- Integration: the PSA integration this setting uses.
Both fields are required. Click Create.
Important: The integration defines where the statuses, project types, companies, and boards available in the setting come from, and it can’t be changed after the setting is created.
A setting is built from up to three parts: exactly one Trigger (the status that starts it), optional Conditions (what narrows it down), and exactly one Send Survey (what gets sent, and to whom). The canvas opens with the Trigger step already in place. Here’s each part:
Choosing the Trigger
The Trigger step reads “When a project moves to.” Click Select Status and choose the project status that should send the survey. The list comes from your PSA integration; Crewhu doesn’t create statuses of its own.
For example, if you select Closed, the survey is sent when a project moves to Closed in your PSA.
Adding Conditions
Conditions narrow down which projects receive the survey. A setting with no conditions covers every project that reaches the trigger status. Which condition types are available depends on your PSA, see PSA-Specific Details.
Each condition type can be used once per setting. To remove one, open its actions menu and click Delete.
How Conditions Combine
Within a condition, values are alternatives (match any one). Across conditions, all must be met. So adding more values widens a setting, and adding more conditions narrows it.
Example, a setting with Project Type = Installation/Maintenance, and Company = Acme:
| Project that reaches the trigger status | Result |
|---|---|
| Installation project for Acme | Survey sent |
| Maintenance project for Acme | Survey sent |
| Installation project for another company | No survey — Company condition not met |
| Consulting project for Acme | No survey — Project Type condition not met |
Sending the Survey
- Survey: select the template to send, or click Create Survey to make one.
- Send To: who receives the survey. Options depend on your PSA, see PSA-Specific Details.
- Send to inactive or opted-out contacts: unchecked by default.
Saving and Activating a Setting
New settings are always created Inactive. A setting can only be activated once it has a trigger status and a survey to send; conditions are optional. Once the survey is saved, just click on the right menu and select "Active":
To deactivate, change Status to Inactive. This stops new surveys immediately; surveys already sent aren’t affected.
-
How a Setting Works
You’ve now seen the three parts that make up a setting. Once it’s Active, here’s what actually happens behind the scenes, with no manual work from you:
- A project in your PSA moves to the status you picked as the Trigger.
- Crewhu picks up that change the next time it syncs with your PSA (not instant, see PSA-Specific Details for how often this runs).
- Crewhu checks whether the project also matches every Condition you added. With no conditions, every project reaching that status qualifies.
- If it matches, Crewhu sends the survey from Send Survey to that project’s contacts.
That’s the whole loop, no follow-up needed once the setting is active.
Managing Your Settings
-
Rename: click the pencil icon next to the name in the breadcrumb.
-
Duplicate: row menu → Duplicate. Creates an inactive copy.
-
Delete: row menu → Delete. Permanent, but doesn’t affect surveys already sent.
-
Bulk actions: select settings via checkboxes to activate, deactivate, or delete several at once.
-
Survey Templates
A survey template holds everything your customer sees: the email, the survey page, and the thank-you page. Templates belong to your Project Survey, not a single setting, editing one updates every setting that uses it.
To review all your Survey Templates, go to Project Survey > Settings and click on Survey Templates on the header:
Creating a Template
Click Create Survey, name it, and the editor opens with ready-to-use content you can edit freely.
Editing a Template
In the Survey Templates window, click Edit next to a template.
The editor has three sections:
- Email: the invitation email, including the subject, the message and the rating question;
- Survey Page: the page where customers rate the categories and leave a comment. Use Categories Color to set the color of the categories;
- Thank You: the page shown after the customer submits the survey.
You can also rename the template in the name field at the top. Click Save to save your changes. A template can't have an empty name.
Deleting a Template
A delete icon appears next to Edit only for templates that no setting uses. Click it and confirm in the Remove Template window. Deleting a template is permanent and doesn't affect surveys already sent.
To stop using a template in a setting, select another survey in the Send Survey step.
-
Categories
Categories are the topics your customers rate, like Timeline, Budget, Communication, or Team. Manage them by clicking Categories in the Settings header.
Categories belong to your account, not to a setting, and stay available to your surveys when you create or delete settings.
What Your Customers See
- The email: asks for a rating on a 1–7 scale right in the message.
- The survey page: opens with that score applied, shows all category questions plus an optional comment field.
- The thank-you page: its message adapts to the rating.
Incomplete Responses
If someone clicks a rating but doesn’t finish the survey page, Crewhu closes the response within two hours. The overall rating is kept; category answers stay blank.
-
PSA-Specific Details
Most of Project Surveys works the same for every PSA. What changes is how each PSA organizes its projects, which affects the conditions you can use and who receives the survey, along with the trigger statuses, the required permissions and data sync.
| ConnectWise | Autotask | Halo PSA | |
|---|---|---|---|
| Conditions | Project Type, Company, Project Board | Project Type, Company | Project Type, Company, Team |
| Send To | All contacts, or Project contact only | Primary contact | End-user |
| Send to inactive/opted-out | Available | Available | Available |
ConnectWise
Grant the permissions in the Project Surveys group, detailed at ConnectWise Permissions. Data syncs hourly, so a survey can take up to an hour to send after a status change.
- Conditions: Project Type uses the ConnectWise project type, Company uses the project’s company, and Project Board uses the ConnectWise project board.
- Send To: choose All contacts on the project (everyone listed in the project’s Contacts tab) or Project contact only (the single contact set in the project’s Contact field).
- Contact status: whether a contact is inactive or opted out comes from the contact data synced from ConnectWise.
Tip
Filter by Company or Project Board when different delivery teams or customer groups need a different survey.
Autotask
Grant the permissions in the Project Surveys group, detailed at AutoTask Integration Permissions.
- Conditions: Project Type uses the Autotask project type, and Company uses the project’s company. Project Board isn’t available for Autotask.
- Send To: always the project’s primary contact, if there isn’t one, no survey sends.
- Contact status: comes from the contact data synced from Autotask. To include a primary contact who’s inactive or opted out, check Send to inactive or opted-out contacts.
Halo PSA
Grant the permissions in the Project Surveys group ([link to Halo PSA Permissions]).
- Conditions: Project Type uses the Halo PSA project type, Company uses the project’s company, and Team uses the team assigned to the project in Halo PSA. Project Board isn’t available for Halo PSA.
- Send To: always the project’s end-user, if there isn’t one, no survey sends.
- Contact status: comes from the contact data synced from Halo PSA. To include an end-user who’s inactive or opted out, check Send to inactive or opted-out contacts.
Tip
If a survey didn’t go out as expected, check the project in your PSA first, its status, type, company/board/team, and contacts are exactly what the setting evaluates.
-
Project Survey Analytics
In Crewhu Pulse, click Project Survey > Analytics. Select the setting you want to analyze and the time frame.
Analytics shows these metrics:
- Surveys sent: total surveys counted as sent;
- Survey conversion: surveys answered divided by surveys sent;
- Projects with surveys: number of projects with at least one survey sent;
- Project conversion: projects with at least one answer divided by projects with surveys.
The metrics follow the rules of the setting you selected.
The Responses table lists each response with its rating, company, feedback and a score for each category.
An exclamation icon in the Rating column marks a survey counted as sent to a contact with no email address. These rows show no rating, feedback or category answers. They only appear when Send to inactive or opted-out contacts is checked. Inactive and opted-out contacts receive the email, so they’re never marked with this icon.
-
When an Integration Stops Working
Project Surveys depends on your PSA integration. If Crewhu loses access to your PSA, active settings using it stop sending surveys:
- A banner at the top of the Settings screen tells you how many active settings are affected.
- The affected setting’s Status column shows Not Running instead of the selector.
The setting stays Active underneath and resumes on its own once access is restored.
Important: Projects that changed status while it was down are not surveyed retroactively.
-
Best Practices
- Start with one broad setting. One setting on your final project status, no conditions, gets feedback flowing right away.
- Use conditions sparingly. Every condition narrows who receives the survey.
- Avoid overlapping settings. A project only gets one survey, from the oldest matching setting.
- Reuse templates across settings. A single edit updates all of them.
- Keep inactive/opted-out contacts excluded by default, so conversion rates reflect who could actually respond.
- Duplicate before changing an active setting, so you can review before activating the copy.
- Watch for the integration banner and fix issues quickly, projects that change status while it’s down aren’t surveyed later.
Comments
0 comments
Please sign in to leave a comment.