> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt > Use this file to discover all available pages before exploring further. # Cookbook > End-to-end recipes that stitch several Squad features together, from raw feedback to a shipped decision. Cookbook Cookbook Recipes that stitch several features together. Each per-feature page has its own focused cookbook; these are the end-to-end journeys that cross the whole product. They assume you've connected at least one source. If not, start with the [Quickstart](/quickstart) and [Integrations](/integrations). The full chain, start to finish. A repeatable loop built around the dashboard. Find the theme behind a jump in pain-point feedback. Goal, evidence, actions, owners. Configure a trigger, get a report each run. Follow a claim down to the original quote. POST feedback from a helpdesk, survey tool, or app. Reconstruct how something got to where it is. ## From raw feedback to a shipped decision The full chain, start to finish. Connect a source (see [Integrations](/integrations)) or pipe data in over the ingestion API. Feedback starts arriving as **signals** under **Insights → Data Signals** ([Data signals](/signals)). Related signals become **clusters**, themes like "slow search" or "requests for SSO" ([Signal clusters](/signal-clusters)). When a theme is strong enough, Squad synthesises it into a scored **insight** (`IN-…`). Open it to read its strength and momentum and the signals behind it. Link it to a **goal** it supports ([Goals](/goals)), so the work ladders up to strategy. Squad recommends **actions** off the insight ([Actions](/actions)). Prioritise them, assign an owner, and **Start** the ones with a chat prompt to hand them to the assistant. When a decision needs writing up, generate a **one-pager**, a PRD to spec the work, or a decision brief to make the call ([One-pagers](/one-pagers)). It cites the evidence automatically. Review the brief on the [Dashboard](/dashboard) under **One pagers to review**, choose **Build**, **Defer**, or **Research**, and **Mark decided**. ## Your weekly triage routine A repeatable loop built around the dashboard. Open the [Dashboard](/dashboard). The caption above the greeting tells you when the daily brief was written. Start, mark done, or dismiss each. What is done drops off automatically. Decision briefs waiting on a call, and PRDs sitting in draft or review. Anything surprising in the last day. Once you have changed the picture, so the next brief reflects it. ## Investigate a spike in complaints Open **Insights** and switch to the **Signal Clusters** tab ([Signal clusters](/signal-clusters)). Filter by **Type → pain point** and sort by **Data Signals** descending. Open the largest cluster and read the **Members** quotes, the real feedback. If it's already an insight, follow the linked `IN-…` and decide whether it needs a goal or an action behind it. If not, ask the [assistant](/chat-assistant) to draft one. ## Turn a quarterly goal into tracked work Create it on the [Goals](/goals) page. Open its **Insights** tab and link them. This is the evidence for why the goal exists. From those insights, accept the **actions** Squad recommends and give them owners ([Actions](/actions)). As work lands, the goal's linked insights and actions keep it honest. You can always trace the goal down to the feedback driving it ([Relationships](/relationships)). ## Let an agent watch something for you Go to **Agents → New** and configure what to watch (a URL, a Slack channel, a Notion space, or a workspace event) plus how often it runs ([Agents](/agents)). Give it instructions and, if you want a written brief each run, a report question and where to deliver it. Each run produces a **report** and folds new findings into your signals, clusters, and insights, so an agent quietly feeds the same pipeline everything else uses. ## Trace any decision back to its evidence Nothing in Squad is meant to be an unsourced claim. A goal, insight, one-pager, or brief. A goal's **Insights** tab → an insight's supporting signals → a signal's original quote and source. Anywhere a reference chip like `SI-12`, `IN-4`, `AC-7`, or `OP-3` appears, click it to jump straight to that entity. See [Relationships](/relationships), or ask the [assistant](/chat-assistant) "what's the evidence behind this?". ## Bring your own data over the API Issuance is not self-service today. Write to [support@meetsquad.ai](mailto:support@meetsquad.ai) and say which organisation the key is for. From your own system (helpdesk, survey tool, app), POST feedback to `/api/v1/signals` with a sensible title and any `metadata` you want to keep. Everything arriving this way is recorded against the `api` source. Ingested signals join the pipeline exactly like integration data, clustered, scored, and surfaced as insights with no further work from you. Step one is not something you can do yourself. No screen in the app mints a key and no CLI command does either, so you have to ask Squad for one. ## See who changed what When something looks different from yesterday, open the [Activity](/activity) feed. It records every create, update, and decision across the workspace (by teammates and by Squad itself) so you can reconstruct how a goal, insight, or brief got to where it is.