Tag a teammate in a deal review call comment by selecting transcript text, setting visibility, typing @ and their name, and confirming the handoff.
Key takeaways
- Anchor the comment to the passage that prompted the action.
- Check the audience before posting.
- Tag the owner with a clear request and deadline.
- Follow up for the specific answer you need.
Deal review calls move quickly. A forecast call can cover several opportunities in one sitting, and a manager often hears something that needs one specific person to act on it. A champion has gone quiet. A pricing question needs finance. A security concern belongs to whoever owns the technical review. The trouble is that a general remark made during the call can fade. It lands in a shared notes page or becomes one line in a recap, and the teammate who owns the next step may never see it as their job.
A call comment can help with that, if you use it well. In Gong, a comment can be attached to a specific passage of the call and can tag the people who need to respond.
The steps use Gong's help page for adding a comment as the reference. Your call tool may work differently, so read its own help pages before you copy these steps. The principles still apply in any tool: be specific, be clear about who should see the note, and make the next action unmistakable.
Every call has more open questions than it has time to answer. The notes that matter are the ones a teammate can act on without a follow-up meeting, so the work is less about writing more and more about writing the right note in the right place.
Step 1: Select the exact words you want to comment on
Select the exact words in the call transcript that your note is about. Do not leave the comment floating over the whole call. In Gong, click Transcript and select the text you want to comment on, as described in Gong's help page for adding a comment.
Anchoring the comment to a passage matters because the teammate who opens it gets the context at once. Suppose a buyer says the legal review has to be finished before their budget cycle closes. A general comment that reads "check legal timing" makes the reader search the recording to learn why it matters. A comment attached to that sentence sits next to the words that created the action, so the reader can see the trigger without guessing.
Choosing the right passage takes some judgment. Pick the moment when the risk, question, or commitment first came up, not the moment you finally wrote your summary. If a buyer raised a concern and the rep answered it, select the concern, because that is the part someone else must act on. If the answer also matters, mention it in your note rather than selecting a second passage.
Keep the selection tight, usually a sentence or two. A long highlighted block makes the reader work to find the point, which defeats the purpose of attaching the note. If the passage runs long, split it into two comments, each anchored to its own point.
Before you move on, read the selected text one more time and ask whether a teammate could understand the note without replaying the call. If the answer is no, add a short quote of the key line. You are not transcribing the conversation. You are giving the next person enough to act without a search.
Think about the same moment from the owner's side. They may not have been on the call, or they may have been on it and busy with another deal. Your selection is the bridge between the recording and their task. A tight anchor and a clear note give them a short path from the question to the answer.
Here is a quick contrast. A weak note says, "Follow up on security." Attached to the whole call, it tells the owner almost nothing about which concern was raised, who raised it, or when. A stronger note is anchored to the buyer's sentence about the questionnaire and says what you need from the owner. The stronger note takes little more effort to write, and it may save the owner a round of questions.
Anchoring also helps coaching. When a rep handled an objection well or poorly, the passage shows exactly what was said, so the feedback stays tied to the call rather than to memory.
Step 2: Decide who can see the comment before you post it
Decide who can see the comment before you post it, using the setting above the comment box. In Gong, you can choose specific people to see the comment, or make it visible only to you. Setting the audience before you type keeps the note from reaching a wider group than you meant.
Not every note belongs in front of the whole deal team. Some notes are coaching points, such as a question about how a rep handled a pricing objection. Others are reminders you want to think through before you raise them with anyone. A note about a teammate's performance, for example, belongs with that person and their manager, not in a thread that a wider group can read. Decide who the note is for first, then write it for that audience.
Visibility also shapes tone. A comment written for one person can be direct about what went wrong, because the audience already has the context. A comment written for a larger group needs to stand on its own. Leave out the backstory that lives in your head and state the facts the reader needs: the account, the passage, the request, and the deadline.
Consider three kinds of audience. The first is only you, which fits a thought you want to return to before sharing. The second is specific people, such as the owner and their manager, which fits a note that asks for action. The third is the wider team, which fits an issue that affects the forecast itself. Each choice suits a different kind of note. Use the narrowest audience that still gets the action done. A narrow audience keeps sensitive notes contained, and a wider one is right when the whole team needs the information.
When you are unsure, start with the smaller audience and share the substance with the wider team in your own words at the forecast. That keeps the detailed note contained while the wider team still hears the outcome.
Visibility is also a good place to judge the note's purpose. If the note asks someone to act, it probably needs a tag as well as the right audience. If the note is only context, it may not need a tag at all. Keeping that distinction clear keeps your tags meaningful, which matters in Step 3.
For example, suppose you hear a buyer ask about data residency on a call that a regional manager also attended. The question matters to the deal, and the solutions owner must respond. Share the comment with the solutions owner and the regional manager, who needs to know. Keep the rest of the team out unless they need the answer to make a forecast decision. The example shows how the audience follows from the purpose of the note, not from habit.
Step 3: Tag the teammate who owns the next action
Type @ and the teammate's name to tag the person who owns the next action. The help page says you type @ and the name "to tag a person or a team," so you can tag a team when the next action belongs to a group rather than one person. The same page says you "can tag up to 50 people in one comment." That is a ceiling, not a target, and a long list of tags rarely makes a note clearer.
Tag the owner, not everyone who might be interested. Each tag should match one action. When several people are tagged in one note, each reader may assume the request is meant for someone else.
Name the task and the person in the same sentence. For example: "@the security owner, the buyer needs the security questionnaire before their procurement window opens. Can you confirm the due date with their IT lead before our next forecast call?" That sentence tells the owner what to do, why it matters, and what to send back. It does not ask anyone to replay the call, and it leaves no doubt about who is responsible.
A second example shows the same pattern for a pricing question: "@Marcus, the buyer asked whether we can hold the current price through the end of the quarter. Can you tell me by Friday whether finance can approve that?" Each note names one person, one request, and one deadline.
If two people need to act on different parts of the deal, write two separate comments instead of one long comment with two tags. Each comment can point to its own passage, and each teammate gets a clear item. Separate comments also make it easier to see later which request got a reply.
If someone only needs to know, a tag may be the wrong tool. Use the visibility setting from Step 2 to share the note, and keep the tag for the person who has to respond. This keeps tags meaningful, so a tagged teammate can tell at a glance that the request is for them.
When the owner is a group, tag the team and say which role you need covered. The note should still state which decision you need and by when, so whoever reads it on the team knows what to do next.
Write the request as a request. Vague notes such as "Thoughts on this?" invite a reply that does not move the deal. A clear note names the item, the deadline you need, and the form of the answer you want, such as a date, a yes or no, or the name of the person who will handle it. For related planning, see sales follow-up checks.
A simple way to check any tag is to ask four questions of the note: who is it for, what do they need to do, by when, and what should they send back. If the note answers all four, the tag is doing its job. If one answer is missing, add it before you post.
Step 4: Follow up to confirm the handoff
Gong's help page says that when you tag someone in a comment, the call appears in Collaboration > Received on their homepage. That gives you a specific place to point the teammate if they miss the tag.
Seeing a call in a list is not the same as agreeing to act on it. Treat the tag as the start of the handoff, not the end. Close the loop in the channel your team already uses, such as a direct message or the deal's shared thread. A short message gives the teammate context outside the tool: "I tagged you on the Acme security comment from today's call. It needs a date from their IT lead before our next forecast."
Ask for a specific reply. Instead of "Can you look?" ask for the date, the owner, or the yes or no you need before the next call. A specific question makes the answer easy to give, and it makes a missing answer easy to notice.
Set a date to check back. Put the item on the agenda of your next forecast call, or on a short follow-up list, so the request does not drift. If the teammate has not replied by then, the request still stands, and you can follow up in the same way. Use the forecast call agenda checks when preparing that review.
If the date passes and nothing has come back, ask again in the same channel and keep the request short. Repeat the passage you pointed to, restate the one thing you need, and offer an easy way to answer, such as a yes or no. A shorter second request is easier to answer than a long reminder that repeats the whole history of the deal.
Review what came back. At the start of the next review, look at the comments you tagged and see which ones got a reply. Replies show you which requests landed, and silence shows you where to follow up. The same review also tells you whether your notes are clear enough, because a note that gets no response may need a clearer request.
Watch for two failures. The first is a tag with no request, so the teammate sees their name and does not know why they were tagged. The second is a request with no owner, so everyone assumes someone else will handle it. Both are usually fixed by going back to Step 3 and rewriting the note with one clear name and one clear action.
A comment does not close a deal by itself. It moves a specific question to a specific person, and the rest depends on the follow-through that comes after.
Illustrative example: Turn a concern into a handoff
Select the transcript sentence where the buyer raised the concern. Share the comment with the security owner and tag them with this request: "Can you confirm the review date with the buyer's IT lead before our next forecast call?" If the owner replies with a date, bring that answer to the review. If no answer arrives, keep the question on the agenda and follow up in the same channel.
Try it today
Open your most recent deal review call and choose an unresolved question. Check its comment for an owner, a deadline, and a requested answer; add whichever part is missing.
Common questions
Does a tag confirm that someone has read the comment?
A tag alone does not confirm that the teammate has read the comment or agreed to act. Ask for the specific answer you need to close the handoff.
Should everyone who can see a comment be tagged?
Tag the people who need to act; visibility can give others the context without asking them to respond.
What should I do when a tagged teammate has not replied?
Follow up in the same channel with the passage and the specific answer you still need.