> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/requests/create-and-send-a-request.md).

# Create and send a request

Every option on the new request page, from recipients and reminders to language, export folder and the send dialog.

Click **New Request** at the top of the left sidebar to open **Create New File Request**. The page has two parts: the request itself, then a **Send Request** dialog for the subject, message and sending options.

Pipefile saves your work as a draft as you go. The status bar shows **Draft saved** when it's stored. Drafts are listed under **All Requests** > **Drafts**, and only you can see your own drafts.

## On the request page

### Recipients

Enter each recipient's name and **Email Address**. Names you've used before are suggested from your [contacts](/team-and-account/contacts.md).

* **Add CC Recipient** adds another person to the same request. Every recipient gets their own email and works on the same checklist.
* On plans with SMS reminders, each recipient also has a **Phone Number (Optional)** field (US and Canadian numbers). A recipient needs a name and either an email address or a phone number. See [SMS reminders](/reminders-and-notifications/sms-reminders.md).
* Each recipient card has a role label. Roles matter when a request includes a form to sign, because each signature field is assigned to a role. See [E-signature](/forms-and-esignature/e-signature.md).

### Reminders and expiration

* **Send**: how often Pipefile reminds recipients who haven't finished. Choose **Never**, **Everyday**, or every 2 to 7 or 14 days. The default is every 3 days.
* **Expires**: the date the request expires. The default is 30 days from today.

Reminders stop once the request is responded, completed or expired. See [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md) and [Expiration, completion and reopening](/requests/expiration-and-reopening.md).

### Tags (optional)

Type a tag and press Enter. Tags let you filter your dashboard later. See [Track and organize requests](/requests/track-and-organize-requests.md).

### Checklist or open-ended

Choose **Checklist** to ask for specific documents one by one, or **Open-Ended** for a single upload link with no list. See [Build your checklist](/requests/checklists-and-sections.md) and [Open-ended requests](/requests/open-ended-requests.md).

### Encryption key

If you've added more than one PGP key, an **Encryption Key** menu lets you pick which key encrypts this request's uploads. You can't change it after sending. See [Use your own PGP key](/security/pgp-keys.md).

## The Send Request dialog

Click **Next**. Pipefile checks that every recipient is complete, then opens **Send Request**.

| Field                                | What it does                                                                                                                                                                                                                                                                         |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Subject**                          | Required. The title recipients see in the email and on the request page.                                                                                                                                                                                                             |
| **Message - Optional**               | A note shown to recipients.                                                                                                                                                                                                                                                          |
| Export destination                   | If you've connected cloud storage, click **Choose Folder** to pick where this request's files are exported. Automatic export needs the Professional or Enterprise plan. See [Cloud storage integrations and auto-export](/reviewing-and-exporting/cloud-storage-and-auto-export.md). |
| **Advanced** > Language              | The language recipients see. See [Send requests in another language](/requests/translations.md).                                                                                                                                                                                     |
| **Advanced** > Notification Sequence | Which reminder emails to use. **Default Sequence** uses Pipefile's standard emails. Appears once you've created a sequence.                                                                                                                                                          |

Click **Send Request**. Recipients get an email (and a text message, if you added a phone number and your plan includes SMS). The confirmation shows the request link, so you can also share it yourself.

To reuse this setup, click **Save as Template** in the same dialog. See [Create and edit templates](/templates/create-and-edit-templates.md).

{% hint style="warning" %}
On the Free plan you can have one active request at a time. If you've reached the limit, Pipefile shows **Account Limit Reached** instead of sending. See [Plans and features](/getting-started/plans-and-features.md).
{% endhint %}

## Edit a request after sending

Open the request and click the **Edit request** (pencil) icon. Make your changes, click **Next**, then **Save Request**.

* If a change would remove documents your recipient has already uploaded, Pipefile warns you first. Download anything you need before you click **Save**.
* If you move the **Expires** date of an expired request into the future, the request reopens.
* Completed and archived requests can't be edited. Reopen them first.

## Related

* [Send from a template](/templates/send-from-a-template.md)
* [Bulk send](/requests/bulk-send.md)
* [AI Assistant](/ai-assistant.md)


---

# 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://support.pipefile.com/requests/create-and-send-a-request.md?ask=<question>&goal=<user_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.