> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow/client-requests/sending-a-client-request.md).
# Sending a Client Request
Send a client request from a checklist or from the requests dashboard: choose what to ask for, mark what you already have, and send the email.
You can send a client request in two ways:
* **From a checklist** on a job, household, opportunity or lead, when the checklist was added from a client request template.
* **From the requests dashboard**, with **New request**, when you want to put a request together on the spot.
## From a checklist
Add the checklist as usual with **Add Checklist** and choose a client request template. The client's steps and your team's steps appear in two groups, **Client** and **Team**, with a request bar above them.
All names shown are examples.
### Before you send: mark what you already have
Until the request is sent, each client step shows **To ask**. If you already have something, or the client doesn't need to do it, click **Not needed** on that step. The client won't be asked for it.
Changed your mind? Click **Ask for it** to put it back on the list.
Depending on the template, steps marked **Not needed** are hidden from the client or shown greyed out so they can see they've been handled.
### Send it
Click **Send to client** in the request bar. In the **Send to the client** window:
| Field | What it does |
| ----------------- | ---------------------------------------------------------------------------------------- |
| **From** | Who the email comes from. See [Who it comes from](#who-it-comes-from). |
| **Send to** | The people in the household who should get the request. Each person gets their own link. |
| **Cc (optional)** | Copy someone else, such as a colleague. |
Click **Send**. You'll see **Client request sent**, and the request bar changes to show when it was sent, when it's due, who it went to and how many steps are still open.
### The request bar
| Chip | Meaning |
| ------------------- | ---------------------------------------------------------- |
| **Not sent** | The request hasn't gone to the client yet. |
| **Sent** | The client has the link and is working through it. |
| **Client finished** | The client pressed **I'm finished**. Check what came back. |
| **Complete** | Every client step is done. |
The buttons on the bar:
* **Copy link**: copies the client's link, for example to paste into a text message.
* **View as client**: opens the client's page exactly as they see it.
* **Resend**: sends the email again, for example if the client can't find it.
### Changing a request on the job
You can tailor a request for one client, before or after sending it. These changes affect this job only; the template stays as it is.
| To… | Do this |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rename steps or change their order | Click **Edit list**, make your changes, then **Done**. |
| Add a step the template doesn't have | Click **Add item**. Fill in the step the same way as in the builder, then click **Add step**. With **One per client**, each person gets their own copy. |
| Change what the client reads under a step | Open the step and click **Edit text**. |
| Send a different link | Open a link step and click **Change**. Pick one of the template's links, **Another link…** to paste your own, or **Automatic** to go back to the template's choice. |
Steps you add after sending appear on the client's page straight away. No new email goes out, so let the client know if you need them to look.
## From the requests dashboard
The requests dashboard lists every form and client request for a household or for your team. Use the filter to show **Everything**, **Client requests** or **Forms**. The **To check** tab lists the requests with something waiting for you to review.
Click **New request** to put a request together in three steps.
### Step 1 of 3: What to ask for
* **From a checklist template**: choose a client request template. You can still add, remove or change steps for this send.
* **Describe it**: type what you need in plain words, such as *"last two payslips, latest super statement and a signed authority"*, and rubica drafts the steps for you to check.
### Step 2: Anything we already have?
Mark anything you already hold, so the client isn't asked for it.
### Step 3: Who, and the email
| Field | What it does |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **To** and **Cc** | Who gets the request. |
| **From** | Who it comes from. |
| **Due** | The due date the client sees. |
| **Email** | The email to use. The template's own email is chosen if it has one. |
| **Subject** | The email's subject line. |
| **Change the wording for this send** | Edit the email for this client only. The template isn't changed. Merge fields such as `{{FirstName}}` and `{{DueDate}}` are filled in when it's sent. |
Click **Send to client**, then **Yes, send** to confirm, or **Not yet** to go back. **Save without sending** keeps the request so you can send it later.
## Who it comes from
The email comes from the first of these that applies:
1. The sender set on the workflow stage that sent the request, if it was sent automatically.
2. The template's shared inbox, if its **Sent from** is set to **Shared inbox**.
3. The person in the template's **Sent from** role on the household, such as the adviser.
4. The owner of the job (or of its parent job).
5. You, the person sending it.
You can change it under **From** before sending. When the template uses a shared inbox, it appears first as **Shared inbox** and is already selected. Everyone else on the team is still listed if you'd rather send it as a person.
All names shown are examples.
Emails from a shared inbox don't add a personal signature. Reminders and **Ask again** emails come from the same sender as the request. To set up a shared inbox, see [Sending from a shared inbox](/workflow/client-requests/building-a-client-request-template.md#sending-from-a-shared-inbox).
### Show one team at a time
When the household has more than one pod, such as a financial planning pod and a lending pod, pills appear above the **From** list, one for each pod. Each pill shows the pod's team and its leader, for example **Lending · Sam Taylor**.
* **All** shows everyone. The window always opens on **All**.
* Click a pod to show only that pod's people.
* The shared inbox and you are always listed, whichever pill is selected.
* The person you've selected stays listed too, so changing the pill never changes who the email comes from.
All names shown are examples.
People who aren't in either pod, such as someone added to the household team by hand, only appear under **All**. If the household has one pod or none, there are no pills and you see the whole list.
With Lending selected: the shared inbox, the lending team and you. All names shown are examples.
The same pills appear when you send a workflow **Email** from a job, and in **Send Multiple Emails**.
## Reminders
If the template has reminders turned on, they go out automatically:
* only while the request is **Sent** or the client is still working on it,
* at most once a day,
* and they stop as soon as everything required is in, or when the client presses **I'm finished**.
The reminder email's subject starts with *A reminder:* followed by the request's name. See [Building a Client Request Template](/workflow/client-requests/building-a-client-request-template.md#reminders) to set them up.
## Next
* [What Your Client Sees](/workflow/client-requests/what-your-client-sees.md)
* [Reviewing What Comes Back](/workflow/client-requests/reviewing-what-comes-back.md)
