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

# Tickets, reminders, alerts, and reports

> Move from an Ask Ellie answer to a ticket, reminder, alert, recurring report, or automation with explicit scope.

Depending on connected tools and workspace permissions, Ellie can help propose or perform actions such as creating a ticket, scheduling a reminder, setting an alert, or creating a recurring report.

## Read versus write

| Request                   | Typical effect                                       |
| ------------------------- | ---------------------------------------------------- |
| Explain a pull request    | Read-only                                            |
| Compare metrics           | Read-only                                            |
| Draft a ticket            | Produces text; no external write until created       |
| Create a ticket           | Writes to the connected project-management system    |
| Draft a Pulse             | Produces instructions or configuration               |
| Create or trigger a Pulse | Stores configuration or sends a report               |
| Set a reminder or alert   | Stores a future action and may send messages         |
| Trigger a fix             | Can create repository work, including a pull request |

## Safe action pattern

1. Ask for analysis.
2. Ask for a draft action.
3. Review destination, owner, recipients, schedule, timezone, and content.
4. Ask what permission and connector will be used.
5. Confirm only the intended action.
6. Open the destination system and verify the result.
7. Record or reverse the action if it is incorrect.

## Ticket example

```text theme={null}
Draft a Linear ticket for the active production pattern PATTERN_ID. Include the evidence, affected repository, proposed acceptance criteria, and owner suggestion. Do not create it yet.
```

After review:

```text theme={null}
Create the approved draft in LINEAR_TEAM and return the ticket link. Do not update any other items.
```

## Alert and report example

```text theme={null}
Draft a weekly Pulse for MANAGER in Slack at TIME TIMEZONE. Include projects over budget, agent context-health regressions, and active high-severity incident patterns. Do not schedule it.
```

Create the automation from [Pulse](/automations/pulse) after checking recipients and timezone.

<Warning>
  Free-form instructions can combine connected context with external actions. Use least-privilege connectors, narrow scopes, test channels, and human review for changes that affect source control, incident response, tickets, people, or spend.
</Warning>

## Verify and audit

For every write, capture:

* Requesting user
* Time and timezone
* Connector identity
* Destination
* Created or changed object
* Returned source link
* Confirmation or approval state
* Rollback or deletion path

If your workspace requires immutable audit logs, confirm the supported audit capability with Entelligence before relying on conversational history.

## Next step

Use [Automations](/automations/overview) for repeatable workflows or read [permissions and troubleshooting](/ask-ellie/permissions).