PowerAdvice Ops
For the PowerAdvice team · UAT only
Prepare voice-based article drafts, check content and images, review homepage choices, and find the right PowerAdvice guide.
Start with the result you need
Mention PowerAdvice Ops in the PowerAdvice channel, then keep follow-up replies in that thread. Name the article or page and the result you want. You can also choose a request on the app’s Home tab.
You can also start a conversation in this app’s Messages tab. The same UAT limits apply.
Try: “Check this UAT article’s images and publishing state.” Or: “Help me prepare an article from this file and identify the missing fields.”
The bot can read the conversation you direct to it. It cannot browse unrelated channels or private conversations.
CMS work
Platform operations
Draft with a saved voice
Bring an approved source brief and ask the bot to list the saved PowerAdvice voices in DraftlyPro. Choose a voice, review the generated article, and approve only the push to a UAT CMS draft. The bot must read the current CMS contributor and channel choices instead of guessing them.
A DraftlyPro delivery receipt does not make the article publishable. Check the saved CMS draft, fill any missing contributor or channel choice, and leave staging and publishing for a separate approved request.
Check the change
Work here stays in UAT. Staging and production are outside this bot’s scope, even when a guide describes them.
When a change needs approval, review its exact fields in the thread; the result is checked by reading the item again.
Use Slack’s Stop button to end a running request. Stopping does not undo work already completed. Ask for a fresh read before retrying a change whose result is uncertain.
Traffic and site questions
Share the UAT page, the time period, and what you noticed. Ask for a site or traffic check. The answer should name what was checked, when, and any data it could not read. Missing data does not mean there were no visitors.
Save a repeating check
Ask for a repeating UAT site, domain, or connection check. Include how often to check, your timezone, and when to stop.
Review the card, then choose Save check. Nothing runs until you save. The check only reads; it does not change the site. Changes and errors return to the same thread.
Use Pause check or Cancel check on your saved-check card to stop it. Slack’s Stop button ends the current request, not a saved check.
Bring the source
Attach a DOCX, PDF, PNG, JPEG, or a ZIP containing those files. Say whether you want a review or a CMS draft. Uploading a file alone does not create or save a draft.
The bot checks each format and scans files before use. The bot’s temporary copies are removed after use; your Slack uploads stay in Slack. Only safe file details and the action record remain in the bot’s records.
Your work record
Use the Slack thread for this request, approvals, and results. Ask for work history to check recorded laboratory summaries and their Slack links. Full messages, uploaded content, and DMs stay out of the project record. A summary does not prove that a CMS change succeeded.
If something stops
Send health for connection status or help for examples. Include the article or page link and what you expected to happen. Do not paste tokens, passwords, or verification codes into Slack.