{
  "@type": "help_guide",
  "id": "how-to-ask-nexus",
  "title": "How to ask Nexus",
  "kind": "basics",
  "summary": "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.",
  "aliases": [
    "prompting tips",
    "how to prompt nexus",
    "ground rules",
    "how should i ask nexus",
    "how do i talk to nexus",
    "tips for asking nexus"
  ],
  "engine": null,
  "agents": [],
  "related": [
    {
      "id": "what-nexus-does-automatically",
      "page": "https://nexus.effiqs.com/help/what-nexus-does-automatically"
    },
    {
      "id": "glossary",
      "page": "https://nexus.effiqs.com/help/glossary"
    },
    {
      "id": "content-engine",
      "page": "https://nexus.effiqs.com/help/content-engine"
    }
  ],
  "reviewed": "2026-10-15",
  "sections": [
    {
      "heading": "What it does",
      "key": "what-it-does",
      "markdown": "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."
    },
    {
      "heading": "Ground rules",
      "key": "ground-rules",
      "markdown": "- **Work in the client's own channel.** Once the channel is pinned, Nexus knows the client and you never need to name it.\n- **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.\n- **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.\n- **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.\n- **Nexus remembers rules you state.** \"Never mention pricing in any blog\" is stored as a guardrail and applied to every future piece.\n- **Previews are not changes.** Bulk changes show a preview first. Nothing changes until you reply \"yes\" or \"confirm\". Check the dashboard afterwards."
    },
    {
      "heading": "Use it",
      "key": "use-it",
      "markdown": "### Name the piece by its exact calendar title, or by its date\n\nNexus finds a piece in this order: its ID, then its exact title, then its publish date, then a unique part of the title.\n\n- **Best:** copy the title from the calendar dashboard and paste it: **\"Write the blog [title].\"**\n- **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.\"**\n- If two pieces share a date, give both: \"the Oct 20 piece about downtime.\"\n- Use the current title. If the title was renamed, use the new one.\n- Avoid \"the downtime one\", \"that blog from last week\" or \"the next one\". They match several pieces or none.\n- 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.\n\n### Use real dates, not relative ones\n\n- Say \"Oct 20\", not \"next Tuesday\" or \"in two weeks\". Nexus doesn't reliably turn weekday names into dates.\n- For a range: \"the posts from Oct 14 to Oct 21\", not \"this week's posts\".\n- For a cadence: \"Mon, Wed, Fri starting Oct 19.\"\n\n### \"Blog\" and \"post\" mean different things\n\n| You say | Nexus does |\n|---|---|\n| \"Write the blog [title]\" | Produces the full website article (research, brief, draft, QA, images) |\n| \"Add a blog idea: …\" | Adds a piece to the website content calendar |\n| \"Draft the post [title]\" | Writes social copy only, for your approval |\n| \"Add a social post: …\" | Adds to the social calendar |\n\n### Say which social dashboard, and the author\n\n- Plain \"social\" or \"social post\" means **Company Social**: the company's own LinkedIn page, Instagram, Facebook and Google Business.\n- For an author's personal LinkedIn, say \"Thought Leadership\" and name the author: \"Draft Jane's Thought Leadership post planned for Oct 21.\"\n- Name the platform when it matters: \"the Instagram post on Oct 20\", not just \"the Oct 20 post\". Several channels can share a date.\n\n### Name the field, section or image you want changed\n\n- **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.\n- **A section:** **\"Revise [title]: shorten the section 'Why breakdowns slip through'.\"**\n- **An image:** \"Regenerate the hero image of [title]: fewer elements, no text\", or \"image 2\".\n- Avoid \"fix the intro and stuff\" or \"make it better\". Nexus will either guess or redo the whole article.\n\n### Give links as full URLs or paths, and say where they go\n\n- \"In [title], add internal links to /services/maintenance in the section about maintenance, and to /case-studies/example.\"\n- \"Cite https://www.example.org/report for the claim about fleet downtime.\"\n- \"Remove the link to /blog/old-post from [title].\"\n- \"example.com is a competitor.\" Nexus removes the link and never cites that site again.\n\n### Put a list in one message\n\n- **\"Set these dates: [title A] to Oct 20; [title B] to Oct 22; [title C] to Oct 27.\"**\n- **\"Rotate Jane, Mark and Ana as authors across October.\"**\n\nNexus handles the whole list in one call and reports per item what changed, what was already right and what it couldn't find.\n\n### Say what must NOT change\n\n- \"Revise [title]: add a manufacturing example to section 2. Keep everything else as is.\"\n- \"Move only the Instagram posts; leave LinkedIn alone.\"\n\n### Give context when you have it\n\n- Who it's for: \"for operations directors at mid-size fleets.\"\n- The angle or source: \"based on the case study in the knowledge base\", or \"use this transcript: [link].\"\n- Rules that should always apply go in once, as guardrails. Don't repeat them in every request.\n\n### Outside the client's channel, name the client\n\nIn a channel that isn't pinned to one client: \"For [client], write the blog [title].\"\n\n### Report problems specifically\n\n**\"File a ticket: [title] published without the hero image on Oct 20, Webflow.\"** Include what happened, which piece, the date and the platform.\n\n### Ask Nexus how to do something\n\nNexus 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.\n\n- **\"How do I set up the image library?\"** Nexus answers from the guide, with where the client stands and the next step.\n- **\"Open the help center.\"** Every guide in one page, with the client's setup status at the top.\n\n### Weak vs. strong, at a glance\n\n| Weak | Strong |\n|---|---|\n| \"Write the next blog\" | \"Write the blog *Fleet Maintenance Checklist*\" |\n| \"Fix the downtime one\" | \"In *How Unplanned Downtime Erodes Margin*, rewrite the meta description\" |\n| \"Move it to next Tuesday\" | \"Move the Oct 20 piece to Oct 27\" |\n| \"Add some links\" | \"Add internal links to /services/maintenance and /case-studies/example in section 2\" |\n| \"Do the social posts for this week\" | \"Draft the Company Social posts from Oct 14 to Oct 21\" |\n| \"Change the image\" | \"Regenerate the hero image of [title]: brighter, no people\" |\n| \"Make Jane's posts\" | \"Draft Jane's Thought Leadership posts planned for October\" |"
    },
    {
      "heading": "Prompts",
      "key": "prompts",
      "markdown": "- \"Write the blog [title].\"\n- \"Write the blog planned for Oct 20.\"\n- \"Move the piece on 2026-10-22 to Oct 27.\"\n- \"Rewrite the meta description of [title] to lead with cost savings.\"\n- \"Revise [title]: shorten the section 'Why breakdowns slip through'.\"\n- \"Set these dates: [title A] to Oct 20; [title B] to Oct 22; [title C] to Oct 27.\"\n- \"Rotate Jane, Mark and Ana as authors across October.\"\n- \"How do I set up the image library?\"\n- \"Open the help center.\"\n- \"File a ticket: [title] published without the hero image on Oct 20, Webflow.\""
    }
  ],
  "prompts": [
    {
      "text": "Write the blog [title].",
      "tool": "produce_content_piece"
    },
    {
      "text": "Write the blog planned for Oct 20.",
      "tool": "produce_content_piece"
    },
    {
      "text": "Move the piece on 2026-10-22 to Oct 27.",
      "tool": "update_content_calendar_item"
    },
    {
      "text": "Rewrite the meta description of [title] to lead with cost savings.",
      "tool": "rewrite_content_field"
    },
    {
      "text": "Revise [title]: shorten the section 'Why breakdowns slip through'.",
      "tool": "revise_content_draft"
    },
    {
      "text": "Set these dates: [title A] to Oct 20; [title B] to Oct 22; [title C] to Oct 27.",
      "tool": "set_content_calendar_dates"
    },
    {
      "text": "Rotate Jane, Mark and Ana as authors across October.",
      "tool": "assign_content_authors"
    },
    {
      "text": "How do I set up the image library?",
      "tool": "read_help_guide"
    },
    {
      "text": "Open the help center.",
      "tool": "open_help_dashboard"
    },
    {
      "text": "File a ticket: [title] published without the hero image on Oct 20, Webflow.",
      "tool": "create_support_ticket"
    }
  ],
  "page": "https://nexus.effiqs.com/help/how-to-ask-nexus",
  "markdown": "https://nexus.effiqs.com/help/how-to-ask-nexus.md"
}