Built my own AI operating system on Jobber. One gap: Jobber's text conversations

I run a home services company, and since late September I've been building what I call our "OS": a private web app that connects Claude AI to Jobber, GoHighLevel, RingCentral and Google. I'm not a coder. I built it by describing what I wanted to Claude Code, the same way I built our end-of-day reporting app.

Claude connects to the OS through a custom MCP connection, and the OS talks to Jobber through my own Jobber API apps (one read-only, one with write access). Nothing gets sent or created without my approval. Claude proposes it, and I approve it.

Here's what it does today:

JOBBER

- Read: find clients by name, phone, email or address

- Read: properties and custom fields

- Read: jobs, visits, requests and invoice summaries

- Read: price history (past invoices and quotes)

- Read: team calendar and open estimate time slots

- Read: new requests still waiting on a reply

- Write: create new clients (with texting turned on)

- Write: create draft quotes

GOHIGHLEVEL

- Read: contacts, conversations and message history

- Write: send SMS replies (opt-outs checked first)

RINGCENTRAL (our office texting line)

- Read: text conversations and recent calls

- Write: send text replies

GOOGLE

- Read: check service addresses before they go into Jobber

SCREENSHOT INTAKE

- I drop in a screenshot of a lead, and it pulls out the details, checks whether they're already in Jobber, then creates the client or adds a note

BEHIND THE SCENES

- Our business rules and price list live in the OS, and Claude reads them live

- On/off switches for every kind of write

- An activity log of everything it did in each app

- When I correct a draft, it logs the change so the drafts get closer to how we actually talk

THE ONE GAP: text conversations inside Jobber.

Claude can read a customer's texts in GoHighLevel and RingCentral, but not the conversation they're having with us through Jobber's own texting. As far as I can tell, the public API doesn't expose those messages, and there are no webhooks or Zapier triggers for them. Right now I work around it with screenshots and copy/paste. I've emailed Jobber API support and I'm waiting to hear back.

Has anyone found a way to read (or send) Jobber text messages through the API or an integration? Or is there a setting or solution I'm missing? I'd love to hear how others are handling it, and I'm happy to share what I learned along the way.