Echo — inbound social · in alpha
Beacon publishes. Echo captures the mentions, replies and quotes that follow — and links each one to the post that caused it, by the post’s own id rather than by guessing. Outbound and inbound on one timeline, per project, so an agency keeps every client’s conversation separate.
You open Echo from inside a project, beside Beacon — each project has its own sources, its own budget and its own captured posts, and they never mix.
Echo is in alpha, and it is running. It captures, classifies into topics, scores sentiment against each one, and links a reply back to the post that caused it. Add a source by typing any public X handle — there is no account to connect and no developer account to register. What is not built yet: a ranked reply queue, saved views, and a public link to share with a client. We would rather name those than let you find them missing.
Most listening tools match on text and hope. Because Beacon published the post, the Hub already holds its id — so “the replies our client’s launch caused” is a join, and the answer is exact rather than approximate. Anything Beacon published stays marked as yours; everything Echo captured is marked as theirs, and the two are never quietly blended.
Sources, settings, budget and captured posts belong to one project and do not mix with another’s. One project per client, which is how consultancies and agencies already work — and it means one client’s inbound conversation is never visible inside another’s.
A reverse-chronological list of replies is the network itself with extra steps. Echo opens on the topics people are actually raising and how sentiment is moving — and every number names the posts behind it, one click away.
No posting, no replying, no following, no contacting anyone. Echo has no write access to any social account, and that is a property of what it is rather than a setting you have to find and switch off.
A sentiment figure nobody can check is a number on a slide. Under Evidence, every topic and every trend opens into the posts that produced it — each one with its author, its unmodified text, a timestamp and a link back to the original. That is also what the network’s developer terms require, including on a link you share with a client, so it is not a thing that gets traded away for a tidier screen.
Reading costs money per post, so every project gets a monthly cap and a choice of what happens when it is reached: pause, or keep going and tell you. Two clients with very different volumes get very different caps, which is the point of it being per project.
Echo’s cost lands in the same place as everything else in the Hub — measured, attributed and visible before the invoice, not after it. Expect roughly $15–45 per brand per month at ordinary volumes.
A post removed on the network is removed from Echo within 24 hours. If access ever ends, the stored copy goes with it. Someone who deletes a post has decided something, and a tool that keeps quoting it has overruled them.
Echo is early. X is the first network, because it is the one Beacon already publishes to and therefore the one where the loop is exact. Other networks come later. Mentions arrive before replies and quotes do, and the analysis screens land after the capture does. When it is doing more than this, this page will say so — and until then it says this.