Recover missed calls, book more visitors, follow up on estimates, publish local proof, and see the KPIs that matter.

TradeVulcan logoTradeVulcan
Menu

Contractor workflows for the revenue leaks that cost booked jobs.

Calls, booking, estimates, reviews, proof, scorecards, AI voice, and CRM context.
Sign in
App Guides
Close Forge

Close Forge pipeline, run logs, and optimization

How to operate the Close Forge pipeline, read run logs and contact records, handle exceptions, and improve follow-up results over time.

Where the team works day to day

After Close Forge is live, the setup page is not the daily workspace. Owners and sales managers should use the Leads pipeline view to watch opportunities, clear exceptions, and understand whether follow-up is converting.

Close Forge builder with Pipeline button highlighted for opening the lead pipeline.
Use the Pipeline button from a deployment when you want to review the exact records created by that Close Forge deployment.
Close Forge pipeline showing captured, follow-up active, contacted, won, needs attention, lost, filters, and a result table.
The Close Forge pipeline combines stage totals, search, connector filters, record values, latest touches, and review actions into one command view.

Understand pipeline stages

StageMeaningOwner action
CapturedAn estimate or opportunity was captured from the CRM.Confirm the value and contact details look reasonable.
Follow-up activeA run or message is queued.Watch for replies and make sure queue volume is expected.
ContactedAt least one customer touch has been sent.Review reply quality and whether the next human action is clear.
Needs attentionA run, message, or step is failed, blocked, stopped, skipped, or missing information.Open the record drawer or run logs, then fix the setup, contact, or workflow issue.
WonThe estimate is sold, approved, accepted, booked, or manually marked won.Use this as conversion feedback and review whether follow-up helped.
LostThe opportunity is rejected, declined, canceled, or manually marked lost.Review patterns before changing copy or timing.

Use run logs and status labels

Close Forge run logs with customer rows, message previews, timestamps, sent and failed statuses, and provider notes.
Run logs show individual customer follow-up attempts, message previews, timestamps, statuses, and provider or workflow issues.
StatusWhat it meansNext action
QueuedClose Forge created the message or run and it is waiting for its scheduled time or send window.No action unless queue volume is unexpected.
SentThe message was successfully sent through the provider rail.Watch for replies and stage movement.
SkippedClose Forge decided not to send because a rule or stop condition applied.Open the reason. Skips are often correct for sold, duplicate, missing-contact, or opted-out records.
BlockedA guardrail prevented sending.Check compliance, suppression, contact quality, or commercial access.
FailedThe provider or workflow could not complete the action.Open the error, repair the cause, and test again.
StoppedThe run was intentionally ended by a stop condition or manual action.Confirm the stop reason matches the customer situation.

Review customer and contact records

TradeVulcan contact record showing contact info, CRM source, revenue, estimates, follow-ups, replies, related estimates, timeline, messaging history, and apps and locations.
Contact records provide the customer-level history behind Close Forge activity: CRM syncs, estimates, follow-up events, messaging history, locations, and related app activity.

Use contact records when a pipeline item needs context. A contact record helps answer: Who is the customer? Which CRM record created the estimate? Has the customer replied before? Is there a related estimate? Which TradeVulcan app touched this customer?

Use the record drawer for manual decisions

When you open a Close Forge pipeline record, the drawer shows stage, provider, option value, sold option, highest option, current workflow step, delivery status, messages, estimate options, line items, photos or attachments, and step history. Managers can move records to active, contacted, won, lost, archived, or clear a manual move without changing the CRM estimate status.

Optimization workflow

  1. Start with the exception queue. Failed and blocked records tell you whether setup, contact data, compliance, or template logic needs repair.
  2. Read skipped reasons before changing rules. A skip can be good if Close Forge protected a sold, duplicate, opted-out, or missing-contact record.
  3. Compare captured to contacted. If many records stay captured, check triggers, delays, send windows, and required contact filters.
  4. Compare contacted to won. If messages send but nothing moves, review copy, timing, estimate quality, and human response time.
  5. Review lost records monthly. Look for common objections: price, timing, financing, scope confusion, missing proof, or slow sales response.
  6. Tune one thing at a time. Change either copy, delay, eligibility, or review rules, then watch the next cohort.

Weekly scorecard

MetricWhy it mattersHealthy signal
Captured recordsShows whether the CRM source is feeding Close Forge.Matches the expected volume of open estimates.
Needs attention rateShows setup, data, provider, or workflow friction.Low and shrinking after first launch week.
Sent rateShows whether eligible records receive outreach.High for records with valid contact details and no stop conditions.
Reply rateShows whether copy invites customer response.Improves when messages are helpful and specific.
Won conversionShows whether follow-up helps recover revenue.Improves over the baseline unsold-estimate close rate.
Time to first touchShows whether follow-up happens while the visit is still fresh.Same-day where appropriate and inside business send windows.

Optimization tips for better results

  • Segment high-value estimates into human-reviewed paths.
  • Use proof or project context in email when the customer needs confidence, but keep SMS concise.
  • Keep first-touch timing close to the estimate while the visit is still memorable.
  • Do not add too many touches. More messages can reduce trust if the customer feels pressured.
  • When a customer replies, make sure a human responds quickly. Automation should create momentum, not replace sales ownership.
  • Use Close Forge Email Blast carefully for selected, eligible contact lists when the workspace plan allows it. Always preview the audience and exclude opt-outs.