Charlotte for Housecall Pro
Inbound calls answered by Charlotte; bookings flow into Housecall Pro automatically.
OAuth callback: /oauth/housecall-pro/callback
Charlotte for Housecall Pro–using HVAC, plumbing, and electrical operators. Inbound calls answered by Charlotte; bookings flow into Housecall Pro as new jobs with caller, address, requested window, and structured notes. Emergency calls bridge to the operator live in under twenty seconds. The OAuth connection takes about ninety seconds via Housecall Pro's standard partner app flow. Charlotte's structured-notes field maps to Housecall Pro's job-notes surface so the operator's mobile app shows context before arrival.
Last updated
What the integration syncs
Booking sync (new-job creation)
Routine appointments book directly into Housecall Pro as new jobs with the caller's name, phone, address, requested window, and structured notes. The Housecall Pro mobile app shows the job within seconds of call-end so the operator has context when they arrive on-site.
Customer sync
If the caller's phone matches an existing Housecall Pro customer, the new job attaches to that customer. New numbers create a new customer record carrying all structured fields from the call (name, address, opt-in flags).
Job sync (status updates)
Operator-side job status changes in Housecall Pro (confirmed, en-route, completed) round-trip into Charlotte's admin portal so the call-history view reflects job lifecycle.
Invoice handoff (Pro tier)
Pro-tier operators get post-completion invoice handoff: completed jobs in Housecall Pro trigger Charlotte's review-request SMS the next morning. The invoice itself stays in Housecall Pro — 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.
Calendar conflicts default to Housecall Pro's resolution
Charlotte respects Housecall Pro's calendar conflict handling but does not run separate overbooking logic. If Housecall Pro accepts a booking inside a busy window, Charlotte books it; if it rejects, the call falls back to a structured note and the operator is paged.
Custom-field coverage is limited at launch
Charlotte syncs the most common fields (name, phone, address, requested time, symptom notes, equipment model). Custom Housecall Pro fields beyond that set need manual mapping during onboarding; coverage expands per request.
Questions operators ask before they connect
Q1How does the Housecall Pro connection work?
Charlotte uses Housecall Pro's standard partner OAuth flow. The operator clicks Connect Housecall Pro inside Charlotte's signup wizard, authorizes the Charlotte app inside Housecall Pro's authorization screen, and the partner platform 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 on Housecall Pro's standard schedule.
Q2What scopes does Charlotte ask for?
Read and write access to jobs and customers in the connected Housecall Pro account — the minimum scope needed to create new jobs and attach them to existing customers. Charlotte does not request payments, payroll, or any unrelated surface. The exact scopes appear on Housecall Pro's authorization screen and are reviewable before granting.
Q3Will Charlotte sync to my Housecall Pro mobile app in time for the day's first job?
Yes. New jobs created by Charlotte appear in the Housecall Pro mobile app within seconds of call-end. The operator's morning routine (open Housecall Pro on the phone, see the day's jobs) shows every overnight Charlotte booking already in place — no manual re-keying from voicemail, no copy-paste between systems.
Q4Can I disconnect Charlotte from Housecall Pro?
Yes. Disconnect from either Charlotte's admin portal or Housecall Pro's connected-apps view. Disconnecting revokes Charlotte's OAuth tokens immediately and stops new job sync; existing jobs Charlotte created in Housecall Pro stay there and remain fully editable. Charlotte's call-history view continues showing them with a disconnected badge so the operator can see the sync is paused.
Q5Does Housecall Pro charge me anything extra for the Charlotte integration?
Charlotte's integration uses Housecall Pro's standard partner API which is included in all paid Housecall Pro plans. Housecall Pro does not charge additional fees for using the partner API for inbound-job creation. Verify the current state on Housecall Pro's own pricing page in case their plan structure changes; Charlotte does not pass through any Housecall Pro fees.
How Charlotte sits vs other AI-receptionist vendors for Housecall Pro
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 Rosie
Rosie targets a similar receptionist-for-trades shape. The Charlotte-vs-Rosie tradeoff for Housecall Pro–using operators: Rosie's per-trade phrasing in their marketing copy is well-tuned, but the underlying integration depth varies. Compare each vendor's Housecall Pro integration page and feature parity directly; pricing on both vendors is published at competitor's own pricing surfaces.
Charlotte vs RingCentral AI Receptionist
RingCentral's AI Receptionist is bundled into their broader PBX product. The Charlotte-vs-RingCentral tradeoff: RingCentral makes sense for operators who already pay for the full RingCentral PBX stack; Charlotte makes sense for operators who want an AI receptionist without adopting an enterprise PBX. Compare each vendor's pricing model on their respective pricing pages.
Plans that include Housecall Pro
Housecall Pro integration is included at every tier (Basic $99/mo, Standard $199/mo, Pro $399/mo). See full pricing for the feature matrix.