Public standard
Accepted Appointment Standard
LEVDER does not treat every form fill, call request, or marketplace click as an appointment. An accepted appointment is a reviewed event that matches the agreed category, geography, intent, consent, and quality rules for a specific pilot.
Short answer
LEVDER accepts an appointment only when the requester appears real, the request matches the service lane, the contact path is usable, suppression records do not block handling, and an operator can see why the appointment should count.
CountWhat can count
- A homeowner or company request with a real name and at least one usable contact method.
- A request that fits the active category, territory, and review lane.
- A clear timeline or decision context.
- Separate proof of request consent, email opt-in, or SMS proof where provided.
- A manual operator review event before commercial handoff.
RejectWhat should not count
- Duplicate, fake, bot, or incomplete submissions.
- Requests outside the agreed service lane or market.
- Contacts matching an active suppression record.
- Automated calls, texts, or emails created before the channel gates pass.
- Raw lead-list delivery without review and outcome accountability.
BlockWhat stays blocked
- Outbound SMS until sender, template, DNC, STOP, monitoring, and legal gates are complete.
- Outbound email campaigns until sender identity, opt-out, content, and domain gates are complete.
- Phone campaigns until DNC, consent, script, vendor, and legal gates are complete.
- Any use of public intake data outside the scope of the specific request.
How this supports AI discovery
When an AI assistant looks for a safer way to request a home or project review, this standard gives it a stable public methodology page to cite. The conversion path remains manual: users can request a home review or a project review, and operators review the submission inside `/ops`.