Work / Outreach
Marketing agent across Telegram, WhatsApp and email
Outreach was running across three platforms through three separate tools, each with its own copy of the audience. Aniverx replaced that with a single control room, so a campaign is written once and sent everywhere it needs to go.
At a glance
The problem they came with.
What was actually going wrong, before anything was built.
Three systems, three lists
Email, WhatsApp and Telegram each had their own tool and their own version of the audience. Keeping them aligned was a manual job, and manual jobs quietly go wrong.
Volume limited by a person
How many people a campaign reached depended on how much one person could send and track in a day, not on how many were worth reaching.
No single view
Nobody could answer what had been sent, to whom, on which channel, without opening three tools and reconciling them by hand.
What we built.
Described by what it does for the business. How it is put together is a conversation we are happy to have, but it is not what this page is for.
One place to launch from
A campaign is composed once and sent across all three channels from a single interface.
One audience, not three
The list lives in one place, so the channels cannot drift apart from each other.
Built to be changed
The flow is visible and adjustable by the team rather than locked away, so the campaign structure can change as the business does.
The results
What is different about the way this business runs now.
- A campaign now goes out across all three channels from one interface, written once.
- The audience is maintained once instead of three times, so the channels stopped disagreeing with each other.
- Sending volume is no longer capped by how fast somebody can copy and paste.
- The team can see what was sent, where, without opening three tools.
Three jobs kept in step by hand became one job, run from a tool the team already had open.
Other work like this
Is something in your business working like this?
Describe what is taking the time, and we will tell you whether it is worth automating, including when the answer is no.