How to create and manage brief types

Business admin
Gong Foundation
Admin Center > Agent studio

Note:
Contact briefs and the ability to add CRM data and information from the web are rolling out in September 2025.

Briefs are structured summaries that organize key information relating to a specific account, deal or call. They serve as quick, standardized overviews for tasks like preparing for meetings, handing off accounts to other teams, or understanding deal progress. Brief types are the structured templates that define what will be defined in a specific brief.

This article walks you through how to create, test, and publish brief types so that they contain the information that matters most to your team.

Create a brief type

Go to Admin Center > Agent Studio, hover over AI Briefer and click Settings.
Click + Brief type and choose a brief type: account, call, or contact.
Choose whether to:
- Start with a preset brief type and customize it, or
- Create from scratch.
Under Settings > Info, give the brief type a name and description.
Under Sections, choose which type of section you want to add:
1. Conversations: Summarizes conversations in Gong. Choose whether you want to ask Gong AI to find the answer or use a smart tracker to find relevant snippets. If you choose to have Gong AI find the answer, ask a question and add details or examples to help the AI understand what to look for. See tips for writing great instructions
2. Web: Summarizes information on the web. Ask a question and add details or examples to help the AI understand what to look for. See tips for writing great instructions
3. CRM or Gong data: Displays data from the CRM or Gong. In these sections, you can format the answers with bold, italics, bullets and more, and add variables to add dynamic data. See tips for adding variables to brief types
Click Test to preview results from any section.
To preview the entire brief type, click Preview at the top of the page.
When you’re satisfied, click Save, then click Publish to make the brief type available for your team.

Test sections and brief types

Test a section

After entering a question and instructions, click Test.
For account brief types, choose an account, deal, and period.
For call brief types, enter a call URL.
For contact brief types, select a contact.
Click Test it.
To test on a different account, deal, period, call, or contact, click Change.

Test a brief type

After you’ve set up the entire brief type, click Preview in the top-right corner.
For account brief types, choose an account, deal, and period
For call brief types, enter a call URL
For contact brief types, select a contact
Click Test it.
If you’re satisfied with the results, click Publish. To test on a different account, deal, period, call, or contact, click Change.

How to write for Gong AI

Writing instructions for Gong AI takes practice. Test your instructions on calls and accounts you’re familiar with, until you get results that you’re satisfied with.

Use natural language: Write the way you’d speak to a colleague
Ask open-ended questions: Encourage descriptive answers
Be specific: Ask clear questions about the conversation content
Clarify terms: Define terms that are ambiguous or jargon
Guide Yes/No answers: Use the instruction field to explain what details to include in the response

Examples questions and details

Here are some instructions from our preset brief types.

Question	Details and more information
Did customer's team members directly communicate their company's pain points? If yes, what were they?	A valid pain point must be a specific business problem that our solution could address - an area where the customer is currently struggling and that our solution could help solve. Valid pain points examples: - Losing efficiency due to manual processes - Lacking visibility into important metrics - Having difficulty scaling their current processes Not valid pain points: - General technical requirements - Lack of formal processes - Budget constraints - Generic statements about wanting to improve Please only include pain points that were explicitly mentioned by the customer’s team AND that our solution could help solve.
Was any factual information explicitly mentioned in the conversation about who the customer is as a company and what they do as a business?	Include details such as: - Their industry - Market segments - Company size - Products/services Avoid including any details about their relationship with our company.
What is the customer’s current tech stack?	Include existing systems to be replaced, required integrations, APIs, third-party platforms, databases, and any technical dependencies that were discussed. Include details about data migration requirements and specific technical configurations that were mentioned.
What are the growth opportunities with this customer?	Focus on growth opportunities with our company’s products and services.
What is the implementation rollout strategy?	Include future implementation milestones, implementation timelines, onboarding phases, key deliverables, resource requirements, and training plans.
Which other solutions does the customer consider, and how do these solutions compare to the customer?	Focus on any known competitors without stating if none were mentioned.
Did the customer's team members directly communicate their company's business objectives and strategic goals?	Please focus ONLY on the customer’s broader organizational goals that were explicitly stated by their team members - not assumptions, our analysis, or their goals for using our product. Examples could include their stated growth targets, market expansion plans, product development roadmap, or other high-level business initiatives mentioned by the customer personnel during the conversation.
Who are the key players from the customer involved in the buying decision for our product? Why are they considered key players?
What is the customer's decision-making process for closing the deal with us?
What criteria does the customer consider when evaluating our solutions?
Are there positive indications that this deal will close? If so, what are they?	Deal positive closure indicators are explicit statements and actions that a prospect is genuinely moving toward a purchase decision. They typically include buying signals of engagement and progress such as: -The prospect openly discussing their challenges or goals (demonstrating genuine interest and need). - Sellers and buyers agreeing on mutual next steps or action items (showing forward momentum). - Active involvement of key stakeholders, i.e people who can make or influence the final decision. - Confirmation that technical or security requirements are satisfied, indicating fewer risks remain. - Expressions of trust or excitement about the solution, suggesting the buyer believes in its value.
Are there negative indications that this deal won't close? If so, what are they?	Negative closure indicators are explicit statements and actions that a prospect is not interested or is considering not proceeding with the purchase. They typically include negative buying signals of hesitation and lack of interest such as: -Budgetary challenges or insufficient funding to support the solution. -Explicit statements of disinterest in the product or frustration with the sales process. -Lack of participation or engagement from key decision-makers, i.e. people who can make or influence the final decision. -Hesitation or non-committal responses (e.g., missing follow-ups, no clear timeline). -Unresolved objections or concerns from the prospect side that remain unaddressed.

How to add CRM and Gong data to briefs

Add dynamic data from your CRM and Gong to your briefs with variables. Learn more about using variables.

Tips for adding variables to brief types

Click {} to open the variables menu, or type {{ to open the variables menu inline
Format the results so they are easier to read with bold or bullets
Match the variables you select to the brief type: For example:
- For deal types, add deal-related variables
- For account types, add account-related variables

*The features available to you depend on your company’s plan and your assigned seats.