Recently active topics

Hi Front team,We’re building a sidebar plugin that loads our plugin page https://samplesite.com/front-plugin inside the Front UI. Front adds ?auth_secret=… to our iframe URL, and we’re trying to  bootstrap the SDK per the docs:  <script src="https://app.frontapp.com/scripts/sdk.js?auth_secret=…"></script>  Our page (HTTPS, same origin as the SDK allow‑list) loads one script at a time and retries the fallback URLs:  - https://app.frontapp.com/scripts/sdk.js  - https://app.frontapp.com/plugins/sdk.js  - https://app.frontapp.com/static/frontend-plugin-sdk.js  For each request we append the auth_secret from the iframe URL. We also guard against multiple insertions, remove existing script tags, and even tried adding  type="module".  What we’re seeing  In Firefox and in Chrome the script load always fails:  - The browser console shows:    Access to script at 'https://app.frontapp.com/scripts/sdk.js?auth_secret=…' from origin 'https://www.samplesite.com' has been blocked by CORS p

Hi I’ve been struggling to have our contact list up to date and it would really help me to have the ability to mass delete auto-created contacts. Perhaps you can integrate this feature or at least allow front support to have an internal way to achieve this.

We've just released an AI prompt file that lets you scaffold Front plugins using any AI coding agent—Claude Code, GitHub Copilot, ChatGPT, Cursor, and more.Simply describe what you want your plugin to do, and the AI generates a working plugin that follows best practices, correctly uses the Front Plugin SDK, and includes built-in debugging tools. What used to take hours of learning our SDK now takes about 10 minutes.Why this matters:Speed - Get from idea to working plugin faster than ever Correctness - The AI handles Front-specific patterns and boilerplate automatically Accessibility - Lower barrier to entry—you don't need to be a Front SDK expert to get started Best practices - Ensures plugins follow established patterns for Front data models and context handling from day one Debugging - Built-in tools show exactly what's being sent to your plugin during developmentWe've built three example plugins using the prompt—a NetSuite manager, subscription manager, and attachment encryptor—to s

Hey all, Patrick from Front’s Support team here! I wanted to share a video demonstrating a workflow that our support team leverages to optimize and semi-automate customer interactions using some of our Front AI features:Topics: Automatically detect and label the topic of the customer inquiry, ensuring that each message is categorized and prioritized accurately. Copilot suggested replies: Suggests a complete reply that not only provides the full answer but also includes links to relevant help documentation, making responses both thorough and resourceful. AI Compose: Adjusts the tone of the email to match the desired style, ensuring a more personalized and empathetic interaction.This AI-powered workflow significantly reduces the time our support team spends on answering common questions, allowing us to dedicate more time to complex inquiries. The best part is customers get faster responses from us all around, leading to higher CSAT. Check it out: Let me know if you have questions or want

Hi, I am new to front and wanted to learn from others that have a small group of 2-5 sales reps and how they are currently using front and what type of automations are helpful to ensure a smooth customer experience while ensuring the app is being used proficiently?

Hello Front community! I was thinking about the “Edit Sidebar” button and the possibility to have more buttons to edit inboxes or views or tags without accessing “Settings” to edit these inquiries,

Hi,In playing around with app requests, I have noticed that it’s possible to map JSON output to dynamic fields, which can in turn update a custom field on the conversation using a rule. However, this seems to only work for a single property. My question is about updating multiple custom fields on the conversation. Is it possible to update multiple custom fields in response to a single application request, without triggering duplicate app requests for each dynamic field? Or is the best approach for this use case to have my backend update the custom fields directly via an API call?For example, I would like to ping my backend with a single request to get the user’s current subscription plan and their renewal date, and update two custom fields (plan and renewal date) on the conversation without triggering a separate application request for each field. The alternative is to ping my backend once with a custom request and have the backend itself update the custom fields by hitting Front’s API

Hi, I am setting up a new support portal, and started an Enterprise Trial so that we would have access to application requests so that we can hit our custom API. After setting up an app request, testing it successfully (“Test Successful”), and the status is “Ready,” it is NOT surfacing when selecting the “Select app request” action in a new macro/rule workflow. See the screenshots below.This is the app request, showing “Ready” status: And when creating a new macro, it keeps telling me to setup a new application request, because it cannot find the ones I have created:Is there something wrong with my account setup? Why can’t I use the app requests in rules/macros?