Daily Updates¶
How Prompts Work¶
Daylee sends daily prompts to each team member via direct message according to the team’s configured schedule. A prompt asks the member to share their standup update.
Prompt timing: Each member receives the prompt at the configured time in their own timezone (if they have set a timezone preference). For example, if the prompt is set for 9:00 AM, a member in New York receives it at 9:00 AM EST and a member in London at 9:00 AM GMT. Members without a timezone preference use the team’s timezone.
Reminders: If a member hasn’t submitted their update, Daylee can send a follow-up reminder. Admins can configure whether reminders are sent and how many minutes after the initial prompt (default: 60 minutes).
Members can submit updates at any time using the slash command or App Home, not only in response to a prompt.
Drafted Updates¶
When at least one task tracker integration (GitHub, JIRA, or Linear) is connected and your account is linked, Daylee tries to write your standup for you before the prompt arrives. The DM opens as a draft for you to review rather than a blank “what did you do today?” question.
Each draft is built from your own activity:
Recent activity in the standup window — commits, pull requests, issues, and comments since the last report. The draft is written in your voice, organized under each standup question.
In-flight tasks (fallback) — if there is no activity in the current window, Daylee looks back fourteen days for tasks that are still in progress (i.e., not in a “done”, “resolved”, or “cancelled” state) and frames them as work you’re continuing on.
Nothing to draft from (fallback) — if neither produces anything, the draft says plainly that nothing has changed since your last standup. You can still reply to add detail.
Detected blockers are always called out separately. Daylee surfaces:
GitHub pull requests with “changes requested” reviews
JIRA and Linear issues whose status or labels mention “blocked” or “blocker”
Daylee never invents work. If your tracker activity doesn’t support a claim, the draft won’t include it.
Reviewing a draft¶
The prompt DM with a draft includes four buttons:
Share It — submit the draft as-is. It becomes your standup update for the day.
Refresh — regenerate the draft from your latest tracker activity. Use this if a pull request landed or a ticket moved since the draft was first built. While regenerating, all buttons are removed and a refreshing status is shown. On completion the new draft replaces the old one and the buttons return. If regeneration fails, the previous draft is restored with a notice.
Edit — opens a form pre-filled with the draft so you can make changes directly.
Cancel — discard the draft and start from a blank slate. Your next reply is treated as a fresh update.
You can also reply to the DM in plain English instead of using the buttons. Daylee understands both confirmations and edit requests:
“lgtm”, “yes”, “share it”, “looks good” — submits the draft.
“add that I paired with Alex on the migration”, “drop the second bullet”, “mention the deploy is blocked on review” — Daylee applies the change and shows you the updated draft to review again.
“no”, “scrap it”, “cancel” — discards the draft so you can start over.
After sharing, the DM updates to show two buttons:
Edit — reopen the form to revise your update. You can edit as many times as you like until the report runs.
Withdraw — roll back your submission. For teams with Publish immediately enabled, the channel post is deleted. The draft returns to review state so you can edit and re-share.
Once the team report has been generated, buttons are removed and the update can no longer be changed.
When drafts don’t appear¶
The draft step is best-effort. The prompt falls back to the standard “Submit Update / Skip Today” message when:
No task tracker integration is connected for the workspace, or you haven’t linked your account in the Connections section of the App Home.
Draft generation fails for any reason (e.g., AI service issue).
You’re on Microsoft Teams — drafted updates are currently a Slack-only feature.
In those cases, submit your update using one of the methods below.
Submitting Updates¶
There are four ways to submit a standup update:
1. Reply to the DM prompt¶
When you receive a prompt from Daylee, reply directly in the DM. This is the simplest method — just type your update as a regular message.
You can also send a voice message instead of typing. Record an audio clip in Slack and send it as a DM to Daylee. The audio is automatically transcribed and processed as your standup update. Supported formats include M4A, MP3, MP4, OGG, WAV, and WebM. The maximum file size is 25 MB.
If your prompt arrived with a tracker-built draft (see Drafted Updates), your reply is treated as either a confirmation (“yes”, “lgtm”) or an edit instruction (“add Alex to the second bullet”) rather than a fresh update.
3. Use the slash command¶
Run /daylee update from any channel. Daylee sends you a draft DM and acknowledges the command with an ephemeral message. This works even if you haven’t received a prompt yet.
4. Use the App Home tab¶
Click Submit Update in the Quick Actions section of the App Home tab. Daylee sends you a draft DM and shows a “Check your DMs” confirmation.
Multiple Teams¶
If you belong to multiple teams, Daylee needs to know which team your update is for:
DM reply: If you reply to a prompt, the update goes to the team that sent it. If you message Daylee directly outside of a prompt thread, it asks which team you’re submitting for.
Slash command / App Home: A team selector appears first. After you pick a team, Daylee sends the draft DM for that team.
Editing an Update¶
You can edit a submitted update until the report is generated. To edit:
Click Edit in the draft DM — the form opens with your current update pre-filled.
Use Withdraw in the draft DM to retract your submission, then edit and re-share.
Or submit a new update for the same team via the slash command or App Home — it replaces the previous one.
Once the report has been generated and delivered, updates can no longer be edited.
Skipping a Standup¶
If you have nothing to report or want to skip a day:
Click the Skip button on the prompt message
Optionally provide a reason for skipping
Skipped updates are recorded in the report as “skipped” rather than “missed.” This lets the team know you intentionally chose not to submit rather than forgetting.
Missing Updates¶
If a member doesn’t submit an update and doesn’t skip, they are marked as “missed” in the report. The report includes a count of missed updates so the team has visibility into participation.
If reminders are enabled for the team, members who haven’t responded receive a follow-up reminder before the report is generated. See Standup Settings for reminder configuration.
Members who have set their availability to out-of-office are not prompted and are not marked as missing.