Question 1

What counts as an unresolved estimate?

Accepted Answer

An unresolved estimate is an estimate that was sent, viewed, or declined but has not become a booked job. JobHearth works from the estimate statuses you already have—draft, sent, viewed, approved, declined, expired, or cancelled—and does not treat an approved or cancelled record as a forgotten opportunity. A row with missing or unclear consent is unresolved for import review, not eligible for outreach.

Question 2

Can JobHearth follow up on every old estimate?

Accepted Answer

No. Recovery is consent-aware by design. An old estimate can be reviewed for recovery only when the imported record has a clear consent signal and a recognized status. Records without consent, with an unclear consent value, or that your team marks out of bounds stay out of the follow-up queue.

Question 3

How do consent and opt-out work?

Accepted Answer

JobHearth uses the consent signal recorded with each estimate and follows the customer’s channel preferences. If a customer opts out, replies that they are not interested, or your staff pauses the sequence, outreach stops. The goal is a useful check-in when it is welcome—not a system that keeps sending after someone has said no.

Question 4

What channels does JobHearth use?

Accepted Answer

JobHearth currently uses email follow-up only. Each message requires the appropriate permission path, and replies are treated as a handoff signal rather than ignored by automation. When a customer responds or shows buying intent, the sequence can pause so your team can take over with the estimate context in front of them.

Question 5

Is estimate recovery pushy or spammy?

Accepted Answer

It should not be. The recovery rhythm uses thoughtful check-ins, measured timing, reply detection, and an automation pause when a human conversation starts. You can stop a sequence, and your team gets the handoff instead of a customer being chased by an endless loop. The standard is simple: create a clear next step, then give people room to respond.

Question 6

How is recovered revenue attributed?

Accepted Answer

Recovered revenue is tied back to the estimate that was reactivated and the job outcome that followed. JobHearth documents the estimate reactivation, verifies the job outcome, and keeps the result in a shared attribution ledger. If a booking cannot be connected to a specific estimate and outcome, it is not presented as recovered revenue.

Question 7

What data does JobHearth store?

Accepted Answer

For an imported estimate, the current record includes the customer identity fields supplied in the import, estimate value, estimate date, status, consent signal, source row, duplicate key, import metadata, and the original imported row. Import metadata includes details such as the file name, row counts, whether it is sample data, and when it was created. The system uses that information to review duplicates and preserve the source context; this FAQ does not promise a retention period or security control that is not documented elsewhere.