End to End: The Customer Journey

Most help articles describe one feature in isolation. This one zooms out. It walks the entire path a single customer takes through Suprata, from "we don't know who they are yet" to "the invoice is paid, QuickBooks knows, and they left a five-star review." If you're trying to understand how the pieces fit together — why an account has tabs for jobs and invoices and contracts, why an appointment is different from a job, why closing an invoice triggers a sync — read this once, slowly. The rest of the system will make a lot more sense.

The journey has nine stops. Each one is handled by a different feature; each one writes a record that the next stop reads.

Stop 1 — The phone rings (or the form arrives)

Someone wants service. They might call your front office, fill in a public request form on your website, reply to a marketing SMS, or walk in the door. However they arrived, the first thing the system needs is an Account — the billable entity you're going to do business with.

Search before you create. This is the single most important habit your office can build. Before you type a new account into the system, search by phone, name, or address. Suprata will surface anyone matching, and nine times out of ten you'll find the customer already exists from last summer's tune-up. If you create a duplicate, you fragment their job history, you double their balance, and you eventually get a "why did you bill me twice?" call.

If the customer truly is new, create an Account and at least one Contact. The distinction between the two is covered in The anatomy of an Account vs. a Contact — read that before you create your first one. The short version: Account = the household or business; Contact = a person attached to it. A residential customer is one Account with one or two Contacts (the homeowners). A commercial customer is one Account with three or four Contacts (decision-maker, AP, site contact).

Capture phone, email, and service address up front. Email is what every future invoice and confirmation will go to; address is what every appointment will geocode against; phone is what every reminder SMS will hit.

A populated account dashboard — the home base for everything that follows

Stop 2 — A Job is born

A Job (sometimes called a workorder) is the unit of work. It's distinct from the Account because one customer might have many jobs over the years, and each job has its own status, its own assigned tech, its own line items, and its own eventual invoice.

Create the job from the Account dashboard — there's a Jobs section that lets you spawn one with the Account already attached. At minimum the new job needs:

Job type (Service Call, New Install, Estimate Visit, etc.). This matters because the job type controls which industry forms automatically attach. If you're an HVAC shop, the "Service Call" type might pull in a system evaluation form so the tech captures model numbers and refrigerant readings without anyone remembering to ask. See Industry forms — what attaches when.
Service location. Often the same as the Account's billing address, but not always — rentals, second homes, and commercial multi-site clients diverge here.
A description of what the customer asked for. Your tech will read this. Be useful, not cute.

The job lands in the New or equivalent unscheduled status. It's recorded but nobody's been told to do it yet. See Creating your first job for a deeper walk-through and Job statuses and the state machine for what each status means.

Stop 3 — The Appointment

A Job is the work; an Appointment is when and who will do it. The two are linked but separate. Why? Because:

One job can have multiple appointments (estimate visit, then install, then warranty check-in).
An appointment can move (reschedule) without rewriting the job.
Some businesses dispatch jobs same-day with no formal appointment — those jobs skip this stop.

Schedule from the Account, the Job, or the Calendar — all three roads lead to the same place. Pick a tech (or a team), pick a window, save. The system records the link in the Appointment record and updates the Job's status from "New" to "Scheduled."

That status update isn't cosmetic. It feeds the dispatch board, the calendar, and any automation watching for "Job became Scheduled" — which is often where appointment confirmations are triggered. The brief between Scheduling and the dispatch board and Appointment confirmations and reminders explains how the chain reacts.

The dispatch board — where today's appointments materialize

Stop 4 — Confirmation

Before the day of service, the customer needs to be reminded. Suprata can send these confirmations automatically — typically by SMS via Twilio for residential, by email for commercial. Configure the timing once and forget it; see Customizing the appointment confirmation.

If the customer doesn't respond to a confirmation, the morning dispatcher catches it and calls. (See The morning dispatch routine.) That's the single biggest source of avoided no-shows: the system pings, then a human follows up on silence.

Stop 5 — Dispatch and the "tech on the way" message

The morning of the appointment, your dispatcher opens the dispatch board. Each tech is a row; each appointment is a card. As crews load up and head out, the dispatcher sends a "tech on the way" SMS — sometimes manually, sometimes automatically when the tech's status flips. The customer now expects you in the next thirty minutes.

This is also where last-minute swaps happen. Tech called in sick? Drag the job to another tech. Customer asked to add a second item? Update the job description. Address turned out to be wrong? Fix it on the Account so future appointments don't repeat the mistake.

The dispatch board is the operational pulse of the day. It's the screen your dispatcher will spend most of their time on, and the more it reflects reality, the smoother everything downstream gets.

Stop 6 — Work happens, and gets recorded

Your tech arrives. They open the job on their phone or tablet, take photos, fill in the industry form (HVAC reading, marine boat conditions, IT equipment serials — whatever applies), capture a customer signature, and add line items from the price list as they consume parts and time. Time clock punches against the job, if you use the time clock, are recorded against that job so payroll knows what to attribute.

By the time the tech is rolling out of the driveway, the job should be in "In Progress" or "Complete" status with line items, photos, signature, and notes. The more complete the field record, the less office cleanup tomorrow.

There are two patterns here that office staff need to know:

