Standalone AI tool, without an ExactEstate integrationEEva in ExactEstate
Knows your propertyRequires supplied information or a configured data connectionWorks from the property, household, unit and ledger data the user can access
Shows its workEvidence depends on available sources and connected toolsLets users open supporting ExactEstate records
Takes the next stepDepends on the actions supported by configured toolsBooks tours, opens work orders and drafts the next step through ExactEstate workflows
ComplianceProperty-specific answers require the relevant records, guidance and configurationAnswers from the property’s own contracts, programs, effective dates and policies
Acts as youAccess depends on integrations and the permissions grantedOperates within the signed-in ExactEstate user's permissions
Asks firstApproval behavior depends on the tool and configured workflowAnything consequential waits for your approval
Answers your phonesRequires a suitable voice or telephony integrationEEva Voice Agent answers leasing, after-hours, maintenance and voicemail calls on your property line
Your other toolsAvailable connectors and permissions depend on the providerWorks with ExactEstate tools and supported MCP connections
Your dataProcessing and retention depend on provider, plan and connectionsExactEstate access controls apply, and model processing follows the deployment and provider settings you choose
The comparison worth making is native context: can the assistant see the correct property records, respect permissions and complete the next approved step without manual handoffs?
Have a supported model provider you prefer? Bring your own API key and keep ExactEstate’s permissions and workflows.