Charlotte for Jobber
Inbound calls answered by Charlotte; bookings flow into Jobber automatically. OAuth handshake takes 90 seconds.
OAuth callback: /oauth/jobber/callback
Charlotte for Jobber-using HVAC, plumbing, and electrical operators. Every inbound call lands in Charlotte first; non-emergency bookings sync to Jobber as new jobs with the caller's name, phone, address, requested window, and structured notes — no copy-paste, no manual keying. Emergency-classified calls bridge to the operator live in under twenty seconds. The OAuth connection takes about ninety seconds end-to-end and runs through Jobber's standard developer-app authorization flow.
Last updated
What the integration syncs
Booking sync (new-job creation)
When Charlotte books a routine appointment, a new Jobber job is created with the customer's name, phone, address, requested window, the caller's described issue, and any equipment notes — populated in Jobber within seconds of call-end.
Customer sync
If the caller's phone number matches an existing Jobber customer record, the new job attaches to that customer instead of creating a duplicate. Unknown numbers create a new customer record with the call's structured fields.
Job sync (status + visit updates)
Status changes the operator makes inside Jobber (job confirmed, on-the-way, completed) sync back to Charlotte's admin portal so the call-history view reflects job lifecycle without context switching.
Invoice handoff (Pro tier)
Pro-tier operators get post-job invoice handoff: when a job is marked completed in Jobber, Charlotte's review-request SMS fires the next morning. The invoice itself stays in Jobber — Charlotte never touches the billing surface.
Where Charlotte deliberately stops short
Stating limitations out loud is how Charlotte earns credibility on the capability claims that matter — operators have heard enough “does everything” pitches.
Job-time-windows respect Jobber's calendar — no overbooking logic
Charlotte respects whatever calendar windows the operator has configured in Jobber but does not run its own overbooking-detection heuristic on top. If Jobber accepts the booking, Charlotte books it; if Jobber rejects (e.g. window already filled), the call falls back to a structured note and the operator is paged.
Custom field mapping is limited to ~12 standard fields
Charlotte syncs the most common fields (name, phone, address, requested time, symptom notes, equipment model/age, urgency). Custom Jobber fields beyond that set don't auto-populate today — the founder maps tenant-specific custom fields manually during onboarding.
Questions operators ask before they connect
Q1How does the Jobber connection actually work?
Charlotte uses Jobber's standard OAuth 2.0 developer-app flow. The operator clicks Connect Jobber in Charlotte's signup wizard, authorizes the Charlotte app inside Jobber's authorization screen, and Jobber redirects back to Charlotte's OAuth callback with the auth code. Charlotte exchanges the code for refresh + access tokens, stores them encrypted at rest, and refreshes them automatically on the standard Jobber-issued schedule.
Q2What permissions does Charlotte ask Jobber for?
Read and write access to jobs and clients in the connected Jobber account — the minimum scope needed to create new jobs and attach them to existing customers. Charlotte does not request access to financial transactions, payroll, or any Jobber surface unrelated to inbound-call booking. The exact scopes are surfaced inside Jobber's authorization screen for review before connection.
Q3Can I disconnect Charlotte from Jobber without affecting my Jobber data?
Yes. Disconnect from either side — Charlotte's admin portal or Jobber's connected-apps view — at any time. Disconnecting revokes Charlotte's OAuth tokens and stops new job sync immediately. Existing Jobber records created by Charlotte stay in Jobber and remain editable; Charlotte's call-history view continues to show them with a disconnected badge so the operator can see they're no longer round-tripping.
Q4Does Charlotte work with both Jobber Lite and Jobber Pro plans?
Charlotte's OAuth integration works against any Jobber plan that exposes the standard developer API. Both Jobber Core and Jobber Connect plans expose the API; Jobber Lite has limited API surface (Jobber's own documentation). Charlotte's signup wizard detects the connected account's plan tier during the handshake and shows a warning if features will be limited by Jobber's plan rather than Charlotte's.
Q5What happens if Jobber's API is down when Charlotte tries to book a call?
Charlotte books the appointment locally in her call-history view with a sync-pending flag, then retries the Jobber API on a 30-second exponential-backoff schedule for up to fifteen minutes. If sync still fails after the retry window, the operator is paged with the structured note and a one-click manual-retry button. Jobber API downtime is rare but Charlotte's pipeline is built to ride through it.
Q6How does Charlotte handle Jobber's rate limits?
Jobber publishes their API rate limits in the developer docs; Charlotte's outbound rate to Jobber is throttled per-tenant well below the published ceiling. For high-volume operators (rare at solo scale) the throttle is operator-tunable in the admin portal. Bursty days — a freeze event triggering a hundred plumbing calls in an afternoon — are smoothed out by Charlotte's queue rather than getting rate-limited by Jobber.
How Charlotte sits vs other AI-receptionist vendors for Jobber
Each callout below cites the competitor’s own product page — we don’t fabricate pricing or feature claims we can’t source. Verify the current state on their pages before deciding.
Charlotte vs Goodcall
Goodcall offers a similar AI-receptionist shape with broader vertical coverage. The Charlotte-vs-Goodcall tradeoff for Jobber-using HVAC/plumbing/electrical operators: Charlotte is built specifically for the solo-trades workflow with native warm-transfer and CRM-booking patterns tuned to those three trades; Goodcall is broader and shallower. Compare each vendor's pricing page and integration docs to make the right call for your business.
Charlotte vs Smith.ai
Smith.ai pairs human receptionists with an AI assist layer. The Charlotte-vs-Smith.ai tradeoff: Smith.ai's human-in-the-loop posture trades hourly per-minute costs for the kind of judgment a human brings; Charlotte's AI-only posture trades that judgment for predictable per-month pricing with a generous bundled-minute allowance. Both surface a Jobber integration on their websites; compare each vendor's integration docs and pricing pages directly.
Plans that include Jobber
Jobber integration is included at every tier (Basic $99/mo, Standard $199/mo, Pro $399/mo). See full pricing for the feature matrix.