# How to Close the Feedback Loop With Customers: From a Support Case to the "It's live" Email (a Real Run)

Source: https://blog.lots.team/how-to-close-the-feedback-loop-with-customers-from-a-support-case-to-the-its-live-email-a-real-run
Published: 2026-11-06T00:30:25.124155+00:00

**To close the loop with a customer, log their request as a post with their email attached, turn it into a task, link the two, mark the task done, then publish a changelog entry linked to that task with "notify requesters" on.** LotsTeam then emails the people whose posts are linked to the task. I ran that whole chain through the LotsTeam connector in my AI agent, and the product reported one requester notified. This article shows every step and what it returned, and it is just as plain about what the run could not show.

I'm the founder of LotsTeam. I ran this in a throwaway test project with a made-up request: a customer asking for a CSV export on a weekly usage report in a fictional product. Nothing here comes from a real customer.

## The loop in one view

| Step | What I did | What came back |
|---|---|---|
| 1. Request in | Logged the request as a post, with a requester name and email | Post created, status open |
| 2. Triage | Raised the priority, added two tags, set status to in progress | Post updated |
| 3. Task | Created a task from the post | Task created and already listed as linked to the post |
| 4. Link | Linked the post to the task explicitly | "Already linked", a no-op |
| 5. Done | Moved the task to in progress, then done | Task done, completion time set |
| 6. Changelog | Wrote an entry tagged "new", linked to the task, as a draft | Draft created |
| 7. Publish | Published it with notify requesters on | Published, one requester notified |

## Step 1: Get the request in (and why mine was a post)

A real support case arrives through the widget, the portal or email. My test project was internal, which means it has no public widget and no portal, so a case could not arrive from outside. I checked the support inbox anyway: it returned zero messages. The connector has tools to list, read, update and reply to cases, but none that creates one.

So the first step in my run was a post, which is LotsTeam's word for a request, bug or idea from a user. I logged it the way you would log something a customer told you on a call or in an email: a title, a description, the category "feature", and the requester's name and email. The tool says to pass the email only when you log someone else's request, and that is exactly the case here. This is the step that matters later: the email on the post is what the "It's live" message is addressed to.

I used one address for the whole run, my own, because a notification needs a real recipient and I did not want to email anyone else. The requester name was marked "made-up".

If you start from a case instead, I did not run that path, so I won't describe it. From the post onward, the loop is the one below.

## Step 2: Triage the request

Triage here means deciding what the request is and how much it matters. I raised the priority from medium to high, added two tags (reports, export) and set the status to in progress. I also left a short comment on the post saying it had been triaged and turned into a task.

The comment is worth doing because it tells the requester, on the post itself, that someone read it. In my run I did not check who can see the comment in a real portal, because the project had none.

## Step 3: Create the task and link the post

I created a task titled "Build CSV export for the weekly usage report", priority high, and passed the post as its originating request. The task came back already linked to the post, and listing the task's linked posts showed it. I then called the explicit link tool as well, and it answered that the post was already linked, with no change.

So you have two ways to get the link: pass the post when you create the task, or link them afterwards. The link is what the notification later follows. A task can carry many posts, so if three customers asked for the same thing, you link all three posts to one task and all three requesters can be emailed. I linked one post in this run, so I can only report the one-requester result.

## Step 4: Move the task to done

I moved the task to in progress and then to done. Marking a task done is a status change on the board. It does not ship code, and LotsTeam does not build the feature for you.

One thing I noticed: after the task was done, the post itself was still in progress. Marking the task done did not change the post status. If you want the request to read as resolved, set it yourself. I did not do that in this run.

## Step 5: Write the changelog entry and link it to the task

I wrote a changelog entry tagged "new", titled "Download the weekly usage report as CSV", with two plain sentences saying what changed and what the user gets. I linked it to the task when I created it, and saved it as a draft first. The link between the entry and the task is how LotsTeam knows which posts to notify. An entry that is not linked to a task has no requesters to tell.

## Step 6: Publish and see what the product does

I published the entry with "notify requesters" on. The result said the entry was published and that one requester was notified. Reading the entry back confirmed it: it recorded a notified count of one and the time.

The notification option is off unless you turn it on, and the tool description says to ask the person before you do. I had the founder's go-ahead for exactly one address, so I turned it on once. When your own agent runs this, keep that habit: it is the one step that sends mail to a customer.

That is what the product did. One email went out, to my own address, and no other address was used.

## What this run could not show

- **The email itself.** The product told me one requester was notified. No tool in the connector shows me the message, so I cannot describe its wording, its subject or how it looks in an inbox.
- **A real support case.** As above, I could not create one in an internal project, so the first step was a post.
- **The public view.** With no portal, I could not show how the changelog entry or the comment looks to a customer.
- **More than one requester, or a post with no email.** I used one post with one email. I did not test what happens with several posts, or with a post that has no email attached.

## When to use this loop

Use it when a request is worth telling the person about. It takes two things at the start, the requester's email on the post and a task linked to it, and two at the end, an entry linked to the task and the notify option on. The tool descriptions tie the email to exactly those pieces.

If you work from an AI agent, you can do all of it by asking in plain words, since every step above was a tool call. My article on [publishing a changelog and notifying the people who asked](https://blog.lots.team/publish-changelog-notify-people-who-asked) goes deeper on the last two steps, and [how to triage customer feedback with Claude or ChatGPT](https://blog.lots.team/triage-customer-feedback-with-claude-or-chatgpt) covers the triage step on a larger batch. If you want your agent to be a named member of the team instead of borrowing your sign-in, read [can an AI agent be a member of your team](https://blog.lots.team/ai-agent-as-a-team-member), and for what an agent may and may not do, [MCP server permissions for feedback and support tools](https://blog.lots.team/mcp-server-permissions-feedback-support-tools).

A project is the unit LotsTeam charges for. Plans start at $24 a month for 3 projects, and new accounts get free credits, no card. The details are in [LotsTeam pricing explained](https://blog.lots.team/lotsteam-pricing-explained), and you can start at [lots.team](https://lots.team).

## FAQ

### How do I tell a customer their request is live in LotsTeam?
Log their request as a post with their email, create a task and link the post to it, mark the task done, then publish a changelog entry linked to the task with notify requesters on. In my run that reported one requester notified.

### Who gets the "It's live" email?
The people whose posts are linked to the entry's task, once, when the entry is first published. In my run that was one person, the address I attached to the post.

### Do I have to turn notifications on?
Yes. The option is off unless you set it, both when you create an entry and when you publish it. The tool says to ask the person first, because this step sends mail to a customer.

### Does marking a task done update the request?
Not in my run. The task became done and the post stayed in progress, so I would set the post status myself if I wanted it to read as resolved.

### Can I run the whole loop from my AI agent?
Yes. Every step I describe was a tool call through the LotsTeam connector. The one thing I could not do was create a support case in an internal project, so I used a post for that step.

### Does LotsTeam build the feature for me?
No. A task marked done is a status on your board. The code is still yours to ship.
