Inbox and listening
Inbox and Listening are in the sidebar for the current brand. Comments and replies are stored for that brand only. A person who can open another brand does not see these rows there.
The worker fetches them. Fetch now on the inbox, and Fetch mentions on listening, do the same work without waiting for the next pass.
Filter by network, account, unread, and needs-reply. Open a thread to read it. An owner, admin, or editor can:
- Send a reply. Nothing is sent until you press Send.
- Mark the thread done.
- Assign it to a teammate who can see the brand.
Reply suggestions are off until an owner or admin turns them on for that brand. A suggestion is a draft in the reply box. It is not sent by itself.
Listening
Section titled “Listening”Save a phrase of 2 to 80 characters. The worker searches networks whose official API allows search. X recent search covers about the last 7 days, not the full archive. YouTube search finds public videos, not comments.
Each mention is labeled positive, neutral, or negative by a word list. That label is not a judgment of the person. The page summarizes the last 7 days.
What each network allows
Section titled “What each network allows”The inbox table says what this product will fetch. No official API means the API this app uses does not offer that feature. Another label means the API exists, but this connection or this server cannot use it.
| Network | What is fetched | What is not |
|---|---|---|
| X | Mentions and replies when the account granted tweet.read and the server may call X. A person sends a reply when tweet.write was granted. On pay-per-use, X only accepts a reply when the original author mentioned this account or quoted it. Keyword search uses recent search. |
Direct messages. X has that API, but this connection does not request dm.read or dm.write. |
| YouTube | Channel comment threads when youtube.readonly was granted and the server may call YouTube. Keyword search is public video search. |
Replies. YouTube can post one with comments.insert, which needs youtube.force-ssl. This connection does not request that scope. Community posts have no API. YouTube has no direct messages. |
| TikTok | Nothing inbound. | The Content Posting API does not list comments, send comment replies, read direct messages, or search keywords. The Research API is not connected. |
| Nothing inbound. | Comment and messaging permissions are not requested. There is no general keyword search. | |
| Nothing inbound. | Comment listing is a restricted Community Management API this app does not include. Messaging is limited to approved partners. There is no keyword search of public posts. | |
| Practice | Sample messages and mentions stored here. | Nothing is fetched from a social site, and there are no direct messages. |
Set X_HTTP_ALLOW_NETWORK=1 only on the machine allowed to call X. Set YOUTUBE_HTTP_ALLOW_NETWORK=1 only on the machine allowed to call YouTube. Leave both unset in development and in CI. Without the flag, the worker stores the reason and does not invent messages.
Who can do what
Section titled “Who can do what”Anyone who can read the brand can open the inbox and listening pages. Owners, admins, and editors can fetch, reply, mark done, assign, and save phrases. Owners and admins turn suggestions on or off.
An AI client with Read can use read_inbox and read_listening. Those tools do not reply or send. A first comment posted with a publish is still not built.