Customers often send a direct message instead of an email. Bring them into the inbox.
What you need
- An X account and an app in the X developer portal.
- Owner or Channels permission in Frosvo.
Steps
- In the developer portal give your app Read, write and Direct Messages permission.
- After setting that permission, generate the account's access token and secret.
- Collect the API key, API key secret, access token, access token secret and the account's numeric user ID.
- In Frosvo go to Channels, click Add channel and choose X. Pick the website, name the connection and paste the five values.
- Click Save and check, then Turn on messaging.
- Copy the address from Steps to turn it on. Register it as an Account Activity webhook and subscribe your account to it. X signs requests with your keys and Frosvo verifies them.
- Send a direct message to your account to test.
What to expect
Direct messages appear as conversations from X in your Inbox. Reply there and the answer goes back as a direct message.
Common problems
- No messages arrive. The webhook may not be registered or your account not subscribed to it.
- Save and check fails. The tokens may have been generated before the permission was set. Regenerate them.
- Keys rejected. Copy them again without spaces. Saved secrets are never shown again in Frosvo, so paste fresh ones.
More help is in the troubleshooting guide. Other social channels: Instagram and Messenger. See the channels overview for the full list, and the inbox guide for answering.
Common questions
Why must permissions come first? Tokens created before the Read, write and Direct Messages permission was set do not carry it. Regenerate them after changing the permission.
How do I test it? Send a direct message to your account from another profile and look for it in the inbox.