8 workflows currently running on the office.
Every LoopLogic pilot ships with a documented set of automation scripts — the AI receptionist, the missed-call text-back, the post-appointment followup, the CRM sync. This page is the live catalog: each script’s name, what it does, and the timestamp of its last successful run. An active script is one that is wired into the office, has fired at least once this week, and is showing a clean run on its most recent invocation.
What’s running right now, and when it last ran.
A read-only view of the office’s automation surface. The cards below are refreshed every render against the office’s script registry — no login required to read, nothing is gated behind the dashboard.
Inbound receptionist
Answers every phone call, qualifies the caller against the office intake, and hands live to a human when the question is outside scope.
Missed-call text-back
Fires within 60 seconds of a missed call — drops a branded SMS to the caller with the booking link and the office hours.
Post-appointment followup
Three-touch sequence after a booked job: thank-you on day 1, satisfaction check on day 3, review request on day 7.
Review request campaign
Pulls the last completed visit from the CRM, drips a four-step ask across email and SMS, and tags the contact once a five-star review lands.
Lead routing CRM
Pushes every new lead from the receptionist or web form into HubSpot or GoHighLevel and routes to the right pipeline by vertical.
Calendar sync
Two-way sync between Google Calendar and Outlook — every booked appointment lands on the assigned technician’s calendar inside ten seconds.
After-hours text reply
Replies to inbound texts outside business hours with the on-call escalation flow — books urgent jobs straight into the on-call calendar.
Weekly KPI digest
Emails the office a weekly KPI digest every Monday at 7:00 AM CT — call volume, booking rate, missed-call recovery, and review count.
We add new scripts to a pilot as the build progresses and remove them when the customer retires a flow. The timestamps shown above reflect the last successful run for each script, not the last deploy — a script that has not fired in the window is marked idle even if the code is loaded. To see the same set as authenticated customers, open the loop dashboard.