Handle your X direct messages in the same inbox as everything else
Direct messages sent to your X account arrive in Vera.Support, where you and your team answer them like any other conversation. The chatbot and human takeover work here too.
This is for you if people reach your business through X direct messages and you would rather not watch a separate app all day. The setup runs through the X developer portal, so allow a few days for approval before messages start flowing.
Step by step
Register and create your app
Register on the X developer portal. Verify your phone number before you start, because registration fails without it. Create an app, then copy the API Key (Consumer key) and the API Key Secret into Settings > Twitter.
Request Elevated access
In the developer portal, request Elevated access. Approval usually takes a few days and the answer comes by email. The rest of the setup only becomes available once you are elevated.
Set up the dev environment
Go to Products > Premium > Dev environments > Account Activity API / Sandbox and choose Set up dev environment. Use the label shown at Settings > Twitter > Synchronization > Dev environment label.
Configure authentication and the callback
Open App settings > User authentication settings. Activate OAuth 1.0a and set the permissions to Read and write and Direct message. Paste the Callback URI from Settings > Twitter > Get callback URL and add your website URL.
Generate your access tokens
In the Keys and tokens area of your app, generate the Access Token and the Secret. Paste both into Settings > Twitter.
Subscribe your account
Enter your X handle at Settings > Twitter > Your username and save. Then click Subscribe. New direct messages should now appear in your inbox.
Settings reference
| Setting | What it does |
|---|---|
| API Key (Consumer key) | The public key of your X app, used to identify it. |
| API Key Secret | The private half of the API key that authorises the connection. |
| Access Token | The token generated in your app's Keys and tokens area, used to act on your account's behalf. |
| Secret | The private counterpart to the Access Token. |
| Your username | The X handle whose direct messages you want to receive. |
| Dev environment label | The label you must enter when setting up the Account Activity API dev environment in the developer portal. |
| Get callback URL | Produces the Callback URI you paste into your app's User authentication settings. |
| Subscribe | Starts the subscription so messages sent to your handle reach the inbox. |
Good to know
You have 24 hours, and five messages
You may send up to 5 messages within 24 hours of the user's message. After 24 hours, nothing can be sent.
A live domain is required
This channel does not work from a local or offline setup. Your site must be reachable on a live domain.
Duplicate messages point to your own account
If messages appear twice, you are almost certainly testing from the account you synced. Write in from a different account instead.
Attachment and rich message limits
You can send a maximum of 3 to 4 attachments, depending on the media type. Image slider, slider and card rich messages are not supported.
Elevated access is the gate
The dev environment step cannot be completed until X approves Elevated access, so start that request early.
Your AI features carry over
The chatbot, human takeover and the AI features all work on X conversations, exactly as they do elsewhere.
Common questions
Why do I need Elevated access?
How long do I have to reply to someone?
Can the chatbot answer X messages?
Why am I seeing every message twice?
Which rich messages can I send on X?
Can I set this up on a test site?
Ready to end the chaos?
Unify your messages, automate the repetitive questions, and turn conversations into revenue — starting today.
Get Started