# Flag VIP customers in Front with a HubSpot snapshot and Slack alert > Every 30 minutes, tag inbound Front conversations from top-tier HubSpot customers as VIP, drop a CRM snapshot in the thread, and ping your #vip-support Slack channel when nobody is on it yet. - Workflow type: agent - Services: Front, HubSpot, Slack - Categories: Customer Support, Sales - Published: 2026-07-08 ## What it does - Sweeps your Front inboxes every 30 minutes and picks up open conversations that have not already been marked as VIP. - Looks up each sender in HubSpot to check lifecycle stage, deal owner, and pipeline value so you know exactly who is asking. - Adds a VIP tag to matching threads in Front and posts an internal note with the CRM snapshot so anyone opening the ticket sees the context. - If the VIP conversation is still unassigned, sends a Slack alert to your escalation channel with a link straight to the thread. ## What you'll need - A Front account with access to the shared inboxes you want scanned and permission to add tags and internal comments. - A HubSpot login with read access to contacts and deals so lifecycle stage, owner, and deal value can be pulled. - A Slack workspace and a channel you use for VIP escalations (for example, #vip-support). - An agreed definition of VIP for your team (lifecycle stage, deal value threshold, or specific owners). ## Prompt Build an agent workflow that triages inbound support conversations for VIP customers by cross-referencing Front with HubSpot and escalating in Slack. Trigger: run on a cron every 30 minutes. On each run, the agent should do the following: 1. Use Front's Search Conversations to pull open conversations across our shared inboxes updated in the last hour. Skip any conversation that already carries the VIP tag so we do not double-process it. 2. For each remaining conversation, take the primary sender's email address and call HubSpot Search Contacts to find a matching contact. If no contact is found, skip the conversation. Do not guess and do not create a HubSpot record. 3. If a contact is found, read their lifecycle stage, owner, and company. Then call HubSpot Search Deals filtered by that contact or their associated company to pull the latest open deal, its stage, and its amount. 4. Decide whether the sender is a VIP using these signals: lifecycle stage is Customer or Opportunity, or there is an open deal above a configurable value threshold, or the account owner is on a configurable list of strategic reps. Expose these as parameters when you set the workflow up so we can tune them without editing code. 5. For every conversation that qualifies as VIP: a. Use Front's Add Tags to Conversation to add the VIP tag, without removing any existing tags. b. Use Front's Add Comment to post an internal note on the conversation summarizing the CRM snapshot: account owner, lifecycle stage or tier, latest deal name and stage and amount, and any notable open items you were able to see (for example, other recent HubSpot tickets). Keep it short and scannable, no fluff. c. If the conversation is still unassigned in Front, use Slack's Send a Message to post an alert in #vip-support with the customer name, one-line reason they qualify as VIP, and a direct link to the Front conversation. If the conversation is already assigned to a teammate, do not post to Slack. Do not reply to the customer, do not change the assignee, and do not modify existing tags beyond adding the VIP one. This workflow is read-plus-enrich only. Ask me for the Slack channel name, the deal value threshold, and any specific owner emails that should always be treated as VIP. Default the channel to #vip-support if I do not provide one. ## How to customize - Change the definition of VIP by tuning which lifecycle stages, deal sizes, or account owners count as top tier. - Point escalation alerts at a different Slack channel or private group, or route to a specific on-call person via direct message. - Adjust the sweep cadence, for example every 15 minutes during business hours and hourly overnight. - Broaden or narrow which Front inboxes are scanned, or skip conversations that already have a specific status like Snoozed. ## FAQ ### What happens if a sender has no HubSpot record? The conversation is left alone. The workflow does not guess or create a placeholder record, so cold inbound and personal senders are not flagged. ### Will the Slack channel get pinged twice for the same conversation? No. The workflow skips any Front conversation that already carries the VIP tag, so once a thread has been flagged it will not trigger another alert. ### How is VIP actually decided? You define it. Common signals are a lifecycle stage like Customer or Opportunity, an active deal above a value threshold, or a specific account owner. You can combine any of these when you set the workflow up. ### Do teammates need to see the CRM data inside Front? Yes, and that is the whole point. The workflow posts an internal comment on the thread with owner, tier, latest deal stage, and any notable open items so the agent replying does not have to bounce over to HubSpot. ### Can I run this on private inboxes as well as shared ones? Yes, as long as the Front login you connect has access to those inboxes. You can also limit the sweep to a specific set of inboxes if you prefer. Use this prompt in General Input: https://www.generalinput.com/prompts/flag-vip-customers-in-front-with-a-hubspot-snapshot-and-slack-alert