Twilio offers scalable, cloud-based communications for web and mobile apps. This includes the ability for companies to call, SMS, chat, or video conference without having to create a communications infrastructure on their own. Further, Twilio can track tasks, evaluate worker performance and availability, and gather event data that can be used to create historical analytics reports.
Millions of users globally rely on Atlassian products every day for improving software development, project management, collaboration, and code quality. Atlassian products include: JIRA Software, JIRA Service Desk, JIRA Core, StatusPage, Confluence, HipChat, Bitbucket, SourceTree, Bamboo, Cover, FishEye, Crucible.
Popular Use Cases
Bring all your Twilio data to Amazon Redshift
Load your Twilio data to Google BigQuery
ETL all your Twilio data to Snowflake
Move your Twilio data to MySQL
Bring all your Atlassian data to Amazon Redshift
Load your Atlassian data to Google BigQuery
ETL all your Atlassian data to Snowflake
Move your Atlassian data to MySQL
Twilio's End Points
Retrieve data about Twilio tasks that are part of your team’s workflow and filter those tasks using an array of fields including priority, assignment status and name. This data can be gathered from within Twilio or integrated from external sources and added to Twilio’s workflow.
Track each workspace event that occurs, including things like the creation of a new Twilio task, a worker being assigned to a task or a change in a worker’s activity status. You can use this data to both generate current analytics and store historical record data for future use.
Get data about your workers, including their activity, availability and relevant skills. This will help you both assign your workers the tasks that are most suited to their skill sets and ensure that those tasks are only assigned when workers are ready to tackle them.
Monitor a worker’s Twilio activity status and use it to determine whether or not to assign an open task to a specific worker.
Atlassian's End Points
Request information about your service desk instance, including its version number, how long the instance has been running and what build it is. Accessing this data will, among other things, allow you to more successfully integrate your service desk with other relevant data sources.
Create a customer entity in JIRA Service Desk by providing Atlassian with the customer’s name, email and display name. Then, use this data in other endpoints to track service requests for a specific customer or integrate it with customer service data from other sources to provide a more comprehensive view of a customer’s journey.
Retrieve data on organizations that are engaging with your service desk, including the organizations’ names, IDs, properties and associated users. Then, access this endpoint to track those organizations, their users and their service requests so that you can have a better understanding of your service interactions with them.
Track any and all customer service requests and get relevant data, such as the customer’s contact info, the reason for the request, and the status of the request (what step it is on in your customer service process). Use this data to evaluate how well your company is responding to these requests and/or monitor customer service trends.