Help center articles

Support writes it. Product and engineering confirm the steps.

One live article before it hits the help center. Agent connect updates a step the last release moved.

Set it up for your agent How agent connect works

livehelp/turn-on-shift-swaps.md

Turn on shift-swap approvals

Owner: Obi Nwosu. Product: Loomwright. Audience: account admins.

Help article for account admins turning on shift-swap approvals in Loomwright. Admins do this once per location. After the toggle is on, a manager can approve a swap in the mobile app.

Before you start

You need an account admin role. A manager cannot turn the toggle on, even for their own location.
Do this once per location. A second location does not inherit the toggle. Repeat every step at the next location, including the re-save. A manager at the second site will not see approvals until you do.
Managers see the approve action only after you re-save that location. The mobile app does not refresh itself.

Steps

Sign in as an account admin. A manager login does not show the Settings page where this toggle lives.
Turn the feature flag shift_swaps on.
Open the admin repo and edit config/features.yml.Open Settings, then Shift swaps, and turn approvals on.
Re-save the location. The toggle does not apply until you do, even if the switch already looks on.
Ask a manager to open one pending swap and confirm the approve button is there.

If it did not work

The manager is in the mobile app, not on the desktop schedule. The desktop page does not approve swaps.
The location was re-saved after the toggle. Saving before does not count.

feature flag

Imani Brooks

Admins do not know the word flag. This step should say turn on.

Obi Nwosu

Agreed. The article should sound like the product, not the repo.

config/features.yml

Sam Adeyemi

@agent step 3 changed last release, the toggle is under Settings now.

agent

Updated step 3. The toggle is under Settings, then Shift swaps.

resolved

Start with @agent to ask the agent

ResolveReply

Fictional example: a Loomwright help article in Gander, with a PM thread and a scripted agent connect reply.

How help articles get reviewed today

Writing the article in the help center itself is convenient, and it publishes a draft the engineer cannot comment on next to the sentence.

A shared doc collects the review and then someone retypes it into the help center. Chat reaches the engineer fastest and loses the step number by Friday.

The toggle moved

Obi Nwosu asks his agent for a help article on turning on shift-swap approvals in Loomwright. The agent writes help/turn-on-shift-swaps.md. Obi runs gander watch and sends the link to Imani Brooks and Sam Adeyemi.

Imani highlights the intro and says admins do not know the phrase 'flag'. She asks for plain words. Obi replies in the thread. The agent is not on it.

Sam starts a new comment: "@agent step 3 changed last release, the toggle is under Settings now." Obi's agent updates the step, replies, and resolves the thread. Imani sees Settings on the same link. The article goes to the help center after that.

Who's in the doc

WriterPMEngineerThe author's agent

Writer Support lead. Sends the draft before the help center.

PM Checks that a customer could follow it.

Engineer Checks the steps against the current build.

The author's agent Moves the step when the engineer uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit help center articles

Grok BotA first draft from the support brief, with agent connect through MCP.

CursorWhen the docs live in a repo, the engineer's session can hear agent connect through MCP.

Claude CodeSame repo path. MCP returns the comment to the session that can edit the article.

Confirm the steps on the live draft. Publish to the help center when engineering has had a thread.

See how it works on the homepage