Skip to main content

Bagel for GTM Teams | TRAINING GUIDE

How Sales, Customer Success, and Account teams submit feedback, track requests, and use Customer 360 Audience: Sales · CS · Account teams Read time: 6 minutes

R
Written by Roy Turiski

🥯 01 Why this matters

Your team hears more product feedback than anyone else in the company — on calls, in emails, in Slack threads with customers. Bagel turns that feedback into a single source of truth that the product team actually uses when deciding what to build next. You don't need to become a Bagel power user to be part of that. There are really just three things worth knowing: how to submit a request in seconds, how to see what happened to it afterward, and how to check what's already been asked for a given account before you get on a call.


🥯 02 A few terms worth knowing

You won't need to manage any of this directly — that's the product team's job. But it helps to recognize the vocabulary when you're looking at a request.

  • Idea — a specific piece of product feedback that's been logged and tracked through a roadmap (submitted, in discovery, in development, shipped, and so on).

  • Evidence — the individual piece of feedback behind an idea: a quote, a request, a comment tied to one account.

  • Product Area — the category an idea is filed under (for example, Integrations, Reporting, Security). This gets assigned automatically and becomes more accurate over time.


🥯 03 Submitting a request

You don't need a Bagel login to submit feedback. There are two ways to do it, and both take under a minute:

Option 1 - Browser extension

Install it once from the Chrome Web Store and it sits in your toolbar, ready whenever it here. you hear something worth logging: mid call, reading an email, or in Slack.
Download it now with this link!

Option 2 - Your CRM

In Salesforce, search for the account and open it; Bagel shows up in the account's navigation bar as another application, right alongside your standard tabs. Submit without ever leaving the account record. This needs to be set up for your org first, so it isn't available for every customer.

How to fill it in?

  • Give it a short, clear title and description of what the customer is actually asking for.

  • The account is pulled automatically from your CRM data — no manual typing, and no risk of it landing on the wrong account.

  • Before you submit, the system checks whether something similar already exists in the backlog or in development. If a match comes up, add your “+1ˮ to it instead of creating a duplicate. If nothing matches, submit it as new.

  • Flag anything time-sensitive or deal-critical directly in the description so it stands out during triage.

TIP

The more specific the description, the faster and more accurately it gets routed to the right team.


🥯 04 What happens after you submit

Once you submit, it's in the product team's hands — this part isn't managed by CS. From there, it reaches the PM in one of two ways, depending on how things are set up for that account:

  • Dedicated inbox — every submission lands in a dedicated inbox for a PM to review and route by hand. This isn't used for every account; it depends on the setup.

  • Automatic matching — Bagel's AI matches your submission behind the scenes to an existing idea, adding it as supporting evidence. The PM sees it the next time they review that idea.

Either way, the PM then does one of three things with it:

  • Confirms it's related — for a matched submission, they confirm it genuinely belongs to that idea, and the status is reflected back to you.

  • Turns it into a new idea — if it's not yet tracked, it becomes its own idea that can move through the roadmap on its own.

  • Declines it with a reason — in the rare case it's not something the product team will pursue, you'll get a short note explaining why.


🥯 05 Staying in the loop

You don't need to check back manually. You're notified automatically — through the

browser extension, Slack, and/or your CRM — any time there's a status change or a

comment on something you submitted. If someone needs more detail from you, you can reply right from that notification; there's no separate portal to log into.


🥯 06 Customer 360: your view into every account

Customer 360 gives GTM users read-only visibility into all the feedback and roadmap activity tied to your accounts, without needing full platform access.

Look up a specific account

Search for the account by name to see:

  • A roadmap view — every idea tied to that account and where it stands (submitted, in progress, shipped, and so on).

  • An evidence table — every individual request or comment logged for that account, whether or not it's been tied to a formal idea yet.

This is the fastest way to prep for a call: check what's already been asked, what's

already planned, and what you can proactively update the customer on before you ask them anything new.

Explore by segment

Instead of one account at a time, filter by a segment — a region, a tier, an industry — to see demand across a whole group of accounts at once. This view shows how many separate accounts have asked for the same thing, which is useful when you want to make the case that something matters beyond just one customer.


🥯 07 Good habits

  • Check for a match before submitting — it takes a few seconds and keeps requests from getting split across duplicates.

  • Be specific. “Wants an API for Xˮ routes and gets prioritized far better than “wants an integration.ˮ

  • Use Customer 360 before every renewal or QBR call — it's the fastest way to know what's outstanding for that account.

  • When in doubt, submit it anyway. Triage is built to sort and route on your behalf — a request is always better logged than lost in a Slack thread.


🥯 08 FAQ

Do I need a Bagel login to use any of this?

No. Submitting a request works through the browser extension or your CRM.

Customer 360 is the only part that needs a login, and it's a lightweight, view-only

role built specifically for GTM use.

What if I'm not sure whether something is a real product request?

Submit it anyway. The product team reviews everything and will decline politely

with a reason if it's not a fit — that's a normal part of the process, not a mistake on

your part.

Can I see what other accounts in my segment have asked for?

Yes — that's exactly what the segment view in Customer 360 is for. Filter by region,

tier, or another segment and see demand aggregated across accounts.

Who do I ask if I have questions?

Send any question in the shared channel you have with Bagel — we're here

to answer.


🥯 Make every feature count 🥯

Did this answer your question?