Pricing
A real-estate brokerage with one after-hours phone workflow should not be scoped like a multi-office team with several channels, CRM routing and custom integration requirements. Pricing is based on the workflow being implemented — not on an artificial one-size-fits-everyone package.
Which inbound channels Veilleur.studio is responsible for handling.
How many qualification paths, routing rules, business-hour behaviors and exception cases need to be configured.
Whether the deployment uses an existing supported integration or requires additional technical work.
Expected call or message volume, average conversation length and third-party usage components that materially affect delivery cost.
The level of workflow design, validation, monitoring and ongoing optimization required.
A contained first-response use case with defined channels, rules and success criteria. Best for teams that want to validate operational fit before expanding.
Broader inbound coverage with more routing logic, integrations and ongoing optimization. Best for teams that want a recurring first-response layer.
Multi-office, high-volume or technically complex deployments requiring additional integration, controls or operational design.
The U.S. product is entering a market where simple AI receptionist tools can be priced very differently from managed real-estate workflows. Publishing a low anchor before real U.S. usage and support economics are validated would create the wrong expectation. Standardized U.S. plan prices will be added once pilot data makes those prices durable, predictable and supportable.
Tell us where your leads arrive, what happens today and which systems your agents already use.