ServiceTitan and Jobber
The caller pop-up shows the customer, their open jobs and which technician is on each job; the AI
agent can look customers and jobs up, open a job and say where the technician is. Installed like any
integration (Admin, Integrations). Code: pbx/crates/integrations/src/fieldservice/, one
registration file per vendor under src/connectors/. No table of its own: jobs stay in the vendor.
Install
| Connector | Settings | Secrets | Auth |
|---|---|---|---|
servicetitan | tenant id, client id, business unit / job type / campaign ids (needed to create jobs), sandbox switch | client secret, app key (ST-App-Key) | client credentials, token kept in memory until a minute before expiry |
jobber | none (job-on-missed-call switch) | none | OAuth connection (oauth_connections): Connect signs in to Jobber, MonoPbx keeps and rotates the refresh token. An install made before the framework keeps its own client id, secret and refresh token (rotated in memory only) until it is connected |
Both need the vendor's partner/developer app (owner work). "Test connection" gets a token and reads one customer (ServiceTitan) or the account (Jobber).
What it does
- Pop-up (caller lookup by E.164): customer name, e-mail, number of open jobs and, for the first three open jobs, "technician <name> (<scheduled|dispatched|working|done>)". Finished and cancelled/archived jobs are not listed.
- AI tools (
int_<connector>_<tool>, per install allow-list):find_customer(phone, e-mail or name),list_open_jobs,create_job(customer id or the caller's phone; the same request within 10 minutes is the same job),technician_status(technician, state, visit window),job_call_target(the customer of a job and the number to dial: click-to-call from a job). - Job from a call: with "open a job for a missed call or voicemail" on, an unanswered inbound call or a voicemail of a known customer opens one job (summary, AI summary and recording link in the job). Unknown numbers never create a job, and a re-delivered call log never creates a second.
Notes
- ServiceTitan needs an appointment to create a job: the job gets a placeholder window (tomorrow 08:00-12:00 UTC) for the dispatcher to move. The customer's first active location is used.
- All values reach Jobber as GraphQL variables; ids are checked before they go into a path.
- Outbound calls go through the guarded egress client only; tests use a recorded fake.
- Tests:
cargo nextest run -p mpbx-integrations -E 'test(servicetitan) | test(jobber)'.
Changes made in the field-service system
A change a person makes in ServiceTitan or Jobber can reach MonoPbx. Create a hook endpoint for the connector under Integrations > Inbound hooks (https://pbx.example.com/hooks/int/servicetitan/<install key>, or jobber), choose the signature check of the system (an HMAC of the body in a header; Jobber signs with the app's client secret) and register the address as the system's webhook. A new job raises integration.field_job_created (job id and number, never the customer or the address); other job and visit changes raise integration.hook_handled with the kind field_job_status. Both appear on the events WebSocket and in webhooks.