sales-front

name	sales-front
description	Front platform help — AI-powered customer operations platform with shared inbox, omnichannel support (email, SMS, chat, social, WhatsApp), Autopilot AI resolution, Copilot agent assistant, Smart QA/CSAT, ticketing, knowledge base, 160+ integrations, full REST API with webhooks, seat-based paid tiers. Use when setting up Front for a support team, shared inbox assignments not routing correctly, Autopilot AI resolving wrong tickets, comparing Front to Missive or Hiver or Zendesk for team email, Front API returning 400 on conversation search, connecting Front to Salesforce or HubSpot via API, analytics reports showing zero values, wondering if Front is worth the price vs cheaper alternatives, or configuring Front webhooks for real-time event processing. Do NOT use for help desk platform comparison across tools (use /sales-helpdesk-selection). Do NOT use for CCaaS/contact center selection (use /sales-ccaas-selection).
argument-hint	[describe what you need help with in Front]
license	MIT
version	1.0.0
tags	["sales","customer-service","help-desk","shared-inbox","platform"]
github	https://github.com/frontapp

Front Platform Help

Helps with everything related to using Front — an AI-powered customer operations platform combining shared inbox, omnichannel support, AI automation (Autopilot, Copilot), ticketing, knowledge base, and a full REST API with webhooks. Used by 9,000+ companies for support, operations, and account management.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What are you trying to do with Front?

   • A) Set up Front for the first time
   • B) Configure shared inbox routing and assignments
   • C) Set up AI features (Autopilot, Copilot, Smart QA)
   • D) Build an API integration or webhook listener
   • E) Connect Front to CRM (Salesforce, HubSpot)
   • F) Compare Front to alternatives
   • G) Troubleshoot performance or data issues
   • H) Something else — describe it

2. Which plan are you on (or considering)?

   • A) Starter ($25/seat/mo) — up to 10 seats, single channel, basic analytics
   • B) Professional ($65/seat/mo) — up to 50 seats, omnichannel, SSO/SCIM
   • C) Enterprise ($105/seat/mo) — unlimited seats, Copilot/QA/CSAT included
   • D) Not sure yet / free trial

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.

Step 2 — Route or answer directly

If the request maps to another skill, route:

• Comparing help desk platforms → "Run: /sales-helpdesk-selection {user's original question}"
• CCaaS / contact center evaluation → "Run: /sales-ccaas-selection {user's original question}"
• CRM integration strategy → "Run: /sales-integration {user's original question}"
• Live chat strategy → "Run: /sales-live-chat {user's original question}"
• Chatbot strategy → "Run: /sales-chatbot {user's original question}"

Otherwise, answer directly from the platform reference below.

Step 3 — Front platform reference

Read references/platform-guide.md for the full platform reference — capabilities, pricing, plan gates, API details, data model, integration recipes, and code examples.

Answer the user's question using only the relevant section. Don't dump the full reference.