SmileLineDocs
Lead capture

Intake review

Correct and acknowledge capture warnings without losing a lead or silently changing CRM data.

Intake review keeps a lead when a capture hook refers to a location, treatment, lead source, or other optional reference that SmileLine can no longer apply safely. You can correct the underlying record, then acknowledge the warning with an audited note.

Open issues appear in two places:

  • Today shows the five newest issues to roles that can update patients. The panel refreshes every minute and hides when nothing needs review.
  • Settings → Review queue shows the ten newest issues and totals by reason to owners and managers, on the Intake issues tab. (Submissions that never became a lead at all live on the neighbouring Unprocessed payloads tab.)

Understand the reason

ReasonWhat happened
Archived locationThe submission referred to a location that had already been archived.
Archived treatmentThe requested or default treatment had already been archived.
Archived lead sourceThe hook's configured lead source had already been archived.
Invalid optional referenceAnother optional capture reference could not be applied safely.

SmileLine still preserves the lead and its raw capture record. It does not revive or apply an archived definition.

Resolve an issue

Open the issue's reason link to inspect the relevant setting. The row also links to its capture hook and patient when those records are available.

Correct the patient, capture hook, or setting as needed. For example, choose an active default treatment on the hook.

Return to Intake review and click Acknowledge.

Optionally add a resolution note, then confirm the acknowledgement.

Acknowledgement never changes the patient, journey, capture hook, or vocabulary item. Make the correction first; acknowledgement only records that a staff member reviewed the warning.

Acknowledging an issue twice is safe: the first acknowledgement remains the resolution. Resolution notes are limited to 1,000 characters and the actor and time are retained for audit.

The queue API is documented under Intake review issues in the /reference.

On this page