Schedule the weekly status, then name the approver

On November 4, Smartsheet said a weekly project summary can be a recurring task. A product note the same day says the results are emailed once you have approved them. One sentence is the schedule. The other is who lets the email leave.

What the release says is available today

Smartsheet’s November 4 release, datelined Bellevue and announced at its ENGAGE 2026 conference, says new Agentic Workflows are available today. A plain-language request becomes a recurring task. The release’s examples are a weekly project summary, and a check on risks and dependencies. The release says the task runs on its own and delivers results to the right people. It also says teams still spend too much of the week on status reports, data checks, and project setup, and it gives no count of those hours.

The product note published the same day is the page that names the email. Its title is “Schedule prompts to run automatically.” In Smart Assist, or in a Smartsheet MCP-enabled AI assistant, you set times for prompts. The note’s three jobs are to summarize overdue tasks, identify at-risk projects, and roll up weekly status updates. The note says the results are emailed once you have approved them.

The note prints three availability lines. Environment: commercial US and commercial EU. Plans: Business, Enterprise, and Advanced Work Management. Subscription model: User Model and Legacy Collaborator.

What else shipped beside the status prompt

Two specialized agents are on the release’s “available today” list. The Integration Agent is not on that list.

The Creation Agent takes a plain-language goal and turns it into a working project, with sheets, dashboards, reports, and automations. The release says this is built in minutes, so new work starts the same day. That timing is Smartsheet’s description, not a clock someone else ran.

The Data Quality Agent reviews sheets and flags issues by severity, on demand or on a schedule. The release does not say those flags wait for the same approval email as a status rollup. Do not paste the product note’s approval line onto this agent.

The Integration Agent is early access, at the address the release gives, smartsheet.com/eap. It starts with GitHub, Zendesk, Airtable, and Monday.com. The release says customers pull data from those tools into Smartsheet by asking. A weekly status that works only if that agent fetches an outside tool is not the workflow marked available today.

Native connections marked available today are ServiceNow, Microsoft Dynamics 365, HubSpot, and Workday, with more releasing each quarter, the release says. A tool named only under early access is not on that list.

What the schedule does not decide

A recurring prompt can prepare the status. The November 4 pages do not say it closes the work, cancels the meeting, or sends on its own judgment.

Read the two send lines apart. The release says the workflow delivers results to the right people. It does not name an approver. The product note says the results are emailed once you have approved them. For the send, follow the note. For what is available today, follow the release.

The approval line is the product note’s description of the email. Write a person’s name against it before you set a time. A role with no person leaves the line blank.

Four lines before you schedule one

Use this on the one status note you rewrite by hand most often. It is a page you write. It is not a Smartsheet form, and it is not an account of a customer.

1. The sentence. One request, in wording the two pages already use. From the product note: summarize overdue tasks, identify at-risk projects, or roll up weekly status updates. From the release: a weekly project summary, or a check on risks and dependencies. Name the project the request is about.

2. The plan and the environment. One plan from the note: Business, Enterprise, or Advanced Work Management. One environment from the note: commercial US or commercial EU. The subscription on the note is User Model or Legacy Collaborator. If you cannot point to the line, do not schedule.

3. The approver. The name of the person who approves the email, because the product note says the results are emailed once you have approved them. A distribution list is not a name.

4. The boundary. The request stays on work already in Smartsheet. It does not need the Integration Agent. The release marks that agent as early access and starts the list at GitHub, Zendesk, Airtable, and Monday.com. If the sentence is false without one of those four, it fails this line.

Filled in as a form, not a real department: a launch list, on Enterprise, in commercial US.

• Sentence: Roll up the weekly status on the launch list.
• Plan and environment: Enterprise, commercial US, on a subscription the note names.
• Approver: your name.
• Boundary: the launch list is already in Smartsheet. The sentence does not ask for GitHub, Zendesk, Airtable, or Monday.com.

If line 2, 3, or 4 has no answer, leave the note as a meeting for another week. If all four have answers, schedule that one prompt. Not a second prompt, and not the Creation Agent, on the same day.

What to do this week

• Choose the status note you rewrite by hand.
• Check your plan, environment, and subscription against the November 4 product note.
• Fill in the four lines. Use only requests the two Smartsheet pages name.
• Schedule only when every line has an answer. Keep the approver’s name on your page.
• Read the first email before you add another schedule. Leave the Creation Agent and the Data Quality Agent for a later week.