How to ask Nexus

What it does

Nexus works out which piece, post, field or link you mean from the words you use. The more exact your reference, the less it guesses and the fewer follow-up questions it asks.

Ground rules

• Work in the client's own channel. Once the channel is pinned, Nexus knows the client and you never need to name it.
• Review in the dashboards, not Slack. Drafts, calendars and posts live in the dashboard links Nexus posts. Slack is for asking and approving. If you want a Google Doc, ask for one.
• Edit the one thing that's wrong. Change a title, a meta description or one section without redoing the article. A full re-draft is slow and throws away your edits.
• One request for many items. "Move these 6 pieces to these dates" or "rotate these 3 authors across October" is one message. Don't ask piece by piece.
• Nexus remembers rules you state. "Never mention pricing in any blog" is stored as a guardrail and applied to every future piece.
• Previews are not changes. Bulk changes show a preview first. Nothing changes until you reply "yes" or "confirm". Check the dashboard afterwards.

Use it

Name the piece by its exact calendar title, or by its date

Nexus finds a piece in this order: its ID, then its exact title, then its publish date, then a unique part of the title.

• Best: copy the title from the calendar dashboard and paste it: "Write the blog [title]."
• Also good: the planned date, written as a full date: "Write the blog planned for Oct 20." or "Move the piece on 2026-10-22 to Oct 27."
• If two pieces share a date, give both: "the Oct 20 piece about downtime."
• Use the current title. If the title was renamed, use the new one.
• Avoid "the downtime one", "that blog from last week" or "the next one". They match several pieces or none.
• If Nexus answers "did you mean…?", pick one of its options. Don't let it create a new piece: a slightly different title is how duplicates happen.

Use real dates, not relative ones

• Say "Oct 20", not "next Tuesday" or "in two weeks". Nexus doesn't reliably turn weekday names into dates.
• For a range: "the posts from Oct 14 to Oct 21", not "this week's posts".
• For a cadence: "Mon, Wed, Fri starting Oct 19."

"Blog" and "post" mean different things

Say which social dashboard, and the author

• Plain "social" or "social post" means Company Social: the company's own LinkedIn page, Instagram, Facebook and Google Business.
• For an author's personal LinkedIn, say "Thought Leadership" and name the author: "Draft Jane's Thought Leadership post planned for Oct 21."
• Name the platform when it matters: "the Instagram post on Oct 20", not just "the Oct 20 post". Several channels can share a date.

Name the field, section or image you want changed

• A field: "Rewrite the meta description of [title] to lead with cost savings." This also works for the title, slug, excerpt, subtitle, author and category.
• A section: "Revise [title]: shorten the section 'Why breakdowns slip through'."
• An image: "Regenerate the hero image of [title]: fewer elements, no text", or "image 2".
• Avoid "fix the intro and stuff" or "make it better". Nexus will either guess or redo the whole article.

Give links as full URLs or paths, and say where they go

• "In [title], add internal links to /services/maintenance in the section about maintenance, and to /case-studies/example."
• "Cite https://www.example.org/report for the claim about fleet downtime."
• "Remove the link to /blog/old-post from [title]."
• "example.com is a competitor." Nexus removes the link and never cites that site again.

Put a list in one message

• "Set these dates: [title A] to Oct 20; [title B] to Oct 22; [title C] to Oct 27."
• "Rotate Jane, Mark and Ana as authors across October."

Nexus handles the whole list in one call and reports per item what changed, what was already right and what it couldn't find.

Say what must NOT change

• "Revise [title]: add a manufacturing example to section 2. Keep everything else as is."
• "Move only the Instagram posts; leave LinkedIn alone."

Give context when you have it

• Who it's for: "for operations directors at mid-size fleets."
• The angle or source: "based on the case study in the knowledge base", or "use this transcript: [link]."
• Rules that should always apply go in once, as guardrails. Don't repeat them in every request.

Outside the client's channel, name the client

In a channel that isn't pinned to one client: "For [client], write the blog [title]."

Report problems specifically

"File a ticket: [title] published without the hero image on Oct 20, Webflow." Include what happened, which piece, the date and the platform.

Ask Nexus how to do something

Nexus has a guide for every engine, feature and agent, and reads it for the client you're working on, so the answer starts from what's already set up.

• "How do I set up the image library?" Nexus answers from the guide, with where the client stands and the next step.
• "Open the help center." Every guide in one page, with the client's setup status at the top.

Weak vs. strong, at a glance

Prompts

• "Write the blog [title]."
• "Write the blog planned for Oct 20."
• "Move the piece on 2026-10-22 to Oct 27."
• "Rewrite the meta description of [title] to lead with cost savings."
• "Revise [title]: shorten the section 'Why breakdowns slip through'."
• "Set these dates: [title A] to Oct 20; [title B] to Oct 22; [title C] to Oct 27."
• "Rotate Jane, Mark and Ana as authors across October."
• "How do I set up the image library?"
• "Open the help center."
• "File a ticket: [title] published without the hero image on Oct 20, Webflow."

Machine twins: /help/how-to-ask-nexus.json · /help/how-to-ask-nexus.md · /help.json · /llms.txt

Reviewed 2026-10-15. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.