Utilization period:
Utilization by Consultant
Weekly Trend
Projects by PM
Remaining SOW Hours
Loading...
Week of Feb 9
| Consultant | Available (h) | PTO (h) | Effective (h) | Billable by Project | Utilization | Notes |
|---|
| Consultant | Available (h) | PTO (h) | Effective (h) | Billable by Project | Utilization | Notes |
|---|
| Project Manager | Available (h) | PTO (h) | Effective (h) | Hours by Project | Utilization | Notes |
|---|
PTO Entries
Pending FreshBooks Time Entries
FreshBooks vs System — Gap Report
Click the Gap Report tab to load data
📌 How it works: Enter hours per project for each team member weekly. Billable hours are calculated automatically as the sum of project hours.
On save, project budgets and SOW breakdowns are recalculated — consultant hours update Functional/Technical SOW categories, PM hours update the Project Management SOW category.
Utilization = Billable ÷ (Available − PTO). Green ≥ 90% ·
Yellow 70–89% · Red < 70%.
To Do0
In Progress0
In Review0
Complete0
Schedule Overview
Read-only view of consultant allocations from Capacity planning
Loading schedule...
Manage Consultants
Add New Consultant
?
JPG, PNG, GIF, or WebP · Max 5MB
Manage Projects
Add New Project
SOW Budget by Role
Role Category
Hours
Rate ($/hr)
Functional Consultant
Technical Consultant
Project Management
Other
Total Budget: 0h
Total Value: $0
Manage Companies
Add New Company
Manage Project Phases
My Profile
Manage Users
Role Permissions
Configure what each role can see and do
FreshBooks Integration
Loading...
💡 What-If: Simulate New Sales
Confirmed
Tentative
Today
Team Utilization Forecast
Available Hours by Week
Support Hours by Company
Recent Tickets
Weekly Support Hours Trend
Top Consultants (Support)
Support Tickets
Support Hours by Company
Zapier Integration
Connect your Slack support channel to the dashboard using Zapier's free plan. Tickets auto-create when new messages arrive.
Your Webhook URL
Setup Instructions
1Create a Zapier account — Go to zapier.com and sign up for a free account (100 tasks/month included)
2Create a new Zap — Click "Create" → "Zaps" → "New Zap"
3Set the Trigger
App: Slack
Event: "New Message Posted to Channel"
Channel: Select your support channel
Connect your Slack account when prompted, then test to pull a sample message.
4Set the Action
App: Webhooks by Zapier
Event: "POST"
URL: Paste your webhook URL from above
Payload Type: JSON
Data: Map the fields below ↓
5Map the Data Fields
In the Zapier "Data" section, add these key-value pairs. For each value, click the "+" to insert the Slack message data.
| Key | Zapier Value |
|---|---|
| description | Message Text (from Slack trigger) |
That's the only required field! The webhook will auto-parse client name, email, company, and support plan from the message text. If your bot posts structured messages (like "Client: Acme Corp"), those fields get extracted automatically.
6Test & Publish — Click "Test" to send a sample ticket, verify it appears in the Tickets tab, then click "Publish" to go live
Optional: Map Individual Fields
If your bot posts with Slack attachment fields (not just plain text), you can map them individually for better accuracy:
| Key | Description | Required |
|---|---|---|
| client_name | Customer or contact name | Optional |
| Client email address | Optional | |
| company | Company name (auto-matches to dashboard companies) | Optional |
| description | Issue description or full message text | Required |
| support_plan | Customer's support tier | Optional |
| priority | low, medium, high, or urgent | Optional (defaults to medium) |
Test the Webhook
Project
Add Task
Add Note
1:1 Meeting Notes
Goals
Utilization Over Time