Daniel, we do not have a clean read on your hobbies yet, so we will not pretend. What we can say: your day is probably better spent with branch leaders and customers than chasing callbacks, invoices, and COIs.
Daniel Reyes / VP Operations / Meridian Mechanical Group
The working brief points to a multi-branch mechanical services business with acquisition and dispatch complexity. If that read is off, correct us on the call. If it is right, after-hours intake is the first place to stop leaking work.
Two things about us
We are a small AI automation services company with a US-based delivery team. We like building relationships in person, and we will fly to you when that helps get the workflow set up right.
Our founders are ex-Google, Meta, and Snowflake engineers who spent over 10 years building AI and data products used by millions. We start with a 14-day free engagement. If we do a good job, all we ask is a good word.
What we noticed before the call
Public corroboration was limited in this pass, so the page separates the operating thesis from verified facts. That is still useful: Daniel can confirm or reject the shape in five minutes.
The draft brief points to multiple branches and acquisition integration. That usually means dispatch, accounting, and customer records are stitched together by people.
src / provided draft page / marked hypothesisCommercial mechanical work has urgent calls outside business hours. If callers hit voicemail or a weak answering service, the job can go to whoever answers first.
src / role-based operating hypothesisCOI requests, AP mismatches, and missing job details are rules-heavy tasks. They are good first workflows because the output is easy to review.
src / provided draft page / marked hypothesisThree workflow opportunities
The point is not a chatbot demo. It is one finished workflow that answers, checks, routes, logs, and escalates when judgement is needed.
maps to OpenNash Voice & Messaging
| Before | Emergency and inbound calls outside business hours risk voicemail, callbacks, or an answering service that cannot complete the job. |
| Agent role | Answers the call, gathers required job data, checks customer status, books the slot, sends confirmation, and flags true emergencies. |
| Human review | On-call lead reviews emergency flags, unusual requests, and uncertain account matches. |
| Measured | After-hours capture rate, booked jobs, missed calls, and time to confirmed dispatch. |
maps to OpenNash Finance Ops
| Before | Invoices arrive in different formats and may not match the right PO, customer, branch, vendor, or acquired-entity ledger. |
| Agent role | Reads each invoice, matches it to the PO and vendor record, drafts the approval packet, and queues only exceptions. |
| Human review | Controller or branch admin reviews exceptions instead of touching every clean invoice. |
| Measured | Touch time per invoice, exception rate, approval cycle time, and duplicate payments prevented. |
maps to OpenNash Workflow Automation
| Before | Certificate-of-insurance requests bounce between branch staff, brokers, customers, and general contractors. |
| Agent role | Detects the request, pulls the right certificate, drafts the reply, files the document, and follows up until receipt is confirmed. |
| Human review | Ops reviews non-standard coverage, new customer requirements, or anything that changes risk. |
| Measured | COI turnaround time, jobs blocked by paperwork, and follow-up messages avoided. |
What ships
One chosen workflow running against Daniel-approved test cases.
The records, systems, and rules the agent needs to read and write.
Clear exception routing for anything that needs judgement.
Every call, match, draft, and escalation recorded.
Capture rate, cycle time, exceptions, and dollars saved.
Your team can review, operate, and extend the workflow.
Pilot terms
Most vendors show a demo. We first confirm the workflow is real, then make that work run.
For Daniel, the first call should decide which workflow is real: after-hours intake, AP matching, or COI follow-up. We write the acceptance tests in plain English and ship against them.
If the workflow does not pass the tests in the 14-day pilot, you do not pay. If it does, the monthly service runs that work with logs, review gates, and clear ownership. The terms shown here are standard OpenNash pilot terms.
Thirty minutes. Confirm the operating picture, choose the workflow, and define the acceptance tests. Two weeks later, you have a pilot to judge.