How to name products and slugs in a feedback tool
Name each product the way customers describe it, and let the slug be a short lowercase version of that name. In Escuta Produto the slug is set once from the name when the product is created, so renaming the product later keeps the hosted feedback page at the same address.
By Rafael Thayto 路 Published 路 Last updated
What does the slug control?
The slug is the short lowercase name that appears in a product's hosted feedback page address. A product named Acme Notes gets its form at escutaproduto.com/f/acme-notes. The slug also names the CSV file you download, so an export arrives with a name like acme-notes-feedback followed by the date. Those are the only two places where the slug shows up, but both matter once a link has been shared with customers.
Escuta Produto creates the slug once, from the product name, when you add the product. The name is lowercased, accents are removed, and every run of other characters becomes a hyphen. The name "Cafe Tabela 2.0" becomes cafe-tabela-2-0. The settings you can change later are the name, website, accent color, allowed origins and notification webhook. The slug is not among them, so treat it as permanent from the first day.
What happens when two products want the same slug?
Two products cannot share a slug. If the name you choose already produces one, the second product gets the same base with four random characters added at the end. For example, a second product called Acme Notes may end up with acme-notes-k3q9. The link works, but it looks like a leftover, and you will paste it into support replies and emails for years.
Decide the name before you type it. A name that is specific enough to be unique is better than a single common word like "app" or "notes", which will collide the moment you add a second product in the same space.
Does renaming a product break its link?
No. Saving new settings updates the name shown in the dashboard and in Slack or Discord alerts, but the slug is not recalculated. If you rename Acme Notes to Acme Notes Pro next spring, the hosted form at the old address keeps working, and new items still arrive under the same product with the same history.
Renaming does change what your team sees in alerts, so tell them when you do. The widget key and the hosted link stay the same. The only way to get a new slug is to create a new product, which also means a new key, a new inbox and a new history. That is a separate decision, not a rename.
How should you name several products?
Name each product the way your customers would describe it. Internal codenames are a common mistake. A codename can reach customers through the hosted link you share, and it appears in every alert, where a teammate who joined last month may not know what it refers to.
| Product name | Slug | Why it works |
|---|---|---|
| Acme Notes | acme-notes | Customers already use this name |
| Acme Notes Web | acme-notes-web | A second app with a clear suffix |
| Falcon | falcon | A codename, so only use it if customers know it |
When two products share a word, add the platform or the audience as a suffix, such as Web, iOS or Teams. Avoid version numbers in names. "Acme 2" tells a customer nothing once "Acme 3" appears, and you will end up renaming the display name later. Renaming is harmless for links, but it still creates confusion in your alerts.
What makes a product name work in feedback?
A good name is short enough to read in an alert, specific enough to be unique, and stable enough that you will not change it. Use the same name on your website, in your app store listing and in your support articles. If the name in your feedback tool differs from the name customers see, they will describe the public one in their messages, and you will have to translate every report.
For example, suppose the public name is "Acme Notes" and the internal project is called "notes-v2-rewrite". Name the product "Acme Notes" in Escuta Produto. The internal project name belongs in your own docs, not in your feedback setup.
Write the names down once, in a short list your team can see. Put the product, the public name and the slug side by side. When a new product arrives, add it to that list before you create it in Escuta Produto. The list takes two minutes to keep current, and it stops the same word from being used twice by accident. It also gives a new teammate one place to look when a customer sends a link and nobody remembers which product it belongs to.
Naming your first product in Escuta Produto
Open the dashboard, add a product and enter its name. Escuta Produto creates the slug at that moment. Open the product's Settings and install page and copy the hosted link, then paste it into support replies or onboarding emails. The same page holds the widget snippet, so you can copy the key at the same time. The hosted feedback page guide explains the language and email options for the link, and the widget guide covers the snippet itself.
Send one test submission after you add the product, then read the alert in Slack or Discord and check that the product name looks right. If it reads well there, it will read well in the inbox and in the CSV file name.
Once the first product is in place, the others follow the same pattern. One feedback inbox for many products explains why each product keeps its own key and filter, and a feedback routine for running five products shows how to review them each week.
Frequently asked questions
Can I change a product's slug after I create it?
The slug is set once, from the product name, when the product is created. The settings page does not offer a slug field. Renaming the product keeps the slug, so existing hosted links keep working. A different slug means creating a new product with its own key and inbox.
What happens if two products pick the same name?
The second product still gets a unique slug. Escuta Produto adds four random characters to the base, such as acme-notes-k3q9. The link works, but a distinct product name avoids that suffix in the links you share with customers.
Should the slug match my domain or my app store name?
It does not need to match. The slug only has to be unique inside Escuta Produto. Choose the name customers use, so the link reads naturally in a support email, and use the same name everywhere else you describe the product.
Related
- One feedback inbox for many productsWhy one feedback inbox beats a separate tool for each app, how per-product keys keep feedback apart, and what you give up by reading it all in one place.
- A feedback routine for running five productsA weekly feedback routine for five products: a daily count check, one fixed review slot per product, a bugs-first triage order and a list of what to skip.
- Using feedback to choose which product to work onHow to use unique customers, rating direction and revenue fit to pick the product that gets your next week of work, and avoid the loudest-product trap.
- How to organize Slack channels for product feedbackHow to set up Slack or Discord channels for product feedback: one webhook per product, a channel per product or a shared one, and ways to keep alerts quiet.