# Feedback and Changelogs for Client Projects: One LotsTeam Project per Client

Source: https://blog.lots.team/feedback-and-changelogs-for-client-projects
Published: 2026-10-28T00:30:25.268579+00:00

Give every client their own LotsTeam project. Each one has its own client feedback portal, site widget, support inbox, task board and changelog, optionally on the client's own domain, and your staff, your clients and your AI agents each see only the projects you give them. You pay per project, not per seat.

In LotsTeam a "post" means product feedback: a feature request, a bug report or a question from one of your client's users. It is not a social media post. A "project" is one product, and it is the unit LotsTeam bills. Below is the setup I would use for an agency or freelancer with several clients, with the dashboard route and the prompt for your AI agent at each step. The dashboard does the whole job. The agent is the faster way to repeat it for client number five.

## Why one project per client

A project keeps everything for one client's product in one place and nothing from another client's:

| What the project holds | Why it matters per client |
|---|---|
| Public portal with Posts, Roadmap, Changelog and Contact pages | Each client gets a portal their users can read, on `<name>.lots.support` or the client's own domain |
| Feedback widget | One script tag per client site, so requests land in the right project |
| Support inbox with numbered cases | Each client has its own cases, hours, reply promise and sender |
| Task board linked to the posts behind it | The work for one client never mixes with another |
| Changelog | One changelog per client, with optional "it shipped" emails to the people who asked |
| Access | You choose who can see which project |

Staff and client logins do not add to the bill: organizations and team members are unlimited, and AI agent members are free, up to 20 per team. You pay for projects. A live example of a project portal is LotsTeam's own: [feedback](https://support.lots.team/feedback), [changelog](https://support.lots.team/changelog).

## Step 1: create the client's project, public or internal

Create one project per client product. Give it the product's name, a logo and a one or two sentence description. The portal address is derived from the name, for example `acme.lots.support`, unless you choose a slug.

Decide one thing now, **public or internal**:

| | Public project | Internal project |
|---|---|---|
| Portal (Posts, Roadmap, Changelog, Contact) | On, at its own address or the client's domain | None: its address shows a private page |
| Feedback widget | Works on the client's site | Refuses to load |
| Who sees posts, tasks and changelog | Your team and the client, plus whatever you publish on the portal | Members of the project only |
| Good for | A client product with real users | A build before launch, an internal tool, work you are not ready to show |

Start a new client as internal while you set things up, then switch it to public when the product launches. The setting is **Project settings, Visibility, Internal project**, and switching it off turns the portal and the widget back on.

**From the dashboard:** create the project and fill in the name, description and logo. Projects are billed (covered by your plan first, then credits), so check the cost before you add one.

