Property facts, homeowner contact details, and consent evidence enter the CRM workflow.
OREVA CUSTOMER WEBSITE
Your public website should be part of your operating system.
Eligible OREVA plans can include a premium customer website that captures seller, property, contact, and showing interest directly into the correct OREVA tenant.
yourbrand.com
YOUR BRAND · YOUR MARKETYour next chapter starts here.
Search homes, explore neighborhoods, and request a personalized home value.
Get My Home Value →PUBLIC SITEVisitor inquiry
→OREVATenant resolution
→CRMLead created
Property discovery and showing interest arrive as relationship context, not a disconnected lead source.
Questions route to the correct tenant so the operating team owns the follow-up.
Branding, market focus, contact details, and custom domain shape the public experience.
Site identity resolves to the correct OREVA organization before a lead is created.
Website activity can continue into CRM, pricing, communications, marketing, and Métis.
FROM VISITOR TO WORKFLOW
A lead should arrive with context—not just a notification.
The public experience and the internal operating record stay connected through server-side tenant resolution.
01Visitor submitsHome Value, property, contact, or showing intent
02Site identity resolvesServer determines the owning OREVA tenant
03CRM lead is createdSource and available property context stay attached
04OREVA continuesFollow-up, pricing, communications, tasks, marketing, and Métis
Luxury presentation. Connected operations.
Editorial property presentationResponsive lead generationCustom customer brandingPlan-controlled entitlement
See it as a homeowner would.Live Website Demo