> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strawberrybrowser.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routine best practices

> Design useful routines that trigger at the right time, avoid noise, combine related actions, and ask for approval.

Routines are most useful when they are narrow, event-driven, and clear about what counts as worth notifying you.

You do not need to start from a blank routine editor. After a chat handles a workflow correctly, tell the companion:

```text theme={null}
Do this workflow every Tuesday morning.
```

Ask it to collect the missing details before it creates the routine.

## Start with the trigger

Choose the trigger that matches the job:

* Daily routine for morning briefings
* Interval routine for frequent checks
* Cron expression for advanced schedules
* App trigger for events such as new email

## Combine related instructions

If multiple actions happen from the same trigger and share the same context, put them in one routine prompt.

Good:

```text theme={null}
When new emails arrive, identify receipts, extract amount and vendor,
save attachments to the accounting folder, and draft a note to my bookkeeper.
```

Less efficient:

```text theme={null}
Create one routine for identifying receipts and another routine for saving receipts.
```

Each routine execution runs its own AI call, so related instructions are often cheaper and easier to review in one routine.

## Define notification rules

Tell the routine when to notify you.

```text theme={null}
Notify me only when a customer email is urgent, a payment looks overdue,
or a reply needs my approval. If nothing needs action, delete the automatic chat.
```

## Keep routines scoped

Avoid routines that inspect every connected app without a reason. Scope by account, folder, label, channel, project, or keyword when possible.

## Use approval gates

For routines that can send messages or update systems, ask Strawberry to draft and notify first.

```text theme={null}
Draft the reply and notify me. Do not send until I approve.
```

## Review run history

Open `strawberry://routines/history` or a routine detail page to review run history. Use it to reduce noise, catch failures, and tune prompts.

If a routine improves after tuning, ask the companion to update the routine prompt or create a skill that captures the refined workflow.

## Good starter routines

* Daily calendar, email, and Slack briefing
* Weekly pipeline risk check
* Invoice and receipt forwarding
* Meeting follow-up drafting
* New lead deduplication and enrichment
* Competitor or target account monitoring