When your phone rings, someone wants to give you money. But if an inbound call never makes it into your CRM (no transcript, no follow-up task, no activity log), the lead is as good as lost. For a Virginia landscaping and hardscaping company with a growing inbound pipeline, this wasn't hypothetical. It was happening every day.
The company took roughly 15–20 inbound calls per week. Every call was tracked in a phone analytics platform (CallRail), but the data (summaries, transcripts, texts) lived entirely inside that tool. Getting it into JobNimbus, their field-service CRM, meant manual copy-paste after every call. With a lean team managing installs, estimates, and warranty requests at the same time, that manual step was consistently skipped.
Why inbound calls never made it into the CRM
The company had the right instincts. They'd chosen specialized tools for each job: a call-tracking platform with transcription, a field CRM built for contractors, a web form tool for lead capture. The problem wasn't the tools. It was the gaps between them.
Inbound calls were logged in CallRail with full AI transcription, but those transcripts never flowed into JobNimbus where the estimators worked.
Web forms (on an early site builder) submitted new leads into a third system. Someone had to manually create the corresponding JobNimbus contact and job — often hours later.
Warranty-request forms from existing customers created the same gap: a submission came in, someone noticed it eventually, and a new job had to be hand-entered.
There was no unified view of which leads had been called, which had been quoted, or which had gone quiet.
The founder put it plainly in an early session: chasing down transcripts and getting ready for appointments had become a scramble.
What the Connex team built
The engagement began in fall 2022 and ran through early 2026, a roughly 3.5-year working relationship that grew in scope as each automation exposed the next gap.
Phase 1 — Call data into the CRM
The first build wired the call-tracking platform directly to JobNimbus via Make. When a call ended, an automation triggered within minutes: the call summary, AI transcript, caller ID, and any associated SMS messages were posted as a JobNimbus activity on the matching contact record. If no matching contact existed, a new one was created. Lead scoring based on call keywords ("estimate," "quote," "when can you come out") was added later to help the sales team triage follow-ups.
Phase 2 — Form submissions, end-to-end
The contact form on the company's website was rebuilt using a more capable form tool and connected to the same Make workflow. A new submission now created a JobNimbus contact in under two minutes, pre-filled with the prospect's project description and contact information, and the team got a notification at the same time. The old workflow (someone checking a form inbox, then manually creating a JobNimbus entry) was retired.
Warranty-request forms followed the same pattern: a submission searched for the existing customer in JobNimbus, created a warranty job under that contact, populated the custom fields (project type, install date, issue description), and notified the relevant team member.
Phase 3 — Phone system migration + SQL pipeline
In early 2026, the company switched phone providers, from CallRail to Aircall, to get better team texting features. Rather than rebuilding from scratch, the Connex team replicated and extended the existing automation to route Aircall call summaries, transcripts, and group SMS threads into JobNimbus on the same pattern. The migration was completed in a single 87-minute ZoomFlow session.
In parallel, the team built a SQL data pipeline pulling JobNimbus jobs, contacts, estimates, and expenses into a centralized database, with a Power BI dashboard layered on top. The company could now see monthly sales and backlog hours in a single view — previously visible only by manually exporting JobNimbus reports to spreadsheets.
Estimated impact
📊
These are estimates derived from session data and operating context — not self-reported figures.
The impact estimate focuses on the call-logging automation, the highest-frequency daily friction.
Volume basis: approximately 15 inbound calls per week (derived from JobNimbus activity counts and session notes referencing call volume).
Manual time per call: ~8–10 minutes to find or create the contact in JobNimbus, copy the transcript link, log a note, and set a follow-up task. That's a conservative estimate for a non-automated step.
Automation savings: ~2 hours per week of manual CRM entry eliminated at the point the CallRail integration went live (late 2022).
Annualized: ~100 hours per year returned to the team from call logging alone. At a loaded cost of $25/hr for admin/field coordinator time, that's approximately $2,500/year in recovered labor capacity.
Form routing: warranty and new-lead forms added a further ~30 minutes/week in manual entry eliminated — roughly 26 additional hours/year.
The SQL pipeline and Power BI dashboard are harder to quantify in hours, but eliminated the need for periodic manual exports and custom spreadsheet reports — work that had been recurring monthly.
In total: an estimated 125+ hours/year of manual data-entry and report-prep time replaced by automated workflows, freeing the team to focus on selling and delivering jobs.
Why the engagement lasted 3.5 years
The company came in with a single integration question. What extended the relationship was the pattern that repeated: every solved problem revealed the next friction. Once calls were in JobNimbus, the team noticed form submissions weren't. Once forms were automated, they switched phone providers and needed to replicate the setup. Once the CRM data was clean, they wanted to analyze it.
The ZoomFlow model (book an hour, work alongside a consultant live on Zoom, get a follow-up summary with next steps) meant every session delivered something shippable. There were no two-week planning cycles. The team arrived with a problem; the session ended with an automation running.
Over 28 sessions, the company's satisfaction score remained at 100%.
For service businesses considering this
If your phone system, CRM, and web forms each hold a piece of your customer record and none of them talk to each other, you're losing more than time. You're losing context. Every manual transfer is a moment where a field gets skipped, a follow-up isn't set, or a qualified lead doesn't hear back for three days.
The tools to fix this have never been cheaper. The configuration work is the bottleneck, and it can be done in focused, one-outcome-per-session increments without a months-long implementation project.
🔧
Tools used in this engagement: Make, CallRail, Aircall, JobNimbus, Squarespace, Microsoft SQL Server, Power BI, Power Automate, QuickBooks Online.
Get your calls, forms, and CRM talking to each other
If inbound calls and form leads still reach your CRM by copy-paste, that gap is costing you follow-ups. Connex has helped 400+ companies connect tools like CallRail, Aircall, and JobNimbus so every lead lands where your team works. Book a call with our team and we'll map out the first automation with you.
Automate monthly Salesforce exports from S3 + Google Sheets: pull daily files from S3, calculate member status in Sheets, and generate a weekly CSV in Drive.
