The Sold Jobs Pipeline is a Kanban board that tracks every sold job from deposit collection to final payment. It lives inside CxC and syncs automatically with ServiceTitan so your team always knows where every job stands β without chasing updates or making calls.
This article explains how jobs enter the board, what happens at each stage, who owns it, and what to do when alerts fire.
How Jobs Enter the Pipeline
Jobs enter the pipeline automatically. No one adds them manually.
A job is routed to the board when all three conditions are met in ServiceTitan:
The estimate is marked Sold and the amount is above your company's configured threshold
The job status is Completed
Revenue collected is less than the estimate sold amount
When those conditions are met, CxC evaluates the job and routes it to the correct column based on where it is in the process. A system message posts in the job's chat channel confirming it has entered the pipeline.
The Board at a Glance
The board header always shows:
Total number of active jobs in the pipeline
Total pipeline value β the sum of all estimate amounts across every active card
Per-column totals so you can see workload and value at each stage
Use the filter controls to narrow the view by technician, business unit, or other criteria. Totals update automatically to reflect your filtered view.
The 8 Pipeline Stages
Stage 1 β Confirm Deposit
Owner: Primary Technician
When a job enters the pipeline, CxC automatically checks whether the required deposit has been collected based on your company's deposit settings.
If the deposit is confirmed: the card advances automatically
If the deposit hasn't been collected: an alert appears on the card and a message posts in the job chat notifying the manager and tech
If the deposit still hasn't been collected after 24 hours, a second alert fires.
Your deposit percentage is configured by your admin in CxC Settings. The system enforces state deposit laws based on the job location β the configured percentage cannot be set below the state minimum or above the state cap where a legal limit exists.
Stage 2 β Material / Equipment List
Owner: Technician or any job channel member
When the card enters this stage, CxC automatically pulls line items from ServiceTitan β including item name, quantity, unit price, and total price. The list populates immediately so your team isn't starting from scratch.
Any job channel member can add, edit, or remove items
Each item can be individually checked off as it's sourced
Upload a Purchase Order directly on the card β it doesnβt sync back to ServiceTitan automatically right now
Set a material ETA so the team knows when parts are expected to arrive
The card advances when all items are checked off
If the list isn't completed within 30 minutes, an alert fires on the card and in the job chat.
Stage 3 β Sourcing
Owner: Production Manager
The Production Manager uploads a Purchase Order for the required parts and sets an expected arrival date.
If parts arrive on time: the Production Manager confirms arrival and the card advances
If parts are delayed beyond the ETA: an alert fires on the card and a message posts in the job chat automatically
The parts delayed flag can also be set manually if needed
Purchase Orders uploaded here sync back to ServiceTitan automatically. Line item cost data is parsed and pushed into ServiceTitan to support accurate job costing and margin tracking β replacing the manual process of entering POs by hand.
Stage 4 β Arrival Confirmation
Owner: Production Manager
The Production Manager confirms that parts and materials have physically arrived by checking a box on the card.
Confirmation is a manual action
Once confirmed, the card advances to Stage 5 automatically
Stage 5 β Schedule Job
Owner: Production Manager
The Production Manager schedules the follow-up appointment in ServiceTitan.
Once the appointment is booked and confirmed, the card advances to Work In Progress automatically
The appointment details are visible on the card
Stage 6 β Work In Progress
Owner: Field Team
The job is active and the technician is on site. The card stays in this column until the work is marked complete in ServiceTitan.
Your team can message, record, and share updates in the job chat channel throughout this stage. Any alerts or bot insights post into the thread automatically.
Stage 7 β Confirm Payment
Owner: System (automated)
CxC automatically validates whether the total invoice matches the total payment collected.
Only successful payments count β failed, voided, and refunded payments are excluded
If invoice total equals payment collected: the card advances to Done automatically
If there's a shortfall: an alert fires on the card and in the job chat so the team can follow up
No manual action is needed unless there's a payment gap to resolve.
Stage 8 β Done
Owner: System
The job is complete and fully paid. The card stays visible on the board for 48 hours, then is automatically removed β no notification, no action required.
All job data, recordings, messages, and history remain in CxC and ServiceTitan. Only the card is removed from the board view.
π¨ Alerts
Alerts appear at the top of the board and in the job's chat channel. They fire automatically when something needs attention and include the job number and customer name so you can act immediately.
Alert
When it fires
Deposit not collected | Deposit validation fails at Stage 1 |
Deposit 24h overdue | 24 hours passed, deposit still outstanding |
Material list 24h overdue | 24 hours passed, list not completed |
Parts delayed | Parts haven't arrived by the set ETA |
Payment gap | Invoice total doesn't match payment collected |
All alerts also post as system messages in the job's chat channel with a direct link back to the Kanban card.
β Admin Configuration
Before the pipeline goes live for your team, make sure the following are configured in CxC Settings:
Deposit percentage β set your company's required deposit amount. The system enforces state law minimums automatically based on job location
Sold threshold β the minimum estimate amount that qualifies a job for the pipeline, configured per job type in ServiceTitan
ServiceTitan integration β must be active for jobs to sync and cards to populate automatically