> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/faq/workflow-planning.md). # Workflow Planning Every organization is asking their teams to do more with less. Working with Pushly doesn't mean your team must log into the platform every time they send a Notification. Below are some options. ### Manual Platform Usage Most of Pushly's partners assign a user or users to leverage our easy-to-use platform for Notification deployment. Using the platform manually allows for rapid Notification deployment while getting quick access to A/B testing, in-line Segmentation, and various Delivery Strategies. While most features are still available via automation, our platform users enjoy experimenting with Segment mixes and content adjustments ![](https://810756845-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lry9Z27iWOZyQEGAgY7%2F-MSizsB1uk7QmJu14FHg%2F-MSj-fnt_mbFBRkbrmwY%2Fmanual.png?alt=media\&token=30fef031-7662-434d-a776-4b01e7f777cd) ### RSS Feeds Pushly has the ability to ingest any number of RSS feeds and deliver the content to the right audience. If you have multiple, categorized RSS feeds they can be assigned to individual [Segments](/platform/segments.md#attribute-definitions) created by your Account Manager. If you have only one feed which contains all your content, Pushly can deploy certain stories to the correct Segment based on the category tags and other factors. ![](https://810756845-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lry9Z27iWOZyQEGAgY7%2F-MSiiiufuSCVUz_9rb-X%2F-MSirPf_ktdx1IQIZTHG%2FRSS%20to%20Audience.png?alt=media\&token=8b9236be-3171-4102-bfd5-20ea03142c22) ### API/Automation and Manual Combination Many partners end up using a combination of the Pushly API and manual sending. In most cases, partners connect their CMS to the Pushly API for breaking news or urgent sends which need to go out as quickly as possible, across as many channels as possible. The API also supports Segmented Sending. Volume is then supplemented by manual platform usage which targets specific audiences, uses A/B testing, etc. ![](https://810756845-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lry9Z27iWOZyQEGAgY7%2F-MSj-jBKYjkF10roknzC%2F-MSj6URl6X8nxHhrvM1Z%2FCombo.png?alt=media\&token=9861ab97-06ed-489c-86aa-e29bd02d08d8) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.pushly.com/faq/workflow-planning.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.