Some techs leave jobs in "In Progress" instead of "Complete." They mean to come back to it but they forget. The end-of-day closeout sweeps these up — see The end-of-day closeout.
Some techs forget to add line items. Then the invoice they triggered has no items on it. This is one of the most common end-of-day fix-ups.

Stop 7 — Invoice generation

Once the job is closed, an invoice is generated from it. This can be automatic or manual depending on how you've set things up. The invoice inherits the Account's billing terms (Net 30, Due on Receipt, COD), pulls line items from the job, applies tax based on each item's tax category, and lands in the office's outbox waiting to be sent.

If the customer was given an estimate first, the estimate becomes an invoice through a conversion flow rather than being recreated — see Estimates vs. invoices for how that works.

The office reviews invoices before sending. Watch for:

Missing line items (tech forgot to add parts they used).
Wrong tax category on a one-off item that wasn't in the price list.
Wrong terms because the Account's defaults haven't been updated.

Once everything looks right, send. The invoice email goes out via your configured SMTP, the customer gets a payable link, and the invoice flips to "Sent" status. See Sending an invoice to a customer.

Stop 8 — Payment capture

The customer pays. Three roads:

They click the link in the invoice email and pay through the customer-facing portal with a saved card or fresh card. Stripe or USIO handles the transaction; the payment is recorded against the invoice automatically. See Connecting Stripe and Saved payment methods and when to use them.
They mail a check that you receive in two days, deposit, and key in manually as a payment of type "Check."
The tech captured payment on-site at job closeout, either with a card reader or a saved-method charge. That payment may already be recorded by the time the office opens the invoice.

Whichever road, the payment record links to the invoice, the invoice's amount-paid and amount-due totals recompute, and if the invoice is fully paid the system marks it closed. Closing an invoice is a meaningful event — it's the point at which the record is locked and (if QuickBooks is connected) queued for sync.

If the customer pays only part, you have an open invoice with a partial payment. That goes onto the A/R aging report and starts the late-fee/reminder clocks running. See The aging report.

Stop 9 — QuickBooks sync, and the review request

Two things happen after the invoice closes:

QuickBooks sync. If you've connected QB, the closed invoice (and its payment) push to QuickBooks automatically on the next sync pass. The customer record on the QB side maps to the Suprata Account; the line items map to QB Items; the payment is applied. If anything goes wrong with the mapping, the QB sync report tells you. See QuickBooks first sync walkthrough and Reading the QuickBooks sync report.

Review request. A closed and paid job can trigger a review-request email or SMS that links the customer to whichever review platform you use (Google Business Profile, Yelp, Facebook). The message takes the customer to your review page on that platform, where they leave the review. The success rate is shockingly high if you send within 24 hours of completion and shockingly low if you wait a week.

When the customer responds — leaves a 5-star review, or replies "looked great, thanks!" — the result lands back on the Account record. Mary in the office sees a green star next to that customer's name next time she pulls them up. The relationship is now richer than it was before. Next time they call, your team has context: this is a happy returning customer.

Why the chain matters

You can short-circuit any of these stops. You can skip the Appointment and dispatch a tech same-day. You can skip the line items and invoice a flat amount. You can skip QuickBooks sync if you're not using it. You can skip the review request.

But every one of those skips trades a small amount of friction for a small amount of long-term cost — duplicate accounts, mystery balances, customers who never get reminded, jobs with no record of what was done. The payoff for following the chain is that, two years from now, when a customer calls back about a unit they think you installed, you can pull up the Account, see every job, every invoice, every payment, every photo, every form, every conversation. That's worth doing the boring data hygiene now.

What can go wrong

Duplicate accounts. The original sin of CRM. Once you have two records for the same household, every report is wrong. Search before you create. See Cleaning up duplicate accounts for the cleanup.
Job closed without line items. The invoice generates with nothing on it. Office sees a $0 invoice and either deletes it (losing the record) or fakes a line. The fix is upstream: train techs to add parts and labor as they consume them, not at the end.
Invoice closed before review. Invoices that are closed get locked and synced; if you spot a mistake at this point you have to void and reissue. Have someone review every invoice before closing.
Payment captured but not applied. Happens when a payment is recorded against the Account rather than against a specific invoice. The invoice still shows unpaid; the Account shows a credit. Reconcile by applying the credit to the invoice. See Customer credits and refunds.
QB sync failure ignored. If QuickBooks rejects an invoice (because the customer mapping is wrong, or an item doesn't exist on the QB side), the invoice sits in a failed-sync state. Most offices don't notice for weeks. Make checking the QB sync report a daily five-minute habit.
Review request sent too late. A week after the job closes, the customer barely remembers it. Send within 24 hours or skip the request.

Where to go from here

This article is the spine; the limbs are everywhere else in the KB. Pick the stop that matters most to your role and dig in:

Front office / call-takers — start with The anatomy of an Account vs. a Contact and Creating your first job.
Dispatchers — The morning dispatch routine and Scheduling and the dispatch board.
Field techs — Job attachments — photos and signatures and The time clock.
Office / billing — Sending an invoice to a customer, The end-of-day closeout, and The end-of-month routine.
Owner / GM — The revenue report and The aging report.