Since you're already running Claude and have Make experience, the custom build is the right call. Here's why: there's no native Claude integration for Jobber that handles scheduling logic and business analysis at the same time, and any app that claims to do it all natively is going to hit a ceiling fast when your logic gets specific to your operation.
The pattern that works is using Jobber's webhook triggers to push job and client data into Make, then passing that payload to Claude via API with a prompt that includes the relevant context. Claude handles the reasoning layer, Make handles the routing, and Jobber stays your source of truth.
For client communications specifically, the key is building the prompt around the job data fields Jobber sends in the webhook, things like service type, client history, job status, so Claude's output is actually personalized and not generic.
GHL is worth having for the CRM and follow-up funnel side, but I'd keep it downstream of Jobber rather than trying to make it the integration hub. The Jobber to Make to Claude path is cleaner for the ops logic you're describing.
What triggers are you planning to build around first?
