How we turned a WhatsApp message into a live Wix van listing

Thirty minutes, every single van

The founder of Sinfin Campervans was spending thirty minutes on every van. Write up the spec. Upload the photos. Get it into the CMS. Draft the newsletter. Every single time. He builds a lot of vans.

That's not an automation problem. It's a hiring problem.

What 30 minutes down to two actually means

The workflow we built gets a van listing live in about two minutes. The two minutes are reading a newsletter draft on a phone.

The honest win isn't the time saved. It's that the job now happens on the day the van is finished, instead of the day someone gets round to it. For a small Derby-based converter doing a handful of builds at a time, that's the difference between a listing that catches a buyer and one that arrives after they've already moved on.

“The honest win isn’t the time saved. It’s that the job happens on the day the van is finished, instead of the day someone gets round to it.”

Why ‘hire’ lands differently than ‘automate’

Automation is a set of rules you write in advance. An agent is a colleague you train. Those are genuinely different things.

A rule chain breaks the moment the input doesn’t match what you planned for. Real WhatsApp messages from a campervan builder are not clean data. They’re emoji bullets, half sentences, a price buried somewhere in the middle, and twenty photos fired in quick succession. A rigid rule chain falls apart on that. An agent trained on real examples copes: because it’s matching against a standard, not a template.

That reframe is the whole reason this worked.

One workspace per client

First thing: a separate workspace for Sinfin in Wix Symphony. One client, one workspace.

That sounds trivial until you’re managing 21 sites and an agent that’s useful for one client starts picking up habits from another. The workspace keeps agents, files and context entirely separate.

Hire a specialist, not a general assistant

We asked the coordinating agent to build a Wix CMS specialist. Not “help me with my website.” A specific role with a job title: CMS Guy. Part of a nine-agent team alongside a Wix Studio implementer, an SEO agent, a content writer and a reviewer.

This is where most people go wrong with AI tools. Ask for everything and you get mush. Ask for one narrow role and you get something you can rely on. Something that works through a job step by step, reports back when it’s done, and asks when it’s unsure.

“Ask for one narrow role and you get something you can rely on. Ask for everything and you get mush.”

If you want the background on how Symphony works as a platform, we covered what Wix Symphony actually does and what it doesn’t a few weeks ago.

Show it twenty examples, not a template

A fresh agent knows Wix CMS in general. It doesn’t know Sinfin. So we pointed it at the listings already live and told it to learn the format: the field structure, how spec bullets are written, where price sits, how the options list reads.

That’s the step everyone skips. Don’t tell an agent what good looks like. Show it twenty examples and let it work it out.

Why the WhatsApp connection matters

Sinfin don’t want a dashboard. They don’t want a portal. They want to do what they already do: fire off a WhatsApp with emoji bullets and photos.

So we connected business WhatsApp to Symphony. The same message gets forwarded straight through, and the work starts. No new tool for the client to learn. No training session. No “have you logged in yet” email three weeks later.

“The best client process is the one the client doesn’t notice you changed.”

The registration plate detail

Once the message lands, the Wix CMS agent reads the registration off the number plate in the photos. It creates a folder in Wix Media named after that reg and files every image into it. If it can’t make the plate out, it asks rather than guessing.

Anyone who has inherited a Wix media library full of files called IMG_2847.jpg will understand why that matters. The Crafter currently live on the site has its main image sitting as YM21..._24_Main_Photo.jpg. The agent read the plate and filed accordingly: every van, every time.

Photos in, fields populated, item created in the CMS, listing live.

Updates arrive the same way

Van sold? Sinfin WhatsApp the word SOLD. Price dropped? They send the new number. The listing updates there and then.

Stale listings are a quiet killer on any for-sale site. Someone enquires about a van that went three weeks ago, the client looks disorganised, and nobody ever tells you it happened. That problem stopped existing.

The newsletter that drafts itself

Once a listing is live, a newsletter draft appears: that van, its details, its photos, ready for the subscriber list. Draft, not sent. We read it, tweak a line, approve it.

Nothing hits a client’s mailing list without a human looking at it first. The approval step isn’t a limitation of the system. It’s the reason you can trust the rest of it.

The 6am meeting that runs without anyone being awake

Once CMS Guy was running, other things followed. A routine that reads the inbox first thing and reports what’s actually waiting, not how many emails arrived. One that flags orders paid but not yet sent, oldest first. One that catches bookings waiting on confirmation before the customer gives up.

And a daily team meeting at 6am. It has now run 32 times without us being awake for a single one. It pulls together what’s live, what’s sold, what’s in the pipeline, what needs attention: and has it ready before the working day starts.

None of that was the plan when we set up the van listing workflow. It’s what happens once the agents know the business.

What actually changed

The Sinfin board reads 24 of 24 tasks done, nothing open, nothing overdue. Thirty minutes down to two.

Agents aren’t good at replacing work. They’re good at removing the gap between the work being ready and the work getting done. That gap is where listings go stale, where enquiries arrive about vans already sold, where newsletter drafts sit untouched for a week.

“Agents remove the gap between the work being ready and the work getting done. That gap is where listings go stale.”

Close that gap and the business looks as professional as it deserves to be.

If you’ve got a job like this eating half an hour on one of your sites, drop us a line and we’ll tell you honestly whether it’s worth setting up a Wix CMS agent for it.

---

Frequently asked questions

Do I need to be on Wix to use this kind of agent workflow?

Not necessarily. Wix Symphony connects to plenty of tools outside Wix. But if your site is already on Wix, the CMS and Media integration is what makes a workflow like this straightforward. The van listing process works as cleanly as it does because the Wix CMS agent has direct access to the collections and media library.

Does the Wix CMS agent publish listings without anyone checking them?

The listing goes live automatically because that’s how we configured it for Sinfin. The newsletter always waits for approval before anything reaches subscribers. You decide where the approval gate sits for each part of the job. If the agent can’t read something clearly, like a number plate that’s obscured, it asks rather than guessing.

What if the WhatsApp message is messy?

Most of them are. Emoji bullets, half sentences, a price buried in a paragraph. The agent handles it because it learned from real listings rather than a rigid template. It matches against examples of what good output looks like, not a structured form. Genuinely ambiguous information triggers a question rather than a guess.

Could we set up a Wix CMS agent workflow for our own site?

The workspace and agent setup, yes. The part that takes experience is knowing how your CMS collection is structured and what the agent should learn from. Get that wrong and it produces something generic. Get it right and it produces something you’d have written yourself. That’s usually where we come in. Drop us a line to talk it through.