MCP/API Feedback

Ability for the MCP/API to create, modify, and delete recurring visits.

The MCP connector can read customer texts (smsMessages) but there’s no mutation to send one. This is the missing half of the best use case you’re marketing. Two real workflows I’ve built with Claude that are stuck at the same wall: 1. Inbound replies. Claude reads every incoming customer text, pulls the full account picture (thread history, jobs, invoices, estimates), and drafts a reply for my approval — but after I approve, I still have to copy-paste the draft into the app by hand because nothing can send. 2. Seasonal retargeting of our whole estimate backlog. We just cleaned up 130+ stale pending estimates (~$25k in unanswered quotes) and archived them as a retargeting pool. A monthly AI job now surfaces everyone whose service season is opening — 100+ fert and aeration quotes come into their fall window in the next few weeks — with a personalized text drafted for each person. With a send mutation, I could approve the batch and have every message go out from our business number, logged in each customer’s conversation thread. Without it, I’m hand-sending 100+ texts one at a time, which means realistically most won’t get sent. Requested: a sendSms mutation (customerId + message) that sends from the company number and logs into the existing conversation like a normal outbound text. A mutation to mark a message viewed/done would also help AI assistants hand off cleanly instead of re-flagging the same text. Texting already runs on Twilio under the hood, so this seems like a small lift for a huge unlock — it turns “AI drafts, owner approves, nothing sends” into a complete workflow. Happy to beta test.

This would be useful for phone agents to understand things like service areas, service offered, and other granular systems for that specific location.

Right now the Calls/Notes log on a customer record (calls notes, follow ups with author and date) isn’t available through the GraphQL API. We can read and write customer description and job dispatch notes, but not this log. Request: add API support to 1. Read existing call notes for a customer for AI context. 2. Add a new call note entry for history for command centre (say emailing externally) This would let us log customer interactions and other communications (like emails handled outside the CRM) automatically instead of manual entry, so reps always have a full accurate history in one place.

Right now every text an automation sends has to be tied to one fixed template. My estimate follow-up automation, for example, sends the same message every time no matter what the customer said or what’s specific to their job. This connects to the send-SMS API request I already submitted. Even with that mutation, if automations still require a static template per trigger, it won’t fully solve it. What would really help is letting automations pull in AI-generated, context-aware text instead of (or alongside) a fixed template, so follow-ups read like a real reply instead of a mass text. Longer term, true AI auto-replies to inbound customer texts (using the actual conversation as context) would be huge for things like estimate follow-ups. Happy to test this if you’re exploring it.

The status field on a recurring series can be active, paused or cancelled. It's a bit confusing that a recurring series with an end date in the past will still have status = active. When I asked Claude for active mowing customers, it checked for series with a mowing line item with status = active, which makes sense at first glance. However, it returned about 40 more customers than I expected. I started looking at these customers in the Homeworks UI and didn't see a recurring series on their profile page. Then looking at the recurring series page, I saw the mowing series with an end date in the past with status active. Once the end date is past, could the status on these series be changed to cancelled instead of remaining active since they are effectively cancelled?