A Dot that sends your client the weekly report.

The job

Every Monday someone pulls last week's figures, writes them up for the client and sends them. It is the kind of standing responsibility a Dot is built to hold: OpenAI describes a Dot as an agent that keeps work moving between conversations, decides when to follow up and uses schedules when timing matters.

The part a Dot's own channels do badly is the hand-over. A Dot reports to you in ChatGPT, Slack or Teams, and your client is in none of those threads. Sending the report as a weekly attachment makes a new copy every week, and the client has to work out which one is current. So the Dot does not send anything. It updates one private page the client already has, and the client's bookmark keeps working.

What you need

• A Dot. OpenAI is rolling Dots out to Pro and Business Premium accounts first, and Enterprise workspaces can switch on the beta. What are ChatGPT Dots? has the plans and regions.
• The Stacktree plugin, installed from ChatGPT's plugin directory.
• A Stacktree account. Free is enough to try it; a weekly link that must not expire starts on Solo at $19 a month.

First-time setup

1. Install the plugin. Open Plugins in ChatGPT and search for Stacktree, or open its listing. Select Install plugin, then Connect, and sign in to Stacktree or create a free account. A Dot uses the plugins installed on your account, so there is nothing to set up on the Dot itself. On Business and Enterprise, your workspace admin decides which plugins members can install. Step by step.
2. Publish the first report yourself. In a ChatGPT chat, ask: "Write this week's report for Northwind as one HTML page and publish it privately on Stacktree, filed under the client Northwind." ChatGPT asks you to confirm, then gives you the link. Keep the stacktr.ee/p/ link: the Dot's prompt needs it. A link on your own domain will not work in the prompt.
3. Add the client's name, or an email gate. Pick one:
   • Their name. Ask: "Make a link to this page just for Dana Reyes." Send Dana that link. Every open through it comes back under her name. It opens without the page's passcode, so send it only to her, and revoke it on its own if you need to.
   • An email gate, on Solo and up. Ask: "Only let dana@northwind.com open this page." Dana confirms her address once with a link from her inbox, and her browser stays let in for 30 days. To have her opens named as well, add ?to=Dana to the end of the page link you send her. Do not also give her a named share link: a share link skips the gate.
4. Switch on comments if they are not on already: "Let readers comment on this page." Dana can then select a line and comment, with no account.
5. Send Dana her link once. It is the last link you send her for this report.

The prompt to give your Dot

Change the three things in square brackets: the page link from step 2, your sources, and the names. Leave the rules at the end in place; they keep the link the same and keep the Dot from writing to your client.

Every Monday at 9am, update Northwind's weekly report on Stacktree.

The page: [paste the stacktr.ee/p/ link from the first publish]
Who reads it: [Dana Reyes at Northwind]. She already has her link, and it must keep working.

1. Gather last week's figures, Monday to Sunday, from [the "Northwind weekly" Google Sheet, our Google Ads account and my email with Dana]. Compare each one with the week before.
2. Read the current page with get_site and keep its layout. Rewrite it as one self-contained HTML page: Northwind's name and the week at the top, a two-sentence summary, the key figures with the change on last week, what moved and why, and what we are doing this week.
3. Read the open comments on the page with list_feedback. Where this week's figures answer one, say so in the page.
4. Replace the page in place with update_site, using the link above. Never use publish_html for this report and never make a new link.
5. Resolve the comments this version answers with resolve_feedback, with a one-line note Dana will see.
6. Do not message Dana or anyone at Northwind. Tell me here, in five lines or fewer: that the page is updated, the two biggest changes, any comment still open, and when Dana last opened her link (list_share_links).

If a source is missing or a figure looks wrong, ask me before you change the page. If Stacktree refuses the update, tell me why and stop. Never switch off the safety scan, and never put passwords, keys or anyone's contact details in the page.

Two notes on the last step. When Dana last opened her link needs Solo, because open times are viewer numbers; on Free the Dot can say the page has been opened, not when. And if you used the email gate rather than a named share link, drop that part: her opens show on the page's screen in your dashboard instead.

The safety scan is the check Stacktree runs on every publish and update for things like API keys and email addresses. If a week's report trips it, you want to hear about it, not have the Dot turn the check off.

What the client sees

• The same link every week. Dana's bookmark opens this week's report, with no new email, attachment or version number.
• A page that opens in any browser and on any phone, with no ChatGPT account, no Stacktree account and nothing to install.
• No new prompts. Updating the page does not change its passcode or gate, so a reader who has got in is not asked again on that browser for 30 days.
• Comments on the page itself, when they are on. Dana selects a line and types. When the Dot answers it, she sees the note next to her comment.
• A private page. The link is unguessable, and published pages are never listed or indexed.

What you hear back

• The named open. On Solo and up, the first time Dana opens the link with her name on it, Stacktree emails you: "Dana Reyes opened" and the page title. That email comes once per link. Her later opens show on the page's screen in your dashboard and in the daily email when your pages have had activity. On Free, you get one email the first time the page is opened.
• Comments. When Dana comments, you get one email about five minutes after she stops, listing everything she left. The Dot reads the same comments the next Monday and answers the ones the new figures cover.
• The Dot's own note. Each Monday the Dot reports in its thread, in ChatGPT, Slack or wherever you told it to send updates: what changed, what is still open, and when Dana last looked.

Stacktree sends the emails, whichever agent updated the page, so they arrive the same way whether you, a ChatGPT chat or your Dot made the change. To have your agent read the opens each morning instead, see who opened it.

What we have run in ChatGPT

On 5 October 2026, the day before the directory listing went live, we ran the Stacktree plugin in ChatGPT Work, in the desktop app. We asked for a page for a named reader and got back a link with her name on it. We opened that link in a signed-out browser and left a comment, then asked ChatGPT to make the change. It updated the page at the same link, and the comment showed as addressed. That is the loop this recipe hands to your Dot.