---
title: 12 recipes for real work
---


Each recipe starts with a small, reviewable version. Keep external changes on
**Ask first** until you have checked several results.

## 1. Triage an inbox with Pulse

**What you need:** Pulse, Gmail, Starter or higher.

1. Hire **Pulse** from **Browse colleagues**.
2. Connect Gmail and leave sending on **Ask first**.
3. Create a weekday routine: “Summarise messages that need me today. If
   nothing needs me, report nothing.”
4. Turn on **Only tell me when something needs attention**.

**Result:** a short inbox brief; replies remain drafts until you approve them.

![Pulse can own a scheduled routine while important changes wait in Needs you.](../assets/screens/2026-11/routines-routine-1440-light.png)

## 2. Collect receipts for the accountant

**What you need:** the Accountant, Gmail and Google Drive.

1. Hire **Accountant** and connect Google Workspace.
2. Ask it to find new receipt and invoice emails and prepare a Finance folder
   list.
3. Review each Drive change in **Needs you** before it is made.

**Result:** a reviewed receipt list and approved files in Drive. Automatic
Drive writes from a routine are not claimed here because that flow is not
confirmed.

![Needs you shows the exact connected-app change before it happens.](../assets/screens/2026-11/routines-home-1440-light.png)

## 3. Watch competitor prices

**What you need:** Rival Watch and the competitor URLs.

1. Hire **Rival Watch**.
2. Put the URLs and products to compare in **What the team knows about us**, on the Company page.
3. Turn on its Monday routine and request only changes from the previous run.

**Result:** a weekly change report; quiet weeks stay in history.

![A quiet routine keeps no-change runs in history without notifying you.](../assets/screens/2026-11/routines-routine-1440-light.png)

## 4. Turn website findings into Linear issues

**What you need:** Website Improver, Linear, Pro or higher for hourly checks.

1. Hire **Website Improver** and connect Linear.
2. Add the site and test areas to its instructions.
3. Turn on **Daily site check**.
4. Read the issue title, team and priority in **Needs you**, then select
   **Approve**.

**Result:** only reviewed findings become Linear issues.

![A routine action names the app, action and arguments before approval.](../assets/screens/2026-11/routines-desk-1440-light.png)

## 5. Answer online-shop customers

**What you need:** the **Shop** pack, product and policy files.

1. Hire the **Shop** pack from **Browse colleagues**.
2. Review its colleagues and leave its routines off while you add product,
   delivery and return facts.
3. Put the customer-care colleague on a public link.
4. Review visitor questions under **Team → Visitors**.

**Result:** public answers use only the sources you selected; difficult cases
hand off into your team.

![A pack detail shows every colleague and routine before Hire the pack.](../assets/screens/2026-11/catalog-pack-1440-light.png)

## 6. Let a clinic front desk answer visitors and hand bookings to you

**What you need:** a front-desk colleague, a public link, and approved clinic files.

1. Add current prices, opening hours and services as that colleague's public sources.
2. Turn on the public link and test those three kinds of question while signed out.
3. In its instructions, say: “Never confirm a booking. Ask for the request and
   hand it to me.”
4. Choose yourself as the hand-off. Review booking requests in **Needs you** or Slack.

**Result:** visitors get answers from clinic files; a person decides every booking.

![A public colleague answers from selected files and hands requests back to the team.](../assets/screens/2026-11/colleague-public-1440-light.png)

## 7. Prepare an agency client report

**What you need:** Client Reporting and the approved source files.

1. Hire **Client Reporting**.
2. Add the reporting period, metrics and writing style to its instructions.
3. Attach the source files in Ask and request the report.
4. Check the source cards and download the finished document.

**Result:** a client-ready draft whose figures can be traced to the supplied
files.

![The Ask start accepts a request and files in one message box.](../assets/screens/2026-11/get-started-02-home.png)

## 8. Review security before launch

**What you need:** a repository and Mayz; Pro or higher for a live test.

1. Choose **Mayz** above the message box.
2. Select the repository and the security review.
3. For a live test, review every setup line and use fake test data.
4. Confirm the setup, then read the report and evidence.

**Result:** a review report with findings, proof and next actions.

![The Ask, Code and Mayz switch opens the right start for a security review.](../assets/screens/2026-11/ysra-ask-1440-light.png)

## 9. Start a code change from Slack

**What you need:** Pro, Max, Team or Enterprise; Slack; a colleague with Code;
a repository.

1. Connect Slack and link your Slack identity.
2. Mention `@Ysra`, name the colleague and describe the change and check.
3. Approve a waiting hand-off in Slack if shown.
4. Open the Code thread in Ysra to review the diff and pull request.

**Result:** the request reaches the same workspace and controls as a web
request; you review code before merging.

![The Slack card confirms which Slack identity is linked to Ysra.](../assets/screens/2026-11/slack-01-link-account.png)

## 10. Fill a supplier web form

**What you need:** Pro or higher and a colleague allowed to use a computer.

1. Send the form URL, the approved values and the instruction “stop before
   submit”.
2. Watch each plain-language step in the live view.
3. Select **Take over to sign in** if the supplier requires an account.
4. Check the final screen, then approve the submit.

**Result:** the form is submitted only after your final approval; sign-in
details are typed by you and end with the computer session.

![The colleague's computer lets you watch, take over and stop.](../assets/screens/2026-11/computer-running.png)

## 11. Put a public FAQ colleague on your site

**What you need:** a colleague and approved FAQ or policy files.

1. Choose the colleague's public settings.
2. Select only the files visitors may use.
3. Turn on the public link and test it while signed out.
4. Add the link to your site and review **Visitors**.

**Result:** visitors ask without an account; you keep internal sources out of
the public colleague.

![A public colleague can answer a visitor without a Ysra sign-in.](../assets/screens/2026-11/avatars-public-light.png)

## 12. Ask for a nightly attendance check-in

**What you need:** a colleague and, optionally, a table with an attendance column.

1. Open the colleague's **Desk → Check-ins** and select **Add check-in**.
2. Ask “Were you present today?” and schedule it for the end of each workday.
3. Choose the colleague's journal or the attendance table as the destination.
4. Answer the first check-in from **Needs you**, Slack or Telegram, then confirm
   that the journal or table received it.

**Result:** one scheduled question records each answer in the place you chose.

![A check-in asks on a schedule and writes the reply to a journal or table.](../assets/screens/2026-11/outputs-desk-checkins-1440-light.png)

## Limits and troubleshooting

Each recipe uses the limits of its colleague, routine, app, chat connection or
computer. If a step is refused, open the message: it names the missing app,
waiting approval or plan limit. See [Wallet, plans and limits](../how-to/wallet-plans.md)
and [Approvals and control](../how-to/control.md).
