What Happens in the 48 Hours Before Your Pipeline Goes Live

Your total time investment before we go live is under 30 minutes. We are not going to ask you to sit through a three-hour onboarding call, learn new software, or configure anything yourself. We need four things from you and then we take it from there.

Fill out a short intake form that covers your business name, your primary phone number, and the number you want inbound leads routed to. That is the foundation everything else gets built on.

List your service categories and the geography you cover — emergency plumbing, HVAC tune-ups, electrical panel swaps, whatever your actual menu is, plus the zip codes or mile radius where you take jobs. Vague here means vague pipeline stages later, so be specific.

Grant calendar access. Google Calendar is the most common setup. We connect directly so booked appointments land where your team already looks — no extra app, no relay system.

Finally, tell us where your leads come from today: Google Local Services, a website contact form, Angi, word of mouth, a referral network. Knowing your entry points lets us wire the right automations to the right sources from day one.

That is the full owner input list. Under 30 minutes. Everything after that is on us.

The first work block is strategy, not button-clicking. We process your intake form and map your specific trade workflow to pipeline stages — not a generic three-column board, but stages that match how your jobs actually move from first contact to paid invoice.

For a plumbing shop that might look like: New Inbound → Dispatch Qualified → Appointment Booked → On-Site → Estimate Sent → Job Won / Job Lost. For HVAC, a seasonal tune-up lead and an emergency no-heat call are two different animals. They live in the same pipeline, but routing logic separates them automatically so your dispatcher is not guessing.

During this block we also identify the automation trigger points — the specific moments in your sales cycle where leads stall if nobody follows up. Where does a booked appointment need a confirmation SMS? Where does an estimate sitting three days without a response need a nudge? We map those gaps before we build a single automation.

We also select the custom field set for your trade. Job type, estimated job value, equipment make and model for HVAC, fixture type for plumbing, access notes for garage door calls. Every contact record that enters your pipeline will carry the information your tech or dispatcher actually needs before they pick up the phone.

This is the build phase. Pipeline stages go in with the exact names from the trade map. Custom fields are added to the contact record and the opportunity record. A tag taxonomy gets configured so you can filter your pipeline by job type, lead source, or urgency — no digging through every card manually to find the three emergency calls that came in Tuesday.

Then automations get wired to every stage transition:

• New Inbound fires an immediate SMS to the lead: direct, specific to the service they requested, not a generic acknowledgment
• Dispatch Qualified sends an internal notification to your phone — text or call, your preference
• Appointment Booked sends a confirmation SMS to the lead plus a 24-hour reminder before the scheduled time
• Estimate Sent triggers a 48-hour follow-up sequence if no response is logged in the record
• No Response after 72 hours fires a re-engagement SMS before the lead gets marked dead and exits the active pipeline

Every automation is written for home service context. The copy reads like a plumber or HVAC contractor communicates with a homeowner — direct, clear about next steps, appropriate for someone who submitted a request at 11 PM about a burst pipe. No corporate language, no confusion.

Calendar sync is connected during this block. Booked appointments write directly to your existing calendar. No manual entry, no double-booking risk.

Before a single real lead touches the pipeline, every path gets tested with a real scenario — not a theoretical checkbox, not a quick click-through.

Test leads are pushed through each entry point: web form, inbound call, and manual import. We confirm each one lands in the correct pipeline stage with the right fields populated and the correct tags attached.

Automation triggers are verified against exact timing specs. The Appointment Booked confirmation SMS fires within 60 seconds of the stage move. The 24-hour reminder sends at the right hour. The re-engagement sequence pauses correctly when a lead responds mid-sequence so they are not getting follow-up texts after they already booked.

Calendar sync gets a live test: an appointment is booked through the pipeline, we confirm it appears on your calendar, and we confirm the lead record updates to reflect the booking.

Edge cases get tested explicitly — not assumed:

• After-hours lead at 9 PM — routes correctly, SMS goes out, internal notification holds until morning
• Duplicate contact (same phone number submits a second form) — merges to the existing record rather than creating a ghost duplicate that inflates your pipeline
• Missing phone number on a web form submission — flags to a review queue rather than silently dropping the lead

If anything fails QA, it gets fixed before go-live. The 48-hour window accounts for fix time, not just build time.

Day three, the pipeline is live. Here is what you actually see.

Open your calendar and any test appointments from QA are visible. If a live lead came in overnight — a homeowner who submitted a water heater replacement request at 7 AM — that lead is already sitting in New Inbound with their name, phone number, requested service, and zip code populated. An SMS went out automatically. Your job is to dispatch or let the AI Receptionist qualify and book them directly.

The pipeline view shows every open opportunity sorted by stage. Three leads in New Inbound. One Appointment Booked for Thursday afternoon. Two Estimates Sent without a response yet — both inside their 48-hour follow-up window, sequence already running. You can see all of it in one view without a spreadsheet, a sticky note, or a voicemail you have not listened to yet.

The first real test of the system is not a stress test. It is the first inbound call that hits your pipeline while you are on a job — crawling under a sink, up on a roof, halfway through a panel swap. That lead gets captured, staged, confirmed via SMS, and sitting in your pipeline when you surface. You did not miss it. You did not lose it to a competitor who answered. That is the whole point.

We do not hand you a login and disappear. After go-live, we stay on the system.

Automation health monitoring — if a sequence stops firing or your calendar sync breaks, we catch it before you notice a gap in booked appointments. You should never have to troubleshoot why a confirmation SMS did not go out.

Sequence updates when your business changes — you add drain cleaning to your service menu, we update the pipeline stages, routing logic, and automation copy to match. You do not log in to do it yourself. You tell us, we handle it.

Edge case handling as lead volume grows — patterns surface over time. A particular lead source sends duplicate submissions. A geographic area has a lag in calendar sync. We address those as they appear, not after they have cost you jobs.

Ongoing performance reviews — we check stage conversion rates to see where leads are stalling, whether a follow-up sequence needs tightening, and whether a new entry point (a new ad campaign, a new referral channel) needs to be wired into the pipeline.

You never touch the system. You watch booked appointments appear in your calendar. That is the deal.