How to create and manage brief types

Business admin
Gong Foundation
Company settings > Customize analysis > AI Briefer

The AI Briefer standardizes and streamlines knowledge sharing by generating structured briefs based on brief types. Build customize brief types for any use case by modifying one of Gong’s preset brief type, or create a brief type from scratch.

Create a brief type

Go to Company settings > Customize analysis > AI Briefer.
Click + Brief type and choose whether you want to build it for accounts or calls.
Choose whether you want to start with a preset brief type and customize it, or create a new brief type from scratch.
Under Settings > Info, give the brief type a name and description.
Under Sections, add a section for each topic you want summarized. Give each section a name and choose whether you want to ask a question that Gong AI will answer in this section, or use a smart tracker to find snippets that are relevant to the topic.
If you choose Ask Gong AI, enter the question you want answered in the first field. In the second field, add details or examples to help Gong AI understand what you’re looking for and find the right information. See tips for writing great instructions.
To see the type of results the instructions produce, click Test AI. To see test results the entire brief type will produce, click Preview.
Click Save to save the brief type, then click Publish to make it available for your team. .

Test sections and brief types

Make sure the AI Briefer delivers the results that you want from a specific section or brief type by testing the instructions on a real call, deal, or account.

Test a section

After entering a question and instructions in the AI instructions section, click Test AI.
1. For deal and account brief types, this opens a testing dialog where you choose an account, deal, and period.
2. For call brief types, this opens a testing dialog where you enter a call URL.
Fill in the fields and click Test it.
If you’re satisfied, continue with the setup. If you want to test the instructions on a different account, deal or period, click Change.

Test a brief type

Once you’ve set up the brief type, click Preview in the top right of the screen.
1. For deal and account brief types, this opens a testing dialog where you choose an account, deal, and period.
2. For call brief types, this opens a testing dialog where you enter a call URL
Fill in the fields and click Test it.
If you’re satisfied with the results, click Publish. If you want to test the brief type again, click Change.

Tips for writing great instructions

Writing instructions for brief types takes practice. Test your instructions a few times, on calls and accounts you’re familiar with, until the AI Briefer produces results that you’re satisfied with. Here are tips to get great results.

Use natural language: Write how you would talk 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.

Example 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.

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.

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