{"action":"created","issue":{"url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/22","labels_url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/22/comments","events_url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/22/events","html_url":"https://github.com/codeforamerica/project-ideas/issues/22","id":35195424,"number":22,"title":"Uproot: Reverse engineer phone trees into media-rich flow charts","user":{"login":"lippytak","id":2533112,"avatar_url":"https://avatars.githubusercontent.com/u/2533112?v=3","gravatar_id":"","url":"https://api.github.com/users/lippytak","html_url":"https://github.com/lippytak","followers_url":"https://api.github.com/users/lippytak/followers","following_url":"https://api.github.com/users/lippytak/following{/other_user}","gists_url":"https://api.github.com/users/lippytak/gists{/gist_id}","starred_url":"https://api.github.com/users/lippytak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lippytak/subscriptions","organizations_url":"https://api.github.com/users/lippytak/orgs","repos_url":"https://api.github.com/users/lippytak/repos","events_url":"https://api.github.com/users/lippytak/events{/privacy}","received_events_url":"https://api.github.com/users/lippytak/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/codeforamerica/project-ideas/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2014-06-07T01:19:21Z","updated_at":"2015-07-01T16:57:18Z","closed_at":null,"body":"**BLUF**: Uproot turns phone trees into media-rich flow charts\r\n**Link**: Brain dump below + motivating example at http://bit.ly/calfresh-uproot\r\n**Project Needs**: Everything (dev, design, research/user to seed good examples)\r\n**Status**: Pie\r\n\r\n==========================\r\n**Why?**\r\nPhone trees are one of the primary interfaces for gov. Especially for social services, where many clients don't have routine access to the desktop web. And especially *especially* for seniors, who prefer audio calls to anything else (source: Jake's stereotypes). The problem with most phone trees is that they suck. Here's what happens when you call the CalFresh service center:\r\n![2014-06-06 11 41 05](https://cloud.githubusercontent.com/assets/2533112/3207314/05a14550-eddc-11e3-8f5e-cb2fd8334a13.jpg)\r\n\r\nCleaned up a bit:\r\n[<img target=\"_blank\" src=\"https://cloud.githubusercontent.com/assets/2533112/3207345/d5b7c976-eddc-11e3-82ba-93c3e5c0f519.jpg\">](http://bit.ly/calfresh-uproot)\r\n(click img for interactive version with audio)\r\n\r\nLarge, complex, confusing phone trees are a horrible and disempowering user experience. The first step to fixing them is to **uproot** them and give them some fresh air #CitizenOnboardStyle.\r\n\r\nPLUS, Tim wants it!!\r\n![screen shot 2014-06-06 at 6 19 54 pm](https://cloud.githubusercontent.com/assets/2533112/3207419/ddeb4a46-ede1-11e3-9800-df37eb369ad4.png)\r\n\r\n**How?**\r\nI think Uproot could take one of a few paths:\r\n\r\n1. **Fully automated phone tree >> flow chart generator**\r\nThis would use Twilio + transcription service (MTurk would do) to automatically crawl through every path of a given phone tree and create a flow chart with node structure + audio segments + text. Input = phone number. Output = flow chart. Not sure if this is feasible. Definitely not feasible for trees that require custom user input (\"please enter your case number and press #.\")\r\n\r\n2. **Interactive web+Twilio UI to support building flow chart from phone tree**\r\nImagine typing a phone number into the web UI and clicking dial. Then a new node pops up as you hear the audio. You can type the transcription as you listen to the segment on repeat. Then you press a number to keep moving along and creating new nodes as Twilio saves the audio for you.\r\n\r\n3. **Generic media-rich flow chart**\r\nThink [Timeline.JS](http://timeline.knightlab.com/) for flow charts. Interactive, embeddable flow charts where every node is assumed to have media (audio, video, img, docs, etc.). This is almost certainly a separate project but it should exist anyway..."},"comment":{"url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/comments/117750698","html_url":"https://github.com/codeforamerica/project-ideas/issues/22#issuecomment-117750698","issue_url":"https://api.github.com/repos/codeforamerica/project-ideas/issues/22","id":117750698,"user":{"login":"daguar","id":994938,"avatar_url":"https://avatars.githubusercontent.com/u/994938?v=3","gravatar_id":"","url":"https://api.github.com/users/daguar","html_url":"https://github.com/daguar","followers_url":"https://api.github.com/users/daguar/followers","following_url":"https://api.github.com/users/daguar/following{/other_user}","gists_url":"https://api.github.com/users/daguar/gists{/gist_id}","starred_url":"https://api.github.com/users/daguar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daguar/subscriptions","organizations_url":"https://api.github.com/users/daguar/orgs","repos_url":"https://api.github.com/users/daguar/repos","events_url":"https://api.github.com/users/daguar/events{/privacy}","received_events_url":"https://api.github.com/users/daguar/received_events","type":"User","site_admin":false},"created_at":"2015-07-01T16:57:18Z","updated_at":"2015-07-01T16:57:18Z","body":"Neat! I do think decomposing the problem into:\r\n\r\n1. Phone tree traversal/mapping\r\n2. Audio processing\r\n\r\nis a good first step. I'm still struggling on how to implement (1) comprehensively."}}