Why bring X (Twitter) into a shared inbox
Answering DMs from the X app ties support to whoever holds the login. In a shared inbox the conversation has an owner, the history stays with the customer, and replies come from your brand account without sharing its password.
How X (Twitter) works in Frosvo
Account Activity webhook
Frosvo receives DMs through X's Account Activity API, using your app's keys with Direct Messages permission.
Room to explain
Replies up to 10,000 characters.
Team workflow
Assignment, notes, tags and saved replies, like every other channel.
Connect X (Twitter) in a few steps
In the desk: Channels → add X. Credentials are stored encrypted and never shown again in full.
- In the X developer portal, give your app Read, write and Direct Messages permission.
- Generate the account's access token and secret after setting that permission.
- Enable messaging, then register the callback Frosvo shows you as an Account Activity webhook and subscribe your account.
- Send your account a DM to test.
Replies on this channel can be up to 10,000 characters.
One inbox for every conversation
X (Twitter) is one of 13 channels that share the same inbox as your website chat. Website visitors can be answered first by the AI assistant, which hands over to your team with the reason. Messages from X (Twitter) go straight to the team, who work them with assignment, private notes and saved replies in the shared inbox, and see every earlier conversation on the contact’s profile.
Questions about X (Twitter)
Does Frosvo answer public replies and mentions?
No. The X channel covers direct messages to your account.
What access do I need from X?
An app in the X developer portal with Read, write and Direct Messages permission, and the account's access token generated after setting that permission.
Can several people answer the brand's DMs?
Yes. Everyone with inbox access can reply, and customers see the reply from your brand account.