# Workflow Planning

### 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

![](/files/-MSj-fnt_mbFBRkbrmwY)

### 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. 

![](/files/-MSirPf_ktdx1IQIZTHG)

### 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. 

![](/files/-MSj6URl6X8nxHhrvM1Z)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.pushly.com/faq/workflow-planning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.