Money
Overdue invoice reminders on a daily sweep, invoice reminders, recurring invoices that generate themselves.
Messages that send themselves
Fourteen switches, zero surprises.
Every step of a job can message the right person automatically: a new booking request pings you, the confirmation texts the customer, on-the-way sends the ETA, completed says thanks. Fourteen message blocks in Settings → Automation, each one editable in your own words with merge fields for the customer's name, the tech, the time and the tracking link, each one toggled per channel. The defaults are deliberately quiet: turning the editor on never starts blasting customers. You opt in, block by block.
Dane4 jobs
8:00Rekey · Maple St
10:30Deadbolt install
11:15Lockout · emergencydragged here
2:00Commercial survey
Rosa3 jobs
8:30Safe service
11:00Key fob program
3:15Master key system
Tuan2 jobs
9:00Storefront repair
Open
1:45Rekey · 4 doors
Sent automatically
Dane is on the way. Arriving 11:15 to 11:35.
Messages that send themselves
Rules on calls and texts
If this, then text that.
Seven triggers start a flow: an inbound call, a missed call, an after-hours call, an inbound text, a callback coming due, a lead going stale. From there the steps chain: send a text, wait for a reply, branch on the answer, tag the contact, notify staff, hand the thread to AI, stop. Calls get the same treatment on the voice side: greetings, menus, ring groups, round robin, voicemail, or an AI answer. Callbacks and cold leads are just flows with a due date, so the follow-up engine and the phone tree are one system, not two add-ons.
The guardrails
Automation with a seatbelt.
This is the part most automation pages skip. In Linq, STOP is absolute: an opted-out contact is never texted again, no exceptions, not even for "transactional" messages. One real event fires one run, enforced at the database, so a double-fired webhook can't double-text a customer. Every flow respects a per-run send cap and a per-contact daily cap. Quiet hours are on, with exactly one engineered exception: missed-call text-back, because the 2am lockout caller should get answered at 2am. And runs survive restarts and redeploys, so a half-finished follow-up never silently dies.
The overnight shift
Work that does itself at 3am.
Schedule
Appointment reminders the day before, job-start reminders to the minute, recurring jobs that rebook themselves.
Upkeep
Review requests queued a day or two after completion, estimates that expire on time, agreements that renew or flag themselves, low-stock alerts before the truck runs dry.
Try it on a real week
Fourteen days. Your actual jobs.
Not a sandbox with fake customers in it. Put a real week through the board, answer real calls with it, and see what the Friday number looks like. Fourteen days, no card, cancel any day.
Campaigns on a signal
Talk when the data says talk.
Some automation isn't about a job, it's about a moment in your own records: a customer lapsing, a quote sitting unanswered, a quote opened but not signed, a warranty about to expire, an invoice past due, a service plan coming up for renewal. Each signal ships with starter SMS and email copy you can rewrite, composes with your tags and filters, and runs through the same consent rules as everything else. The win-back sends itself; the words stay yours. More on the campaigns page.
Pricing
One flat price. The robot works free.
Automation ships with Linq Growth plans and up. One flat price, no per-user fees. See pricing.
Automation questions
What can Linq automate?
The follow-through layer of the whole loop: booking and job-status messages, on-the-way ETA texts, review requests after completion, invoice and appointment reminders, recurring jobs and invoices, missed-call text-back, and custom rules on calls and texts. Field service automation here means the messages and reminders run themselves; the decisions stay human.
Will it spam my customers?
It's engineered not to. Opt-outs are absolute, one event can only ever fire one run, every flow has send caps and per-contact daily caps, quiet hours are on by default, and the out-of-the-box message settings start conservative. The one deliberate exception to quiet hours is missed-call text-back, because a caller at 2am wants an answer at 2am.
Can I edit what it sends?
Every block. All fourteen job messages, every flow step, every signal's starter copy: your words, with merge fields for the customer, the tech, the time and the tracking link. Automation decides when; you decide what.
Does any of this need the AI receptionist?
No. The message automation, reminders and text rules work on every setup. The 24/7 AI receptionist, which answers the call itself and books the job, is the layer on top, on Growth plans and up.
Keep reading
Where this page points next.
Get started
Stop being the reminder.
Set the rules once and the follow-ups happen without you: the thank-you, the review ask, the overdue nudge, the text back at 2am.
Start free, or put one real week through it on the 14-day trial and judge it on Friday.
