Twitter Bot by Kore.ai for TELUS Business Connect Video
Twitter BOT, your Virtual Assistant.I am here to help you tweet, retweet, send a direct message, and receive tweets from the people
Twitter Bot App Integration with TELUS Business Connect Video
This bot lets users tweet, retweet, send a direct message, and receive tweets from the people they follow – with the power of chatbots, the simplicity of natural language, and the convenience of speech and text – all right within RingCentral team messaging.
To get started, you will need:
- An account with Twitter.
- Your user credentials.
To add the bot within team messaging, simply select “New Conversation” and enter the name of the bot, or search for the bot in “People” to add to an existing message thread. Once the bot is added, the bot will present you with a greeting. Prior to performing your first command, you will be asked to authenticate with the two items listed above. Once connected, message “help me” or “what can you do,” and the bot will provide you a list of tasks it can perform for you.
This bot is available as a free trial for one month. Questions? Contact us via Partner@kore.ai for pricing or help in setting up your bot
*Twitter logo and trademark are owned by Twitter, Inc.
- Self-serve with natural language ease to tweet, retweet, follow users, unfollow users, send direct messages, receive alerts, automate workflows, and more.
- Gain multi-channel convenience by completing tasks in one channel such as the desktop app or start in one and finish in another, such as mobile.
- Get instant visibility into new posts and activity.
- Follow up instantly using actionable, simple response options.
App Scope and Permissions
When authorized, this app will be granted the following permissions:
|Read Accounts||View user account information, e.g. name, business name, and contact info|
|Team Messaging||Post messages, as well as view, edit and delete Team Messaging related data|
|Webhook Subscriptions||Manage and subscribe to webhook notifications|
|Glip||Deprecated: TeamMessaging permission should be used instead|