← Ted KellyDEMOFictional company & dataView code
Summit Home Services · Office tools · M3

Every update lands in the thread they're already reading. Nobody has to ask “where's my tech?”

When a job moves (received, scheduled, tech on the way, done), a short, correct update is posted as a reply on the customer's or warranty company's own email thread, helpdesk ticket or portal. If it can't find the right thread, or the customer has just written something, it stops and asks a person.

One job, two ways

What changedIllustrative numbers for this demo job
Before

The office answers by hand

After

Updates post themselves, on the same thread

Demo clock
10:12 AM

Try it: move a job along

Pick a job, then press the next status. Each press runs the same checks the real automation runs, and the reply appears on that job's thread.

The thread

Anything the automation isn't sure about lands here with the full story: which thread it looked for, what it found, and the update it was going to post. A person decides.

The safety rules it follows

    What it costs to run

    Per update, Google Workspace$0Apps Script and the Gmail API are included with Workspace, within Google's daily quotas. A small shop posts a few dozen updates a day.
    Optional AI rewrite~0.1¢Templates are the default and need no AI. If you want a model to smooth the wording, it's a fraction of a cent per update.
    n8n instead$5+/moSelf-hosted on a small server from about $5 a month, or n8n Cloud on a monthly plan. Pricing changes, so check n8n's current page.
    Helpdesk and portals$0 extraComments go through the helpdesk's or vendor portal's own API with the login you already have.

    Ted builds it for a fixed price, then a monthly retainer covers running it: keeping an eye on the Needs a person queue, adding templates when you take on a new vendor, and fixing what breaks.