How Voceva Works: A Five-Minute Setup Guide for Estate Agent Websites

This is a practical walkthrough — what Voceva actually does when it is connected to a WordPress estate agent website, what it needs to generate a voice bite, and what the result sounds like. If you are evaluating whether to install it, this should answer the technical questions.

What Voceva needs to work

Voceva reads from your existing property listing pages. It does not require a separate data feed, a CRM integration, or manual input of any kind. It pulls from what is already on the page: the property address and postcode, the listing description, key features if you have them in a structured list, property type and bedroom count, and the asking price.

That is it. If you have those fields populated on your property pages — and if you are already on Rightmove or Zoopla you certainly do — Voceva has enough to build a voice bite.

The postcode does a lot of work. Voceva uses location data to add context that is not explicitly written in your description: walking time to the nearest station, nearby school Ofsted ratings, the character of the local area. The agent does not have to write any of that. It comes from the postcode.

The installation

Voceva is a WordPress plugin. Installation follows the same process as any other plugin: upload the zip file from the Voceva dashboard to the WordPress plugin directory, activate it, and enter your API key. That is roughly three minutes if you have done it before.

The plugin adds a Voceva block to Gutenberg — the standard WordPress editor your team probably already uses to manage listings. When you open a property listing post, you insert the Voceva block where you want the audio player to sit. Most agents put it just above or below the main photo gallery, or at the top of the description section.

The first time you save with the block in place, Voceva generates the voice bite automatically. It sends the page content to the Voceva API, combines it with the location data, composes a short script, and returns a rendered audio file. On a standard UK broadband connection, that generation takes around 20 to 30 seconds. The audio is then cached to the page — subsequent visitors just hit the play button and hear the file immediately.

What the voice bite sounds like

The default output is approximately 40 to 60 seconds of audio. The voice is a neutral British English voice — clear and professional without sounding synthetic in the way that text-to-speech tools did five years ago. It speaks to the buyer directly, in second person, and covers three things in order: the property itself, the key location context, and a close.

The script Voceva composes is not a verbatim reading of your description. It is a condensed, spoken version that prioritises the three or four details most likely to matter to a buyer in that property type and price band. A one-bed flat emphasises transport and tenure. A family home emphasises schools and garden aspect. The system has been trained on what actually drives enquiries, not just what agents typically write.

You can listen to the generated bite in the Voceva dashboard before it goes live on the page. If you want to regenerate it — because the description has been updated, or because you want to tweak the emphasis — you can do that from the plugin panel without touching any other part of the listing.

What happens when a listing changes

Price reductions, description updates, changes to available parking or leasehold status — these happen regularly. When the listing content changes in a way that affects the voice bite, you can regenerate it in one click from the listing editor. Voceva compares the new content to the cached version and flags if the change is significant enough to warrant a new audio file.

When the listing is removed from sale and marked as sold or let in your CMS, the audio player is hidden automatically. You are not left with a voice bite playing on a property that has completed.

Multi-branch and high-volume agencies

If you manage 40 or more active listings at any point, Voceva has a batch generation option. From the plugin admin panel, you can select all listings without a current voice bite and queue them for generation in one action. Voceva processes them sequentially, typically at around 90 seconds per listing including generation and caching. A 40-listing portfolio takes about an hour to voice-up from scratch — which you run once, then maintain with individual regenerations as stock turns over.

Voice bite data, including play count and completion rate per listing, is visible in the Voceva dashboard. That data is also accessible via the Voceva API if you want to pull it into a wider analytics tool or report it as part of vendor marketing reviews.

What you need before you install

Your property listings need to be standard WordPress posts or pages — the kind generated by any of the main estate agent WordPress themes or plugins (EstateGuru, WP Property, Easy Property Listings and similar). If your listings are built that way, Voceva will work with them without modification.

You need a Voceva account and an API key, which you generate from the Voceva dashboard after signing up. There is no minimum contract. You pay per voice bite generated, which means you can start with five listings and scale from there.

If you want to test it on a staging site before rolling out to your live property pages, Voceva supports that — the API key works on any domain associated with your account.