> For the complete documentation index, see [llms.txt](https://nationgraph.gitbook.io/nationgraph/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nationgraph.gitbook.io/nationgraph/help-center/readme/signals-overview/signals-setup.md). # Signals Setup Configure your Signals to surface the most relevant opportunities. Learn how to tune filters, set notification preferences, and optimize your signal-to-noise ratio. *** ### Signal Templates Click here to watch [video](https://screen.studio/share/RQIk0v2H). {% embed url="" %} Creating a signal template {% endembed %} {% hint style="warning" %} #### Important You must have a territory or mapped accounts before signals will generate. NationGraph needs to know which institutions to run signals across. Use [Accounts (Account View)](/nationgraph/help-center/readme/accounts.md) to define the account set. Use [Workspaces](/nationgraph/help-center/readme/workspaces.md) when you need to build a territory by team, region, or account list. {% endhint %} {% hint style="warning" %} #### Important Changes to Signal settings don’t apply retroactively. After updating your filters, wait until the next run to see results that reflect the new criteria. {% endhint %} ### Start with the fastest path If a teammate already has working templates, copy theirs first. When you copy from a coworker, NationGraph brings over the template details shown in **Signals → Templates**: * name * query * last-generated time * keywords and exclusions * look-back and created date Copied templates populate in your feed automatically. Copied signals take **3–24 hours** to run. ### Name and organize signal settings Name each setting before you save it. Clear names make it easier to scan, reuse, and compare settings across the team. Use a simple pattern: * **Territory or segment** * **Product or use case** * **Signal type** Examples: * **California K-12 — Competitor** * **Southeast Counties — Budget Trigger** * **Higher Ed — RFP** ### Add a new template Use **Add signal template** when you need a new use case. {% stepper %} {% step %} #### Choose the right signal type A **market opportunity** signal usually maps to **Market Pain Points**. Use it when the opening is not tied to a competitor. Example: a vape-detection company looks for K-12 districts where staff discuss students smoking or vaping in bathrooms, hallways, or parking lots in board minutes, YouTube meetings, or press releases. A **competitor** signal maps to **Competitor**. Use competitor names plus broad industry terms when you want signals like contracts renewing soon or institutions that appear unhappy with those vendors. {% endstep %} {% step %} #### Add keywords Keyword matching is **fuzzy** by default. Wrap a keyword in quotation marks for a **hard match**. For example, use `"vaping in bathrooms"` when you need that exact phrase. Use **ALL** for **AND** logic. Every listed keyword must appear in the same document for that result to reach the feed. {% endstep %} {% step %} #### Set the look-back window Use **Search Start Date** to define how far back NationGraph should scan. Common choices are **90 days** or the start of the school year. New templates usually load in about **1 minute to a couple of hours**. After that, NationGraph reruns the template every **24 hours**. {% endstep %} {% step %} #### Write the intent prompt Use **What are you looking for?** to describe the outcome you want after NationGraph filters by date and keywords. Example: `I'm looking for evidence of K-12 districts struggling with students smoking or vaping in bathrooms, hallways, or parking lots.` {% endstep %} {% step %} #### Add exclusions Use **Exclude Keywords** to remove noisy matches. Always consider excluding your own company name. NationGraph scans PO and contract data, so excluding your company helps avoid surfacing your own wins. {% endstep %} {% endstepper %} ### Keyword matching rules Use fuzzy keywords to cast a wider net. Use hard match when precision matters. This is useful when: * a phrase must appear exactly as written * a broad keyword creates too much noise * you want every keyword on the list to appear in the same document with **ALL** ### Signal Builder for Templates Click here to watch [video](https://screen.studio/share/GSLU1QQG). {% embed url="" %} How to use our Signal Builder template {% endembed %} {% hint style="info" %} Use this for repeatable setup. Paste a company URL. Then return the same structure every time. {% endhint %} Use this framework when you want NationGraph or an AI assistant to build signal settings from a company URL. The goal is simple: * Identify what the company sells * Map it to the right SLED segments * Generate four distinct, high-signal settings {% file src="/files/6vyXPOhNB7lCZUSvIpHF" %} ### Four signal types Use the boxes below to sanity-check each signal before you save it. In the walkthrough, the two example templates map to these existing types: * **Market opportunity** fits the **Market Pain Points** pattern. * **Competitor** fits the **Competitor** pattern.
🔁 1. Competitor Signal **Use this when** You want to find incumbent vendors, expiring services, end dates, or dissatisfaction with competitor products. **Prompt checklist** * mention the target SLED segments * mention the category * look for contract end dates or expiring services * allow dissatisfaction signals * avoid buying-stage wording **Keyword rules** * use competitor names * add 1–3 broad category terms * keep every keyword to 1–2 words * do not include renewal, rebid, replace, switch, evaluation, contract, or solicitation
📈 2. Market Pain Points Signal **Use this when** You want to detect need before a formal buying motion starts. **Prompt checklist** * focus on pain, friction, backlog, shortages, compliance burden, or cost pressure * keep it specific to the target SLED segments * describe the operating problem, not the vendor **Keyword rules** * use pain terms only * keep every keyword to 1–2 words * do not include competitor names
📑 3. RFP Signal **Use this when** You want to find formal buying activity for the company’s solution area. **Prompt checklist** * explicitly say you are looking for RFPs * name the target SLED segments * describe the solution area buyers would request **Keyword rules** * use product or solution terms * keep every keyword to 1–2 words * do not use RFP, RFQ, RFI, solicitation, bid, procurement, or proposal * do not include competitor names
📈 4. Purchase Ability Signal **Use this when** You want to find accounts with budget, funding, leadership movement, or another event that creates a buying window. **Prompt checklist** * look for grants, funding, leadership changes, or budget events * tie the trigger to the company’s product area * keep the language specific to the target SLED segments **Keyword rules** * use grant names, funding terms, leadership moves, or related triggers * keep every keyword to 1–2 words * avoid competitor names unless the funding itself is branded
### Signal Setting Collaboration Copying and reusing Signal settings is the fastest way to get started. * Review a colleague’s existing template * Copy settings with confidence * Reduce setup time across the team #### Copied Signal settings run automatically Click here to watch [video](https://screen.studio/share/GSLU1QQG). {% embed url="" %} When you copy a Signal setting from a colleague, it will now automatically run. This means: * No additional setup after the copy * Faster onboarding for new team members * First results usually appear within **3–24 hours** ### Custom Territory Definition You can now define exactly ***which*** accounts Signals should run against in settings. * Upload a **custom account list** per territory * Generate Signals **only** for your target accounts * Align Signals directly with your book of business Click here to watch [video](https://screen.studio/share/QAS4sBSg). {% embed url="" %} ### How Signals work on the back-end: #### NationGraph data foundation NationGraph maintains a continuously updated public-sector data platform. It includes millions of documents from federal, state, and local sources, like: * Budgets and financial plans * Strategic plans and capital improvement programs * Board and council meeting minutes, transcripts, and associated video content * Purchase orders (POs) and contracts * Requests for Proposals (RFPs) and grants * Press releases and public announcements * Procurement guidelines and policy documents * Legislation and regulatory filings New documents are ingested daily. Signals are designed to surface high-intent, sales-qualified leads (SQLs). #### How a Signal is generated 1. **You define settings.** Date range, included keywords, excluded keywords, and your intent prompt. 2. **NationGraph scans documents in your time window.** This creates the initial baseline. 3. **Every 24 hours, Signals re-run automatically.** New matching documents create new Signals and SQL alerts. #### Key settings | Parameter | Description | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Search Start Date** | Defines the historical window for scanning back from today. Example: `90 days` scans back 90 days. | | **Included Keywords** | Keywords are fuzzy by default. Wrap a keyword in quotation marks for a hard match. Use **ALL** when every keyword must appear in the same document. | | **Excluded Keywords** | Keywords that remove unwanted matches. Always consider excluding your own company name if you scan PO or contract data. | | **“What Are You Looking For?”** | Intent prompt applied after filtering by date and keywords. Example prompt: `"I’m looking for competitor contracts that are renewing soon or institutions that appear unhappy with those vendors."` | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://nationgraph.gitbook.io/nationgraph/help-center/readme/signals-overview/signals-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.