# Plan your day automatically (/use-cases/team-ops/day-planner)



Copy this prompt to start your first task:

<Prompt>
  Set up a teammate that scans #general and #team each morning for commitments like people saying they'll send something by, merges them with my fixed events into one brief, and tells me plainly if today doesn't actually fit the hours I have.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Set up a teammate that scans #general and #team each morning for commitments like people saying they'll send something by, merges them with my fixed events into one brief, and tells me plainly if today doesn't actually fit the hours I have.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

Planning your day automatically means hiring a teammate that scans channel activity for commitments, merges them with your fixed events and priorities into a single morning brief, and says plainly when a day doesn't actually fit — naming what to delay, shorten, or cut. Every evening, it checks today's plan against what actually happened and carries anything unresolved into tomorrow's brief with context, so nothing slips through unnoticed.

<Callout type="info">
  It surfaces recommendations and tracks what slipped, but it doesn't rearrange your schedule for you. You still make the call.
</Callout>

## How to use this workflow [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a day planner [#hire-a-day-planner]

    Open **AI Teammates** in the sidebar, click **Hire AI Teammate**, and pick the **Senior Project Manager** template. The default bio is generic day planning. Replace it on the Profile step so it knows this job means scanning for commitments, checking the plan against real available hours, and carrying slipped items forward:

    <Prompt>
      You're our day planner. Every morning, scan #general and #team for commitments since the evening before, phrases like I'll send that by... or let me look into..., and merge them with fixed events and priorities into one brief. Check the plan against my actual available hours and say plainly when it doesn't fit, noting what to delay, shorten, or cut. Every evening, compare today's plan against what actually happened and carry anything unresolved into tomorrow's brief with context.
    </Prompt>

    Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/project-manager&#x22;, name: &#x22;Senior Project Manager&#x22;, bio: &#x22;You're our day planner. Every morning, scan #general and #team for commitments since the evening before, phrases like I'll send that by... or let me look into..., and merge them with fixed events and priorities into one brief. Check the plan against my actual available hours and say plainly when it doesn't fit, noting what to delay, shorten, or cut. Every evening, compare today's plan against what actually happened and carry anything unresolved into tomorrow's brief with context.&#x22; } }" />
  </Step>

  <Step>
    ### Tell it where to watch for commitments [#tell-it-where-to-watch-for-commitments]

    Add the teammate to #general and #team first. It can only read channels it's a member of.

    <Prompt>
      Scan #general and #team channel activity since the evening before, listening for commitment language: “I'll send that by...”, “let me look into...”. Track each one with a due date.
    </Prompt>

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Senior Project Manager&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Scan #general and #team channel activity since the evening before, listening for commitment language: \&#x22;I'll send that by...\&#x22;, \&#x22;let me look into...\&#x22;. Track each one with a due date.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;Scanning #general and #team since yesterday evening for commitment language, things like 'I'll send that by...' or 'let me look into...', and logging each one with a due date so nothing said in passing gets lost.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Turn the daily cycle into an automation [#turn-the-daily-cycle-into-an-automation]

    Open **Automations** in the sidebar, click **Create via Chat**, and pick this teammate in the New Thread composer that opens:

    <Prompt>
      Every morning, merge the fixed events I've posted in this channel, priorities, and open commitments into one brief. Check it against my actual available hours and say plainly if it doesn't fit. Every evening, compare today's plan against what actually happened and carry anything that slipped into tomorrow's brief.
    </Prompt>

    <LivePreview component="NewThread" scenario="{ populated: false }" />
  </Step>
</Steps>

**Nothing here needs your approval:** this teammate only reads channel activity and posts the brief to a channel — it never touches anything outside Helio, so nothing it does is irreversible. See [Control](/ai-teammates/control) for what does pause for sign-off.

## Tips for Better Results [#tips-for-better-results]

| Tip                                                      | Description                                                                                                            |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Add the teammate to every channel it should scan         | It can only read channels it's a member of — #general and #team (or whichever channels you use) need it added first.   |
| Give it your real available hours, not an ideal calendar | The "doesn't fit" check only helps if it's checking against the hours you actually have, not a wishful full day.       |
| Let the evening slip check run every day                 | Carrying unresolved items forward with context only works if it runs every evening, not just when you remember to ask. |
| Treat the brief as a summary, not a scheduler            | It surfaces what to delay, shorten, or cut — you still decide and move things yourself.                                |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="Does it rearrange my schedule automatically?">
    No. It surfaces recommendations — what to delay, shorten, or cut — and tracks what slipped, but you still make the final call and move things yourself.
  </Accordion>

  <Accordion title="Which channels does it scan for commitments?">
    Whichever channels you add it to, for example #general and #team. It can only read channels it's a member of.
  </Accordion>

  <Accordion title="What happens to something that doesn't get done?">
    The evening slip check compares today's plan against what actually happened and carries anything unresolved into tomorrow's brief with its original context, instead of dropping it.
  </Accordion>

  <Accordion title="What does the morning brief actually contain?">
    One digest combining a summary, fixed events, priorities, and open commitments — instead of several scattered pings.
  </Accordion>

  <Accordion title="Does this need my approval to run?">
    No. It only reads channel activity and posts the brief, so this flow runs on its own. See [Control](/ai-teammates/control) for what does pause for sign-off.
  </Accordion>
</Accordions>

<Cards>
  <Card title="Team Ops" href="/use-cases/team-ops" description="Back to the Team Ops use case overview." />

  <Card title="Triage support tickets" href="/use-cases/team-ops/support-triage" description="Answer routine tickets, escalate the rest with context attached." />
</Cards>