End-to-end recipes that stitch several Squad features together, from raw feedback to a shipped decision.
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 and
Integrations.
Raw feedback to a shipped decision
The full chain, start to finish.
Your weekly triage routine
A repeatable loop built around the dashboard.
Investigate a spike in complaints
Find the theme behind a jump in pain-point feedback.
Turn a quarterly goal into tracked work
Goal, evidence, actions, owners.
Let an agent watch something for you
Configure a trigger, get a report each run.
Trace any decision back to its evidence
Follow a claim down to the original quote.
Bring your own data over the API
POST feedback from a helpdesk, survey tool, or app.
Connect a source (see Integrations) or pipe data in over the
ingestion API. Feedback starts arriving as signals under
Insights → Data Signals (Data signals).
Squad groups signals into clusters
Related signals become clusters, themes like “slow search” or “requests for
SSO” (Signal clusters).
A strong theme becomes an insight
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 the insight to a goal
Link it to a goal it supports (Goals), so the work
ladders up to strategy.
Work the recommended actions
Squad recommends actions off the insight (Actions). Prioritise them, assign
an owner, and Start the ones with a chat prompt to hand them to the assistant.
Write the decision up
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). It cites the evidence
automatically.
Make the call
Review the brief on the Dashboard under One pagers to review, choose Build,
Defer, or Research, and Mark decided.
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).
Give it instructions and an output
Give it instructions and, if you want a written brief each run, a report question and where to
deliver it.
Read what it finds
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.
Nothing in Squad is meant to be an unsourced claim.
Open the entity
A goal, insight, one-pager, or brief.
Follow its links downward
A goal’s Insights tab → an insight’s supporting signals → a
signal’s original quote and source.
Click a reference chip
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, or ask the
assistant “what’s the evidence behind this?”.
Issuance is not self-service today. Write to
support@meetsquad.ai and say which organisation the key is for.
POST your feedback
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.
Watch it join the pipeline
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.
When something looks different from yesterday, open the 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.