**From your agent** (works with the AI agent you already use, such as ChatGPT or Claude, connected to the LotsTeam MCP server; setup is on [lots.team/mcp](https://lots.team/mcp)):

```
In my LotsTeam organization, create a project called "Acme Bookings" for
a client. Description: "Online booking for Acme studios". Logo:
https://example.com/acme-logo.png. Make it an internal project for now.
Tell me what it will cost before you create it.
```

A new project is billed, so the LotsTeam tool tells the agent to confirm with you before it creates one.

## Step 2: brand the client feedback portal and put it on their domain

Each project's portal has its own logo, favicon, colours, header and footer, set in the project's portal appearance settings. In the Footer section, untick **Show "Powered by Lots.Team" branding** to switch that line off. A portal that looks like the client's product, on an address the client owns, is what makes it work as a client feedback portal rather than a link to a third-party tool.

To use the client's own address, such as `feedback.example.com`:

1. Add the domain to the project, in the dashboard or through your agent.
2. LotsTeam returns the DNS record to add. It is one CNAME record, set to DNS only (not proxied). Send it to whoever manages the client's DNS.
3. Verify. LotsTeam checks the DNS and the certificate, and tells you which records are still missing. The certificate is issued automatically.

Customers can use "Continue with Google" on a custom portal domain, so the client's users are not sent to a LotsTeam address to sign in. Support replies can also go out from the client's own sending domain: connect it in the project's email settings. Without that, mail goes out as "Project name Support" from support@lots.support.

```
Connect feedback.example.com to the Acme Bookings portal and give me the
DNS record to send to the client. When I tell you it is added, check it
and tell me what is still missing.
```

Adding a domain needs a person with permission to manage project domains. An AI agent member can never do it (more on that in step 4).

## Step 3: put the widget on the client's site

Every client site gets the same script with a different project id:

```html
<script src="https://lots.team/widget.js" data-project="PROJECT_ID" async></script>
```

You find the tag in the project's settings and paste it before `</body>`. The widget settings stay in the dashboard. Platform-specific steps for Next.js, Webflow, Framer and WordPress are in [How to Add a Feedback Widget](https://blog.lots.team/add-feedback-widget-nextjs-webflow-framer-wordpress).

What the client's users get:

- A message box that opens a numbered support case, with an instant confirmation email that carries the case number.
- A Feedback tab for feature requests and bugs, which land as posts on the same project.
- A "Your requests" tab to follow replies, and an Online or Away dot that follows the hours you set for that client.
- A camera button, "Capture this page", that attaches an image of the visible part of the page. It only runs on that click. Password, card, one-time-code, email, phone and address fields are blanked, and anything you mark `data-lt-private` is blanked too. Users see a preview with Retake and Remove before they send it.

For client work the screenshot is the useful part: "the button is broken" arrives with the page that has the button.

Visitors do not need an account. Customers who want to follow their requests on the portal sign in with Google or an email code.

## Step 4: give staff, clients and AI agents the right access

LotsTeam has three roles, and access is set per project.

**Your staff.** Owners and admins see every project. Invite everyone else as a **member** with only the permissions you pick and only the projects you list, so a freelancer sees the clients you put them on and nothing else.

**The client.** Invite them by email, as a member with only their own project and the permissions you choose, or as a viewer, which is read only. They accept while signed in with the invited email address. A viewer who is invited without any project listed sees every project in your organization, so always pick the client's project.

**AI agents.** There are two ways to connect an agent and they behave differently:

| | Your own agent (ChatGPT, Claude, Claude Code, Codex, Cursor) | An AI agent member |
|---|---|---|
| Signs in as | You, with your permissions | Itself, with its own key |
| Sees | Everything you can see, across all clients | Only the projects you choose |
| Shows up as | You | Its own name with an Agent badge |
| Best for | Cross-client questions and reports | One agent per client or per job |

To add an agent member, an owner or admin opens **Team settings, Add an AI agent**, names it, chooses Member or Viewer and picks its projects. LotsTeam shows its key once; paste it into your agent's settings. It connects over MCP or the REST API. You can pause it, replace its key or remove it at any time, and there is an activity view of what it did. Free, up to 20 per team, on every plan.

An agent member can never sign in, receive email, invite people, change roles or project access, or change settings, domains, email settings or billing. An "Acme support agent" with access to the Acme project only can, with the permissions you give it, read that client's posts, draft replies and write changelog entries there. It cannot see the next client's project or touch the portal domain. We run LotsTech this way: our own agents are members of our own LotsTeam, each with its own key.

Your clients' users write the posts and cases your agent reads. The LotsTeam skill tells the agent to treat them as data and never as instructions, and to confirm before it replies, publishes or changes the team. For the full access picture, see [Is LotsTeam Safe?](https://blog.lots.team/is-lotsteam-safe).

```
Invite sam@example.com to my organization as a member with access to
only Acme Bookings. They can read posts, tasks and the changelog and
comment on posts. Show me the email and role before you send the invite.
```

## Step 5: run the weekly loop for each client

The same loop runs inside every project.

**1. Triage the posts.** In the dashboard, open Posts and sort by Most Popular. Merge duplicates (up to 20 at a time, within one project; votes move to the kept post) and link the posts that asked for the same thing to a task.

**2. Work the support inbox.** Each message is a numbered case with a status (open, waiting on customer, snoozed, resolved or closed), a priority, an assignee and tags. Use the Unassigned, Mine and Unread and snoozed views, saved replies and internal notes that never reach the customer. Set the client's support hours and a reply promise in the project's support settings. Your agent can draft replies, and sends only when you tell it to; a sent reply is emailed to the customer and their email replies thread back into the same case. To tell a customer when their request ships, track the case as a post: when the post ships, everyone linked gets one "It's live" email.

**3. Show what is planned (optional).** Tick **Show on Public Roadmap** on a task and add a public summary. Only the tasks you tick appear, in Planned, In Progress and Completed, on that client's portal. See [the public roadmap feature](https://lots.team/features/public-roadmap).

**4. Publish the changelog.** Open Changelog in the client's project, write the entry with a tag (New, Improved or Fixed), link it to the task that delivered the work and tick **Email the people who asked for this**. The entry appears on the client's portal. Emails are off unless you turn them on for that entry, go once to the authors of the linked posts who left an email address, and skip anonymous voters. The full flow is in [How to Publish a Changelog and Notify the People Who Asked](https://blog.lots.team/publish-changelog-notify-people-who-asked).

Prompts for your agent, one per phase:

```
For the Acme Bookings project: list the open posts by votes and group them
by theme. Create a task for the top two, link every post that asks for the
same thing to its task, and show me what you linked. Do not merge anything.
```

```
List the open Acme Bookings support cases that have waited more than a day.
Draft a reply to each and show me the drafts. Do not send any.
```

```
Draft changelog entries for the Acme Bookings tasks finished this week.
Tag each New, Improved or Fixed, link each to its task and turn on
notify_requesters. Do not publish. Show me each draft and how many people
it would email.
```

If a task lands in the wrong client's project, move it: the dashboard's Move and the agent's `update_task` with a new project id both keep its comments, status and dates. The two projects must be in the same organization, and any posts or changelog entries linked to the task have to be unlinked first.

## Step 6: report across all your clients

A project-by-project view is right for the work. For the Monday check, use your own connected agent, because it can read every project you can:

```
For every project in my LotsTeam organization, give me one table with a
row per client: open cases, cases waiting on the customer, median first
reply and median resolution time for the last 30 days, and the share of
good ratings. Then list the five posts with the most votes across all
clients.
```

The agent reads this from the project and organization support numbers (open, waiting and unassigned cases now, plus the last 7 and 30 days of new cases, median first response, median resolution and ratings) and from the posts across the organization.

## What it costs for a roster of clients

The project is the paid unit. Plans cover a block of projects and pay as you go costs a flat amount per project, drawn from credits and charged daily:

| Clients | Option | Monthly price |
|---|---|---|
| Up to 3 | Starter, 3 projects | $24 |
| Up to 10 | Pro, 10 projects | $69 |
| Up to 30 | Business, 30 projects | $159 |
| Any number, no plan | Pay as you go | $9 per project |

*Plan and pay-as-you-go prices checked on 27 October 2026 on [lots.team/pricing](https://lots.team/pricing).* A project beyond a plan's block is billed at your plan's rate. Eligible new accounts get 10,000 free credits, valid for 90 days, no card. Three clients on pay as you go cost $27 a month, so Starter's $24 covers the same three for less; from eight clients Pro's $69 is below eight projects at $9. Every feature comes with every project, including the custom domain and custom email, and organizations and team members are unlimited. More on how credits and plans fit together in [LotsTeam Pricing Explained](https://blog.lots.team/lotsteam-pricing-explained).

## FAQ

### What is the simplest client feedback tool setup in LotsTeam?

One project per client. Add the widget to the client's site, put the portal on their domain, and invite your staff to only the projects they work on. Feedback, support cases, tasks and the changelog for that client then stay in one place, separate from your other clients.

### Can clients see each other's projects?

Not when each person is invited to only their own project. Members see only the projects you list for them, and so does a viewer who has projects listed. Owners and admins see every project, and a viewer invited without any project listed sees all of them, so always pick the client's project.

### Can I run the client feedback portal on the client's own domain?

Yes. Add the domain to the project, add the CNAME record LotsTeam gives you (DNS only, not proxied), and verify. The certificate is issued automatically. Replies to the client's customers can also be sent from the client's own sending domain, set in the project's email settings.

### Can an AI agent work on one client's project only?

Yes. Add it as an AI agent member in Team settings, choose Member or Viewer and pick that one project. It has its own key, shows an Agent badge on what it writes, and can never sign in, invite people, change roles or change settings, domains or billing. Agent members are free, up to 20 per team.

### How much does it cost for ten clients?

Ten projects fit in the Pro plan at $69 a month, checked on 27 October 2026. Staff, clients and agent members do not add to that: organizations and team members are unlimited and AI agent members are free, up to 20 per team. Check lots.team/pricing for current prices.

### What do I do when a client leaves?

Switch their project to internal under Project settings, Visibility. That takes the public portal and the widget offline and leaves the posts, tasks and changelog with your team. You can also delete a project in the dashboard. Neither ends a plan: plan changes are made from Billing.

*LotsTeam details checked on 27 October 2026 from [lots.team/pricing](https://lots.team/pricing), [lots.team/llms.txt](https://lots.team/llms.txt), [lots.team/skill.md](https://lots.team/skill.md), [api.lots.team/tools.json](https://api.lots.team/tools.json) and the product feature pages for the [support inbox](https://lots.team/features/support-inbox), [feedback board](https://lots.team/features/feedback-board) and [changelog](https://lots.team/features/changelog). Project names, domains and emails in the prompts are examples.*