Social Inbox

The Social Inbox is the Inbox tab of the Social Publisher. It gathers the comments, mentions and direct messages your connected accounts receive and lets your team read and answer them without leaving Gamosy.

It is not the same thing as Messages, the conversations between studios and creators inside Gamosy. This page is only about what comes in from social networks.

What the inbox reads

No other network is read yet.

• Bluesky reads messages only with an app password that has Allow access to your direct messages turned on. Without it, comments and mentions still arrive and the account's line says messages are not read; a member who manages the Social Publisher is also told what to update.
• Mastodon reads with the permissions granted when the account was connected. An account connected before the inbox existed may need one Reconnect, which the account's line offers, or, if it was connected with your own access token, a new token saved on Platforms with Update access token.
• Instagram reads the comments under the account's newest fifty posts, and only comments from the last ninety days. Direct messages and mentions are not read.
• YouTube comments are read with a Gamosy key, not your channel's login, so there is no consent screen to go through. Gamosy cannot answer YouTube comments yet; the conversation says so and offers Open on YouTube. YouTube's developer policies require every stored copy to be checked again or removed within 30 days, so a thread the inbox stops seeing on YouTube is removed here too. Reading shares one daily YouTube quota across Gamosy; when it is spent, the account's line says so and reading resumes after the daily reset. Nothing needs doing.
• WordPress reads the comments on the site's posts, pages and other content through the site's own REST API, with the application password the connection was made with, including comments still waiting for approval, which the inbox marks Awaiting approval. Spam, trash, pingbacks and trackbacks are not read.
• Discord reads, in the one channel the connection publishes to, the replies to the posts Gamosy published there and the messages in public threads opened from those posts. Direct messages and mentions are not read, and a file is shown only as the kind of file it was.

Turning it on

The inbox is off for every account until a workspace manager turns it on.

1. Open Social Publisher in your workspace sidebar and switch to the Inbox tab.
2. While nothing is on yet, the tab opens on Choose what the inbox reads: every connected account the inbox can read, with its status. Once an account is on, the same list sits behind the Manage button above the conversations.
3. Press Turn on next to an account. A dialog spells out what will be read from that account, how long Gamosy keeps it, and that turning it off later removes everything stored. Check the box and press Turn on the inbox.
4. The first check runs at once. New conversations appear in the list as they are read.

An account that needs a reconnect or a new app password shows it on its line. A member who manages the Social Publisher sees what to do there, with a Reconnect, Open Platforms or Try again button, depending on what needs doing; anybody else sees what is not being read and is asked to pass it on to a workspace manager. An account whose connection was disconnected only says Paused: reconnect it on the Platforms tab, or on Discord press Reinstall bot there, to read it again.

Who can do what

A member without the manage permission sees a short note under the conversation instead of the composer. If your studio limits members to particular games, each member sees only the conversations of the games they work on, plus the studio-wide accounts. In a game's view the account list shows that game's accounts; studio-wide accounts are read in the Studio view.

Reading and answering

The Inbox tab itself says how many conversations are open and unread, so you can tell from any other tab of the Social Publisher whether something is waiting. The number follows what you do in the inbox: opening a conversation, marking it read or resolving it takes it off the count, and marking it unread puts it back, as does reopening one that was never read. Each time the list loads, the number is read again, so what your teammates did shows up too. In a game's view the count covers that game's conversations.

The list opens on Unresolved. Switch to Unread or All, filter by network, kind (comment, mention or message) or assignee, and search senders, post titles and public comments. Open a conversation to read it in full; the Open on button in its header takes you to the original on the network.

Write an answer in the composer at the bottom. A public reply goes out under the connected account as a reply to the comment you picked; a message goes to the sender's chat. Resolve a conversation once it is dealt with, or assign it to a teammate.

Copy link in the conversation's header puts a link on your clipboard that opens that conversation directly. It is the clean form of this page's address: the address bar opens the same conversation while you have it open, but it also carries whatever else you were doing on the page.

A teammate who opens the link lands on the conversation if they can see it. If it belongs to a game they do not work on, if it has since been removed, or if it simply could not be loaded this minute, the inbox opens on the list and says which.

Check now and automatic reading

Every account the inbox is on for is read on its own schedule, every 15 to 30 minutes depending on the network. An Instagram account whose Meta notifications are arriving is read once an hour instead, because the notification brings the next read forward. Check now brings every account you may read forward and reads as many as fit in a few seconds; whatever is left is read within the next few minutes. Any member can press it. The button waits two minutes between checks and has a daily limit per workspace; after that the inbox simply keeps reading on its schedule.

How long Gamosy keeps it

Comments and mentions are kept for 180 days after they were posted and direct messages for 365 days, then removed automatically. If your workspace needs a different period, between 30 and 730 days, ask support. The text of a direct message is stored encrypted; the sender's public name and handle are not, because they are public on the network.

Turning the inbox off for an account removes every comment, mention and message it stored from that account, immediately; the record of the answers your team sent stays with the workspace. Nothing is deleted on the network. Delete integration on the Platforms tab removes the connection and the stored conversations together. Disconnect alone pauses the inbox for that account and keeps what it stored until it expires or you turn the inbox off.

When somebody asks Gamosy to erase what they wrote, everything stored from their account leaves every inbox, and nothing that account writes afterwards is stored. A conversation that is theirs, such as their direct messages, their mention of your account or a comment thread they started, goes with everything in it. On any other conversation only their messages go: other people's replies, the answers your team wrote, notes, labels and assignments stay, and their name comes off the conversation and off the notifications that named them. A conversation left with nothing in it from anybody but your team goes too, with the answers, notes, labels and assignment stored in it. A WordPress comment left without an account carries nothing the inbox can recognise its author by: on request it is deleted by hand, and a later comment under the same name is still read.

Answering needs a plan

Reading is part of every workspace. Answering from the inbox is part of the Social Publisher plan or the trial that comes with it. When neither is active, the composer says so and reading stays open.