1import{j as e,c1 as t,c2 as o,U as a}from"./index-CzAkNt2W.js";import{C as s}from"./FeatureVisuals-DTmdkc4B.js";import"./triangle-alert-Cl8dz-Zm.js";import"./camera-CjA2pwTw.js";import"./grip-vertical-xb7LzVoA.js";import"./flask-conical-kc3-ZtHR.js";const d=()=>e.jsx(t,{icon:a,heroVisual:e.jsx(s,{}),eyebrow:"Customer CRM",title:"A pool service CRM that actually fits the route business.",lede:"Every homeowner, every pool, every gate code, every visit, every reading â searchable in two taps. Stop juggling a contacts app, a spreadsheet of pools and a notebook full of equipment models.",heroBullets:["Unlimited customers and properties on every plan","Lead pipeline with stages and follow-up reminders","Per-property equipment, chemistry history and gate codes","Route assignment baked into the customer record"],intro:e.jsxs(e.Fragment,{children:[e.jsx("p",{children:"Most pool service software was designed for plumbers, electricians or general handymen and then bent into shape for pools. That's why service businesses end up duct-taping a generic CRM to a paper route sheet and a separate billing tool. SplashIQ was built the other way around: the customer record assumes a pool, the property record assumes equipment, and the route assumes recurring weekly chemistry."}),e.jsx("p",{children:"If you run a pool route â residential, commercial, condo association or a hybrid â the CRM at the centre of your business needs to know that a single customer can own three homes, that each home can have a spa and a pool, that each body of water has its own pump and heater, and that every Tuesday a technician shows up to test the chemistry. SplashIQ stores it all in a single graph and surfaces it the way your team actually works."})]}),sections:[{heading:"One customer, many properties, every detail",body:e.jsxs(e.Fragment,{children:[e.jsx("p",{children:"A customer record in SplashIQ is the entry point to everything you know about that account. Open it and you see contact details, preferred contact method, billing notes, a timeline of every visit, every invoice, and every flagged issue. Click into a property and you get the address, gate code, pool type (in-ground, above-ground or spa), gallonage, service frequency and the assigned technician."}),e.jsx("p",{children:"This matters because pool work is messy. The homeowner pays the bill but the housekeeper opens the gate. The pool is in-ground but there's also a spa with a separate chemistry profile. The pump was replaced last August but the heater is still the original from 2009. A generic CRM forces all of that into a single text field. SplashIQ gives it real structure so a technician arriving for the first time has every fact they need before they get out of the truck."})]})},{heading:"Leads and customers in one pipeline",body:e.jsxs(e.Fragment,{children:[e.jsx("p",{children:`Leads and customers live in the same searchable list, separated by a simple toggle. A new website inquiry comes in as a lead with stage "new". Your office team moves it to "contacted", then "qualified" once they've spoken to the homeowner, then "quoted" after sending a proposal. When it closes, one click converts it to a customer and the property and route assignment workflow takes over.`}),e.jsx("p",{children:"Every lead carries a follow-up date. Overdue follow-ups light up in amber on the dashboard so nothing rots in a spreadsheet for three weeks. When you win the job, the entire conversation history travels with the converted record so the technician doing the first visit can see exactly what was promised."})]})},{heading:"Search that knows what you're looking for",body:e.jsx(e.Fragment,{children:e.jsx("p",{children:"Type a partial street name and SplashIQ returns the matching property. Type a phone number and it returns the customer. Type a pump model and it returns every property running that pump â invaluable when a manufacturer issues a recall. The CRM understands the relationships between customers, properties, equipment and visits, so a single query can answer questions that take a spreadsheet half an hour."})})},{heading:"Built for the way pool routes actually run",body:e.jsxs(e.Fragment,{children:[e.jsx("p",{children:"Every property is assigned to a technician and a service frequency: weekly, biweekly, monthly or on-demand. That assignment drives the schedule, the route map, the work-order queue and the homeowner's portal in one go. Reassign a technician and the change ripples through the calendar automatically. There's no second system to update."}),e.jsx("p",{children:"Commercial accounts get the same treatment. A property manager who owns twelve condo pools is a single customer with twelve properties, each on its own frequency, each with its own equipment list and its own homeowner portal link. Bill them as one account, service them as twelve."})]})}],benefits:[{title:"Onboard new techs in an afternoon",body:"Every property page already contains the equipment list, gate code, dog warning and chemistry history. A new technician can run a route on day one."},{title:"Stop losing leads to follow-up fatigue",body:"The lead pipeline with follow-up reminders means hot leads never sit unread in a Gmail inbox for two weeks."},{title:"One source of truth across office and field",body:"When the office updates a phone number or a service frequency, the field a
1pp reflects it on the next visit. No syncing, no spreadsheets, no confusion."},{title:"Grow without growing the admin",body:"Adding the hundredth customer takes the same effort as adding the tenth. The structure scales; the headcount doesn't have to."}],faqs:o,closing:e.jsx(e.Fragment,{children:"Run your route off a real CRM, not a spreadsheet."})});export{d as component};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.