Private review · Implementation checklist

A stronger homepage, with an honest launch gate.

This is a separate marketing concept. Mobve.com and customer voice routing are unchanged. Proposed prices, draft documents, and fictional data are clearly labeled.

Implemented for review

New homepage composition, Mobve blue/ink visual system, responsive navigation, and clearer product story.
English and Spanish voice-demo interface, interactive workflow examples, and fictional property context.
One compact pricing explanation and scoped quote.
Integration approach, onboarding, current/planned scope, trust, and FAQs.
About, contact, pricing, integration, security, privacy, terms, and accessibility pages.
Contact links open Mobve.com’s existing early-access form; this preview has no contact form or download.
Search metadata structure, noindex preview, no tracking, and keyboard controls.

Live voice activation

Read back the current approved Mobve voice settings using authorized Telnyx access.
Create a separate fictional-property assistant. Do not alter the Berrada assistant.
Attach only fictional knowledge. No customer tools, credentials, recordings, webhooks, or transfers.
Set explicit duration/concurrency/cost limits supported by the provider and verified data-handling policies.
Verify the voice matches and run English, Spanish, interruption, ambiguity, emergency, and failure tests.
Use an authenticated server WebSocket. No public unauthenticated widget URL. Verify browser audio, interruption, timed termination, and repeat-attempt rejection before public launch.

Owner decisions

Approve costs and commercial terms before treating proposed prices as an offer.
Supply permissioned customer evidence; do not publish invented testimonials.
Verify company identity, support channels, integration availability, and current capability claims.
Approve final legal language and call-recording/data practices.
Verify delivery through the linked production early-access form before public launch.

Public launch

Remove preview labels only after resolving their dependencies. Approve the exact revision, connect the production domain through the existing deployment process, replace noindex with canonical metadata and a sitemap, then verify production forms and provider paths. Publishing this review site does not authorize that step.