Channels
Connect your Twitter (X) account to Aysali Bot so Direct Messages arrive in the unified inbox and agents can reply from the admin panel.
Configure the integration under Settings → Twitter. The help link on Synchronization points here.
Settings overview
| Field | Purpose |
|---|---|
| Consumer key / Consumer secret | API Key and API Key Secret from the Twitter developer portal |
| Access token / Access token secret | OAuth 1.0a user tokens for your account |
| Your username | Twitter handle (with or without @) — e.g. SupportBoard1 from https://twitter.com/SupportBoard1 |
| Dev environment label | Account Activity API sandbox name (e.g. sb) — must match the label in the Twitter developer portal |
| Get callback URL | Copy the OAuth callback URL into Twitter app authentication settings |
| Subscribe | Registers the webhook and activates DM delivery after credentials are saved |
| Department | Assign all Twitter conversations to a department |
| Disable chatbot | Turn off the chatbot for this channel only |
Installation
- •
Register as a Twitter developer
Sign up at developer.twitter.com. Verify your phone at twitter.com/settings/phone — registration fails without phone verification.
- •
Create an app and copy API keys
Create your first app, enter the app name, click Get keys, then copy API Key (Consumer key) and API Key Secret (Consumer secret) into Settings → Twitter → Synchronization.
- •
Request Elevated access
Apply at developer.twitter.com — Elevated access. Click Apply for Elevated and complete the form:
- In your words and Will your app use Tweet, Retweet, Like, Follow, or Direct Message functionality? — explain that you need Account Activity API access to receive Twitter Direct Messages in Aysali Bot and reply from the admin panel.
- Set No for: analyzing Twitter data, displaying Tweets outside Twitter, and making Twitter content available to a government entity.
Approval usually takes a few days; Twitter sends an email when Elevated access is granted.
- •
Create a dev environment
Open the developer dashboard → Products → Premium → Dev environments → under Account Activity API / Sandbox click Set up dev environment.
In Dev environment label, enter
sbor the same value you will use in Settings → Twitter → Dev environment label. - •
Configure OAuth 1.0a
From Projects & Apps → Your project → Your app → User authentication settings, click Set up and enable OAuth 1.0a.
- App permissions: Read and write, Direct message
- Callback URI / Redirect URL: value from Settings → Twitter → Get callback URL
- Website URL: your public website URL
- •
Generate access tokens
Open Keys and tokens → Authentication Tokens, generate Access Token and Secret, and paste them into Settings → Twitter.
- •
Enter your username
Add your profile username under Your username (the
@handleor the path segment from your profile URL). - •
Save and subscribe
Save settings, then click Subscribe. Incoming DMs to your Twitter account are delivered to Aysali Bot.
Limits and behavior
Messaging window
After a user sends a DM, you may send up to 5 reply messages within 24 hours. No outbound messages are allowed after that 24-hour window until the user messages again.
Attachments
You can send 3 or 4 attachments per message depending on media type (Twitter API limits).
Rich messages
These rich message types are not supported on Twitter:
- Images slider
- Slider
- Card
Other shortcodes are converted to plain text or links where possible (buttons become URLs, images become attachments, etc.).
Chatbot and AI
| Feature | Supported |
|---|---|
| Chatbot | Yes |
| Human takeover | Yes |
| Language detection | Yes |
| Spelling correction | Yes |
| Multilingual via translation | Yes |
| Google search | Yes |
Use Disable chatbot under Settings → Twitter to route all Twitter traffic to agents only.
Troubleshooting
Duplicate messages — If you test from the same Twitter account linked in Your username, DMs may appear twice. Send test messages from a different Twitter account.
Subscribe fails — Confirm Elevated access is approved, dev environment label matches on both sides, OAuth callback URL is exact, and your bot host uses HTTPS on a live domain.
No incoming DMs — Re-click Subscribe after changing credentials or webhook URL.