{"_id":"58dc699c21742d0f00a74f1b","project":"5429beef1163360800ed31fa","parentDoc":null,"category":{"_id":"57a82c7aff9bd30e00a6f1c1","project":"5429beef1163360800ed31fa","version":"5429beef1163360800ed31fd","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-08-08T06:53:46.702Z","from_sync":false,"order":10,"slug":"client-support","title":"Client Support"},"__v":0,"version":{"_id":"5429beef1163360800ed31fd","__v":21,"project":"5429beef1163360800ed31fa","createdAt":"2014-09-29T20:19:59.904Z","releaseDate":"2014-09-29T20:19:59.904Z","categories":["5429beef1163360800ed31fe","55e74e1f5d36b32b002563fa","55e7500a73169617001f2e86","55e76b8196131b2f00bf4b72","55e89569cdbb8a350096df9c","55f8935eb089b71700a8364e","55f8a67d3bb4bb0d0022d093","55f9dbefc7ef770d00d9bf6d","5601c21a22ecf60d002b27b3","5601c21ff12aee0d001bb06e","5601c2256c7b610d00280db5","5601c22c22ecf60d002b27b4","5603738d0c78b00d0039af47","5626f70bfcbbc621004ebf52","566f7a1ae144ab0d00e9732f","566f85ca7820960d00c3b93d","56708ce43a32d20d00c45cbf","56708d436995210d003aad8e","5736471abe10a9200030732c","57a82c7aff9bd30e00a6f1c1","591b8500e3992319007190f4"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"user":"569d8ad30306a10d00ce9a1f","updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-03-30T02:12:44.777Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"**When you have a new Feature Request (Not a bug report), Just write an email to**\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"requests:::at:::adsnative.com\",\n  \"title\": \"TO\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"- Title of the email: A very short note about the feature request \\n(example: Custom report by Device Type)\\n\\n- Summary: One line summary explaining the feature request \\n\\n- Description: Explanations of the full feature requests. Provide examples, use cases and anything you feel is relevant. Impact of this feature on revenue/workflow etc.\\n\\n- Priority: Low, Medium, High, Urgent.\",\n  \"title\": \"Please use the following format for your email :\"\n}\n[/block]\nThe goal of this process is to establish a direct communication line between Client and AdsNative Product team so we can clearly understand the feature being asked for and the impact of the requested feature on client revenue/workflow etc. Once all the details are communicated, feature request sent by you will be evaluated by the Product team and they will respond as soon as possible. Of course, we are a small team and believe us that we will be putting our best to respond and keep you updated on the ticket status.\n\nGenerally speaking, feature requests (not bug fixes) must fit into our product roadmap. Due dates will be shared once we pick up the task into our product pipeline (which can take days, weeks or even months depending on our roadmap). If something is time-sensitive and does not fit into our immediate roadmap (i.e., it’s not a bug fix and also isn’t applicable to our broader customer base), we’d be happy to assess whether it could be expedited in consideration of our hourly engineering rate.\n\nAlso, if we need more information regarding the request you raised, our product team will reach out to you directly in reply to the email request you sent. Our product team will be the main POC for the feature request you have raised. So when you want to know the status about any feature that was requested, just respond on this dedicated email thread and you should hear back from us soon. Any questions you may have or our team has, will be communicated via the requests@adsnative.com channel. \n\nTrello Boards will be used only for day-to-day account management tickets and bug reports raised by Clients.","excerpt":"Steps to raise a new feature request with AdsNative Product team","slug":"client-feature-request-process","type":"basic","title":"Client Feature Request Process"}

Client Feature Request Process

Steps to raise a new feature request with AdsNative Product team

**When you have a new Feature Request (Not a bug report), Just write an email to** [block:callout] { "type": "info", "body": "requests@adsnative.com", "title": "TO" } [/block] [block:callout] { "type": "info", "body": "- Title of the email: A very short note about the feature request \n(example: Custom report by Device Type)\n\n- Summary: One line summary explaining the feature request \n\n- Description: Explanations of the full feature requests. Provide examples, use cases and anything you feel is relevant. Impact of this feature on revenue/workflow etc.\n\n- Priority: Low, Medium, High, Urgent.", "title": "Please use the following format for your email :" } [/block] The goal of this process is to establish a direct communication line between Client and AdsNative Product team so we can clearly understand the feature being asked for and the impact of the requested feature on client revenue/workflow etc. Once all the details are communicated, feature request sent by you will be evaluated by the Product team and they will respond as soon as possible. Of course, we are a small team and believe us that we will be putting our best to respond and keep you updated on the ticket status. Generally speaking, feature requests (not bug fixes) must fit into our product roadmap. Due dates will be shared once we pick up the task into our product pipeline (which can take days, weeks or even months depending on our roadmap). If something is time-sensitive and does not fit into our immediate roadmap (i.e., it’s not a bug fix and also isn’t applicable to our broader customer base), we’d be happy to assess whether it could be expedited in consideration of our hourly engineering rate. Also, if we need more information regarding the request you raised, our product team will reach out to you directly in reply to the email request you sent. Our product team will be the main POC for the feature request you have raised. So when you want to know the status about any feature that was requested, just respond on this dedicated email thread and you should hear back from us soon. Any questions you may have or our team has, will be communicated via the requests@adsnative.com channel. Trello Boards will be used only for day-to-day account management tickets and bug reports raised by Clients.