top of page

I didn't automate our client's van listings. I hired an agent to do them.

2 minutes ago
5 min read

Thirty minutes, every single van


Our client Sinfin Campervans builds campers in Derby and sells them.


Every time one is finished, the same thirty minutes disappears. Write up the spec. Upload twenty-odd photos. Get it into the CMS. Draft something for the mailing list.

This is how a new van arrives. Emoji bullets, a wall of spec, a pile of photos.



Thirty minutes isn't the problem. The problem is they build a lot of vans, and the job always lands on the wrong day.


So I stopped treating it as automation and started treating it as hiring.


Automation is a set of rules you have to write. An agent is a colleague you have to train. Those are very different jobs, and that reframe is the whole reason this worked. If you want the background on the platform itself, we covered what Symphony actually does and what it doesn't a couple of weeks ago.


Dashboard interface displaying a team of nine agents with assigned roles and skills, visualized as icons in a circular arrangement, on a dark-themed background.

Give the client their own workspace


First thing I did was open a separate workspace for Sinfin.

Sounds trivial. It isn't. A workspace keeps agents, chat threads and files apart, so the Sinfin agent doesn't pick up its habits from another client's site. With 21 sites on the books, that separation is the difference between this being useful and being a liability.

One client, one workspace. That's the rule now.


Hire a CMS specialist, not a general assistant


Then I asked Maestro, the agent that coordinates the others, to build me a specialist in Wix CMS. Not "help me with my website". An actual role, with a job title. It's called CMS Guy and it sits in a team of nine, alongside a Wix Studio implementer, a marketing manager, a technical SEO agent, a content writer and a reviewer.


This is where most people go wrong with AI tools. They ask for everything and get mush. Ask for one narrow role and you get something you can actually rely on, working through a job step by step and reporting back when it's done.


Symphony task card showing CMS Guy completing each step of a listing job and marking it done

Make it learn the house style


A fresh agent knows Wix CMS in general. It doesn't know Sinfin. So I pointed it at the listings that were already live and told it to learn the format. The field structure. How the spec bullets are written. Where price goes. How the options list reads.


That's the step everyone skips, and it's the one that makes the output usable instead of generic. Don't tell an agent what good looks like. Show it twenty examples of good and let it work it out. It's the same principle behind the pump catalogue we restructured into two CMS collections, just pointed at a smaller job.


Connect the WhatsApp they already use


Here's the bit I'm most pleased with, and it's the least technical thing in the whole setup.

Sinfin don't want a dashboard. They don't want a portal. They want to do what they already do, which is fire me a WhatsApp with a wall of emoji bullets and a pile of photos. So I connected business WhatsApp to Symphony. I forward that same message straight through, and the work starts.


WhatsApp thread with Symphony showing the van advert and CMS Guy picking up the job

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 reg plate trick


Maestro hands the job to CMS Guy, and the first thing it does is read the registration off the number plate in the photos. Then it creates a folder in Wix Media named after that reg and files every image into it. When it can't make the plate out, it asks rather than guessing.

Look at the Crafter that's live right now.

The main image sits there as YM21..._24_Main_Photo.jpg. That isn't a naming convention I typed in for that van. That's the agent reading a plate and filing accordingly, every time, for every van.


Anyone who has inherited a Wix media library full of files called IMG_2847.jpg will understand why that matters more than it sounds.


Then it goes live


Photos in, fields populated, item created in the Cars collection, listing live. The Crafter it handled most recently: 2021, 2.0 TDI, MWB, four berth with pop top, 114,112 miles with service history, shower, night heater, solar, 41,999 pounds. All of it lifted out of a WhatsApp message and put in the right fields.


Wix CMS Cars collection showing the VW Crafter listing with its media gallery populated

A beige VW Crafter campervan with raised pop-top roof is parked on a brick street; four detailed thumbnails are shown below a large front-side view.

Updates land the same way


This is the part I didn't plan for and now wouldn't give up. Van sold? Sinfin WhatsApp the word SOLD. Price dropped? They send the new number. The listing updates there and then.

Stale listings are the 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 just stopped existing.


The newsletter drafts itself


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

Nothing hits a client's mailing list without a human looking at it first, and I'd say that to anyone selling you agentic AI with no approval step in it. The approval step isn't a limitation of the system. It's the reason you can trust the rest of it.


It didn't stop at listings


Once CMS Guy was working, the rest crept in:


  • A routine that reads the inbox first thing and says what's actually waiting on us, not how many emails arrived

  • One that flags orders paid for but not yet sent, oldest first

  • One that catches bookings waiting on confirmation before the customer gives up

  • A daily team meeting at 6am, which has now run 32 times without me being awake for a single one


None of that was the plan. It's just what happens once the agents know the business.


What actually changed


Thirty minutes down to about two, and the two minutes are me reading a newsletter draft on my phone. The Sinfin board currently reads 24 of 24 tasks done, nothing open, nothing overdue.


But the honest win isn't the time. It's that the job now happens on the day the van is finished, instead of the day I get round to it. That's what agents are genuinely good for. Not replacing the work. Removing the gap between the work being ready and the work being done, which is the same argument we made about not needing a developer every time you want to publish.

If you've got a job like this eating half an hour a week on one of your sites, drop us a line and we'll tell you honestly whether it's worth handing to an agent.



FAQs


Do I need a Wix site to use Symphony?

No. Symphony is a standalone platform and connects to plenty of non-Wix tools. But if your site is already on Wix, the CMS and Media integration is the bit that makes a workflow like this straightforward rather than fiddly.

The listing goes live automatically because we set it up that way and we trust the format. The newsletter always waits for approval. You decide where that line sits for each job.

Most of them are. Emoji bullets, half sentences, prices in the middle of a paragraph. The agent copes because it learned from real listings rather than a rigid template. When it can't read something, like a number plate it can't make out, it asks.

The workspace and the agent, yes. The part that takes experience is knowing how the client's CMS collection is structured and what learning the format should actually point at. That's usually where we come in.


Untitled design (20).png

Thanks for subscribing!

Are you curious about the latest WIX news?

Our newsletter will keep you up-to-date on all the latest WIX tips and tactics from Search Engine Land and other sources all over the Web.

 

Subscribe today.

Start your project with VISION:

bottom of page