These prompts are designed for current Breeze Assistant behavior in HubSpot. They work best when they include a direct task, clear context, an explicit output format, and a defined search focus such as the exact records, pipelines, files, lists, or date ranges to use. Breeze is especially useful when it is asked to analyze CRM activity, summarize relationships, prepare for meetings, identify trends, draft follow-up communications, and help structure workflow logic.
For Payments and Financial Infrastructure, Breeze is particularly effective for relationship intelligence, pipeline visibility, partner and merchant onboarding analysis, issue and support trend identification, deal acceleration, and internal coordination. This sector often involves complex, multi-step processes such as integrations, underwriting, risk reviews, onboarding, and settlement coordination. That makes well-structured prompts especially valuable for surfacing friction, identifying revenue opportunities, and improving execution across teams.
There are also nuances unique to this space. Payment processors and fintech platforms rely heavily on onboarding velocity, activation rates, and ongoing merchant engagement. Clearing and settlement operations involve precision, coordination, and issue resolution across multiple parties. Sales cycles often include technical stakeholders, risk teams, and operations, not just buyers. The prompts below are designed to reflect those realities.
Use your portal’s exact pipeline names, stages, segments, product lines, onboarding statuses, lists, and property names in the brackets below. That will usually improve output quality and make the results more actionable.
10 Breeze-optimized prompts for Payments & Financial Infrastructure
1) Merchant or partner meeting prep brief
Best for account managers, partnership teams, and sales reps preparing for merchant or platform conversations.
Prepare me for my meeting with [CONTACT NAME] at [COMPANY OR PLATFORM NAME]. Use the contact, company, associated deals, notes, emails, calls, meetings, tickets, and the last 12 months of activity in HubSpot. Give me: 1. a 1-paragraph relationship summary, 2. the account’s likely priorities based on recent interactions, 3. open support issues, onboarding delays, or integration challenges, 4. revenue or expansion opportunities suggested by CRM activity, 5. 5 smart questions I should ask in the meeting, 6. a concise follow-up email draft I can send after the meeting. Write this for a payments or fintech professional preparing for a high-value partner or merchant conversation.
2) Merchant activation and onboarding risk scan
Useful for identifying merchants or partners that are stuck before going live or fully activating.
Review accounts and deals in pipeline [PIPELINE NAME] where onboarding or activation is in progress. Identify the top 20 merchants or partners that appear at risk of delayed activation based on: - long stage duration, - missing required onboarding steps, - incomplete integration or technical setup, - overdue tasks, - low recent activity, - notes indicating confusion, delays, or dependency on external teams. For each at-risk account, provide: - why it appears at risk, - current onboarding or activation stage, - what is missing or blocking progress, - recommended next best action, - a short internal or external follow-up message. Output as a prioritized list from highest to lowest risk.
3) Support and transaction issue trend analysis
Strong fit for operations and support teams managing high volumes of merchant or transaction-related issues.
Analyze tickets, notes, and support conversations from the last [90/180] days for [SEGMENT OR PRODUCT LINE]. Cluster the top issues into categories such as: - failed transactions, - settlement delays, - chargebacks and disputes, - onboarding or KYC issues, - API or integration errors, - reporting discrepancies, - payout timing concerns. For each category, provide: - issue summary, - likely root cause, - representative examples, - whether this looks like a product, process, integration, or support gap, - the likely impact on merchant satisfaction and retention, - a recommended action for the team. Keep the output practical for a payments operations and support team.
4) Cross-sell and product expansion scan
Useful for identifying merchants or partners that could adopt additional products or services.
Review existing customers and active relationships using [CURRENT PRODUCT OR SERVICE] but not [TARGET PRODUCT OR SERVICE]. Use CRM history, associated deals, notes, meetings, tickets, and engagement activity to identify the top 15 expansion candidates. For each candidate, provide: - why they are a fit, - which signals support the recommendation, - likely angle for the conversation, - any onboarding or support issues to address first, - a personalized outreach draft for the account owner. Focus on relationship, usage, and sales signals in the CRM.
5) Stalled deal and integration review
Strong fit for sales and solutions teams managing deals that require technical integration or multi-team coordination.
Analyze open deals in pipeline [PIPELINE NAME] with expected close dates in [DATE RANGE]. Flag which deals are most likely to stall based on: - stage duration, - last activity date, - missing technical or integration milestones, - lack of stakeholder engagement, - overdue tasks, - notes indicating integration complexity, risk review delays, or unclear requirements. For each at-risk deal, show: - current stage, - why it appears stalled, - what is missing, - the best next move, - a suggested owner action for this week. Start with an executive summary, then provide the deal-by-deal breakdown.
6) Platform and partner relationship prioritization
Helpful for partnerships teams managing multiple platforms, ISVs, or referral partners.
Review our active partner and platform relationships in [SEGMENT OR PROGRAM]. Use CRM history, associated deals, notes, meetings, and engagement activity to identify: - the top 15 highest-priority partners, - partners with strong recent momentum, - partners that appear under-engaged, - partners that may be at risk. For each partner, provide: - priority level, - evidence supporting that priority, - likely opportunity for growth, - recommended next step, - a short outreach or follow-up message. Keep this practical for a partnerships team managing growth and retention.
7) Clearing and settlement coordination scan
Tailored for teams managing transaction flow, reconciliation, and coordination across multiple parties.
Analyze accounts, deals, and tickets related to [SETTLEMENT, CLEARING, OR TRANSACTION FLOW PROCESS]. Identify where coordination issues may be occurring based on: - repeated support tickets, - notes mentioning delays or discrepancies, - multiple stakeholders involved with unclear ownership, - long resolution times, - lack of recent updates on open issues. For each flagged account or issue, provide: - the likely coordination problem, - the stakeholders involved, - what is unclear or missing, - recommended next steps, - a suggested internal summary for alignment. Focus on improving clarity and coordination across teams.
8) Lost deal pattern analysis for payments and fintech
Useful for identifying patterns in lost opportunities and improving go-to-market strategy.
Review all closed-lost deals in pipeline [PIPELINE NAME] from the last [6/12] months. Group the losses by: - merchant segment, - product type, - objection themes, - competitor mentions, - stage where the deal was lost, - common missing capabilities, integrations, pricing alignment, or stakeholder engagement. Then tell me: 1. the top 5 loss patterns, 2. what we should change in our sales or onboarding process, 3. what product or enablement gaps may exist, 4. 3 actions we should take this quarter to improve win rate. Write this for a payments or fintech growth leader.
9) Ideal merchant or partner profile generation
Helpful for refining target accounts using real CRM data.
Analyze our closed-won deals and strongest customer relationships from the last [12/24] months for [PRODUCT, PLATFORM, OR PROGRAM]. Create an ideal merchant or partner profile using: - company types, - size or volume indicators if available, - geography, - contact roles, - engagement patterns, - sales cycle signals, - common needs or use cases from notes and calls, - objections that were successfully overcome. Then provide: 1. the profile summary, 2. key stakeholders to target, 3. top messaging angles, 4. early warning signs of poor-fit prospects, 5. the top 20 current open deals or companies that most closely match this profile.
10) Workflow builder for onboarding delays or support escalation
A strong operational use case for aligning sales, onboarding, and support teams.
Build a workflow for [PIPELINE NAME OR TICKET PIPELINE NAME]. Goal: identify merchants, partners, or accounts that are stalled, at risk, or experiencing onboarding or support issues. Criteria: - deal or onboarding stage has been active for more than [X] days with no progress, - no activity in [Y] days during onboarding or integration, - ticket priority is [HIGH] and no response in [X] hours, - repeated support tickets within [TIMEFRAME], - notes indicating delays, confusion, or technical blockers. Create a workflow with: - enrollment triggers, - if/then branches, - internal notification, - owner task creation, - internal note summarizing likely issue, - optional merchant or partner follow-up draft, - exit criteria, - suppression logic to avoid duplicates. Show the workflow in a clear step-by-step structure.
Two practical notes
Sensitive data note
Teams in payments and financial infrastructure should avoid entering highly sensitive or regulated information directly into prompts. This includes full card data, bank account details, authentication credentials, nonpublic transaction records, or sensitive compliance-related information. Breeze is most effective when it is pointed at the right CRM records and activities without exposing unnecessary sensitive details.
How to get the most out of Breeze Assistant
For the best results, use the exact pipeline name, stage, onboarding status, product line, partner type, and date range in the prompt. Ask for a specific output format such as a prioritized list, executive summary, breakdown by account, or outreach draft. The closer the prompt matches how the team actually manages onboarding, integrations, transactions, and relationships in HubSpot, the more actionable and valuable the output will be.
