# Feedback Groups A **Feedback Group** is a space that centralises every piece of feedback for a specific project, programme, or initiative. It is the organisational backbone of your work in BoundaryAI: a single container for every channel, every dataset, every analysis, and every report that\ belongs to one effort. When you put feedback inside a Feedback Group, you stop thinking about individual surveys, sources and uploads as isolated artefacts. You start thinking about a project: *"what is the customer experience in Europe this quarter?"*, *"how is the second-year cohort feeling about the new curriculum?"*, *"what do partners think of our onboarding?"* — and BoundaryAI keeps every input and every insight in one place so you can answer those questions over time. *** ### What a Feedback Group contains A Feedback Group can hold any combination of the five feedback channels BoundaryAI supports. You do not have to use all of them — most groups\ start with one or two and grow over time. | Channel | What it is | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **Surveys** | Custom-built questionnaires sent to respondents via a share link, QR code, or embed. | | **Uploads** | Existing datasets imported as `.xlsx`, `.csv`, `.docx`, `.pdf`, `.txt`, `.json`, or `.xml`. | | **Connectors** | Tickets and conversations pulled in automatically from third-party tools (Zendesk, Freshdesk, Intercom, Jira, HubSpot, and others). | | **Web scraping** | Reviews and mentions collected on a schedule from public sources (Google Reviews, Trustpilot, TripAdvisor, Reddit, X, Google News, and others). | | **Interview transcripts** | Long-form qualitative material brought in as documents and analysed alongside structured responses. | Whichever channels you use, BoundaryAI normalises everything into the same analytical model — themes, sentiment, segmentation, flags — so aTrustpilot review and an Excel column of NPS comments end up in the same dashboards. #### Real examples * *Management Faculty — Course Evaluation 2026* * *Product X — Customer Feedback (Europe)* * *Campus Life Insights — First-Year Cohort* * *Partner Engagement — Q2 2026* * *Beta Program — In-Product Feedback* *** ### Creating a Feedback Group 1. Click **New Feedback Group** from the Feedback Groups page (or the dashboard). 2. Enter a clear, descriptive name (2 – 255 characters; must be unique within your organisation). 3. Click **Create**. You land directly inside the new group's page, ready to add a survey, upload a file, connect a platform, or set up a scraper. A Feedback Group starts empty by default — no auto-generated survey, no placeholder content. You decide what belongs in it. > **Naming tip.** Use a name that will still make sense in a year. *"Q2 NPS"* is fine for this quarter, but *"Customer NPS — Quarterly"* keeps\ > working as you add the next cycle. *** ### The Feedback Group page Every Feedback Group has its own page at `/single-survey-series/`. The page is laid out around the **project**, not around individual\ surveys, so you can read the state of a programme at a glance. #### Header The header shows the group name, a back-link to the Feedback Groups list, and a rename pencil. (Renaming is disabled for the default *Individual Surveys* group.) #### Quick Overview A summary band at the top of the page surfaces: * **Total interactions analysed** across every channel in the group. * **Sentiment breakdown** — positive, slightly positive, neutral, slightly negative, negative. * **Sentiment trend** — a chart of how sentiment has moved over time. * **Last interaction** — the timestamp of the most recent piece of feedback. Time-range filters let you narrow the view to the last week, month, three months, six months, twelve months, or all time. #### Source tabs Below the overview, the page is split into tabs for each source type: * **All Surveys** — combined view across every channel, useful when you do not care which channel a response came from. * **Surveys** — manually-built surveys. * **Uploads** — Excel, CSV, document, and JSON imports. * **Connectors** — connected ticketing platforms. * **Web Scraping** — running and historic scrapers. Each tab shows what is already in the group, plus a quick-start CTA to add a new source of that type. #### Reports widget A reports panel on the page shows how many reports and report schedules are scoped to this group, with shortcuts to **New Report** and **See**\ **Reports**. Reports are described in their own section below. *** ### Group-level analytics A Feedback Group is more than a folder. The genuinely useful thing about putting surveys, uploads, and tickets in the same group is that\ BoundaryAI rolls them up into cross-channel analytics. #### Cross-source overview The Quick Overview at the top of the page aggregates *every* response across *every* channel. A scraped Trustpilot review counts the same as an open-ended NPS comment from a survey, and both feed into the same sentiment trend. #### Super-Themes **Super-Themes** are themes that span multiple sources inside the group. Where a single-source analysis might surface *"price"* and *"shipping speed"*, a Super-Theme groups those threads across surveys, uploads, and tickets so you can see what is *actually* dominant at the project level — not just what is loud in one channel. For each Super-Theme you get: * **Aggregate mention count** across the whole group. * **Sentiment** — a single signed score that summarises whether the theme is praised or criticised on average. * **Source surveys** — which inputs contributed. * **Last computed** timestamp and a manual **Recompute** option to re-cluster after a major data change. Super-Themes use embedding similarity to cluster similar findings across channels, so wording differences (*"too expensive,"* *"price is too high,"* *"not worth the cost"*) collapse into a single row. #### AI Insights The **Insights** view goes one step further: it asks the AI to summarise the group in plain language. It returns: * A handful of headline themes with explanatory copy. * Sentiment recaps with examples. * Language patterns and recurring phrases. * Category breakdowns (where applicable). * A short list of suggested action items. Insights are computed asynchronously and cached, so you can poll a long-running generation in the background and refresh later. The UI handles\ the polling for you. *** ### Reports Reports are **scoped** to a Feedback Group, which means a single report can summarise everything across the group's surveys, uploads, scrapers, and connectors — or you can narrow it down to specific channels inside the group. From the group's Reports widget you can: * **Create a new report** scoped to this group. * **Schedule a recurring report** (daily, weekly, monthly, or a custom interval) and have it emailed to recipients automatically. * **Filter the report's contents** to specific surveys, themes, or time ranges within the group. * **Export** the resulting report as PDF, HTML, or JSON. Reports inherit the group's structure — surveys, themes, Super-Themes, sentiment, flags — so a single PDF can act as a quarterly readout for an entire programme, without you having to assemble it from separate sources. *** ### Sharing & permissions Feedback Groups can be shared with other members of your organisation. Each user is assigned one of two roles per group: | Role | What they can do | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Read-only** | View surveys, uploads, connectors, analyses, Super-Themes, insights, and reports. Cannot create or edit anything. | | **Read-write** | Everything Read-only can do, plus create, edit, and delete surveys and other sources, run analyses, generate reports, and manage sharing. | The user who creates a Feedback Group automatically receives Read-write access. Org-level admins always have full access regardless of the\ group-level setting. > **Note.** Permissions today are a two-tier model (Read-only / Read-write), not a three-tier *Viewer / Editor / Owner*. If you need to restrict who can delete the group itself, manage that at the organisation level. *** ### Renaming and deleting #### Rename Click the pencil next to the group name to open the rename dialog. The new name must be 2 – 255 characters long and must not collide with another group in your organisation. Renaming does not affect the group's URL, share links, or any of its surveys — only the display name changes. #### Delete Deleting a Feedback Group is intentionally a more deliberate action. * The group itself is removed from the list. * All audit-logged for traceability (who, when, which group). * **The surveys inside the group are not deleted.** They are detached from the group and remain available; if they have no other home, they fall back into the default **Individual Surveys** group on next sync. If you want to permanently delete the data, delete the surveys first (and confirm the cascade prompt for their responses), then delete the group. > **Heads up.** *Individual Surveys* — the default group — cannot be renamed or deleted. It always exists per organisation as a fallback. *** ### The default "Individual Surveys" group Every BoundaryAI organisation has a built-in Feedback Group called **Individual Surveys**. It exists to catch any survey that was created\ without explicit assignment to a custom group, so no work is ever orphaned. You can use it freely, but treat it as a temporary holding area: * It cannot be renamed. * It cannot be deleted. * It cannot be shared with specific members (org-level access applies). * It is excluded from group-level comparisons that look at distinct project trends. If a survey is going to be re-run, compared, or reported on as part of a programme, move it out of *Individual Surveys* into a custom Feedback\ Group as soon as you can. *** ### A note on flags Flags — keyword-driven detection rules used for theme tagging and notifications — are configured **per question** on individual surveys, not at the group level. The group does not impose flag rules on its surveys. That said, **reports can aggregate flag results across every survey in the group**, so even though flags are defined locally, you can monitor\ and report on them globally from the group's Reports widget. *** ### Best practices * **Use one Feedback Group per real-world initiative.** A group should map to a project, programme, or environment that has a name in plain English ("Q2 NPS — Europe", "Onboarding Survey 2026"). Avoid creating a group per survey. * **Mix channels deliberately.** The point of a group is cross-channel analysis. Pulling in scraped reviews alongside survey responses inside the same group lets Super-Themes surface patterns that no single channel could. * **Move work out of *****Individual Surveys***** once it has a home.** Treat the default group as a triage area, not a long-term destination. *** ### What's next * Add the first source — a survey, an Excel upload, a connector, or a scraper. * Style the surveys to match your brand — see Customizing a Survey. * Track lifecycle and run cycles cleanly — see Managing Surveys. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://boundaryai.gitbook.io/boundaryai-docs/basics/feedback-groups.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.