Inbox
Every client’s enquiries in one queue
where
Messenger, Instagram, WhatsApp
One place instead of a shared password and a browser tab per client.
For marketing agencies
Inbox, publishing, ads and reporting across Meta, Google and TikTok — for every client, in your agency’s brand.
Join the waitlistEvery client gets a workspace holding their accounts, their conversations, their campaigns and their reporting — Meta, Google and TikTok connecting into the same place. You switch client, not tool.
Every client’s enquiries in one queue
where
Messenger, Instagram, WhatsApp
One place instead of a shared password and a browser tab per client.
Reply to the public as the client, and moderate what they leave
where
Facebook, Instagram, TikTok
You read the exact text back before it is sent.
Plan and publish across a client’s channels
where
Facebook, Instagram, Threads, TikTok
A calendar per client, not a spreadsheet shared between three people.
Build campaigns, creatives and audiences, and watch what they cost
where
Meta, Google, TikTok Ads
One console operates every client’s media buying.
The catalogues and feeds behind a client’s shopping ads
where
Meta and Google catalogues
Products, sets and feeds, with their health visible before a campaign runs.
What is being said about each client, gathered daily
where
Facebook, Instagram, Threads, TikTok
A morning brief on the conversation, not just the chart.
The deck, the PDF and the link, on each client’s schedule
where
Every connected channel
Built from the same data the rest of the workspace runs on.
Your people, on the clients they run
where
Every workspace
Access is granted per client, not one shared login the whole agency uses.
Each person set to the work they actually do
where
Across the roster
A community manager and a media buyer do not need the same screen.
Switch on only what a client has agreed to
where
Per client, per channel
What is off is not hidden from the screen — it is not connected at all.
what the workspace keeps
Daily, weekly, monthly, quarterly — whichever a client is on.
Pick a report type and a schedule for each client. Every one arrives as a deck, a PDF and a link they can open without an account.
35
Multi-year history, community management, message volume per platform, learnings and recommendations — each one a section you switch on for the clients who want it.
Turn a section on for one client and off for another. The report follows what that client actually needs.
Model
Every page answers one of five questions: how a number moved, what was said about your client, what a rival did, what came into the inbox, how a post performed. Around forty sections exist, each one written in advance, including what it does when the data is thin. A report can order those sections, leave them out, shorten them and write into them. It cannot invent one. Anything we do not already have becomes a request on our desk, not a surprise in your client’s deck.
Composition
Fifteen more reports those decks asked for and never got. Twelve of them are at least seventy per cent pages that already exist. Two need nothing new at all: one is four existing sections at summary length, the other is the same sections pointed at a single question.
Cadence
Cadence does not decide structure either. The quarterly executive summary is sixteen pages; the monthly it summarises is forty-two. Executive does not mean longer.
We produce all seven today. Each one is the same report assembled differently — other sections switched on, another rhythm, another reader — and every card below says what changes.
It reads what was said about your client that day, not the account statistics. A daily brief built from statistics alone is a page about yesterday’s reach, and no client has ever asked for that.
Competitor figures say how they were reached, on the slide itself, so nobody has to hunt for a footnote to know what they are looking at.
Send a client their report in either language, or both. The Arabic is written, not machine-translated — right to left, correct numerals, real typesetting. Switch this section over and read it.
The page turns around the same way your client’s report does — the same behaviour, not a demonstration built for a website.
2026-07-01 → 2026-07-31
Reach by day
Reach
1,204,880
+24.6%
Engagements
48,317
−3.4%
Engagement rate
4.01%
+0.8%
Reach by day
Live Meta data appears here once a connection is authorised.
And because both languages are written rather than translated, each is checked against the other. The Arabic and the English carry the same figures, or neither goes out.
A report is a thing your client keeps. It should look as though it came from you, and it should not look as though it came out of a generator.
Every piece of client data we hold carries the agency it belongs to, and every read is answered inside that boundary. There is no ordinary path through the product that returns another agency’s clients.
The separation is not a convention our own people can step around when it would be convenient. It is enforced on every read, including ours.
If the product is ever unsure which agency it is answering for, it refuses to answer at all. The worst you would see is a stopped page, never somebody else’s client on your screen.
A little administrative work has to see more than one agency — billing, support, a fault you have asked us to look at. It is a short fixed list, available to nobody outside it, and every use of one leaves a record.
The access your client gives us is encrypted on its own, and the thing that opens it is kept somewhere else entirely. It is tied to your agency and to that one connection, so a copy taken anywhere else opens nothing. If one record is ever exposed, that is one client’s access, not everyone’s.
What Meta granted and what you permitted are separate questions, and nothing runs unless both say yes. The permission is not a label in the interface — it is the thing that has to agree before anything happens. So “the agency never enabled this” and “the platform never did this” are the same statement.
Everything a connection can do is written out in plain language as a list of permissions. A new connection starts with reading on and every kind of writing off — no posting, no replying, no messaging, no spending — and it stays that way unless you turn something on yourself. Six of the twenty-one touch data about members of the public, and they are marked wherever they appear, because they carry obligations that reading a reach figure does not. Reading performance means aggregate numbers only, never individual people.
Connect a client’s accounts, put your team on them, and run the work from one place — messages, comments, publishing, campaigns and the reporting that comes out of it. Everything carries your agency’s brand, in English or Arabic, and nothing reaches a client until you release it.
Meta, Google and TikTok connect into the same workspace. Your client approves the accounts from a list, you set who on your team works on them and what each of them can do, and the reporting starts with the next period that closes.
Your client owns their business accounts, so the connection is theirs to approve. You send them one link that opens a page written for them, and nothing else.
Eight questions, and a person reads every answer.