Front users

Hi everyone,We’ve been experiencing consistent performance issues with Front across multiple users, and I wanted to check if anyone else has run into something similar.The main problems we’re seeing:Frequent freezing: when switching between conversations or navigating through the app, the UI becomes unresponsive for several minutes unless the page is refreshed Incorrect conversation rendering: selecting one conversation sometimes shows a completely different thread in the main view Wrong assignment display: conversations appear assigned to the wrong users in some casesThis has been happening across different users, devices, and both web and desktop versions. It started recently and wasn’t an issue before.We’ve already tried clearing cache/cookies and doing fresh reloads, but the issue persists and comes back intermittently.Has anyone experienced similar behavior?

Hi everyone,I’m trying to figure out the best way to track performance for users who work across multiple shared inboxes.In our case, the user have access to analytics in more than one inbox, but reporting is still separated per inbox. I’m looking to understand if there’s a way to get a combined view of metrics like messages sent, reply time, and first response time across all inboxes user works in.Right now, it seems like the only option is to pull reports seperatly and combine them manually, which isn’t very efficient.Has anyone found a better way to handle this? Maybe through exports, integrations, or a specific workflow inside Front?Thanks in advance!

Hello, Curious if anyone has seen any rules (outside of the “standard” rule set that really helps CS teams perform well? I am aware of the SLA features and love those, but any creative workflows or sequences anyone has seen work really well for Customer Success teams?

Hey folks,We started using the knowledgebase for internal tips and tricks about Front. I’m bringing in other team members to brainstorm how it can be used across our organization internally, and where it might also be useful externally. How are your teams using the knowledgebase? 

Hi everyone,We've been exploring Copilot's suggested replies feature and ran into a couple of things that have us a bit puzzled. Hoping someone here has experienced something similar or can shed some light!For context, we use WhatsApp exclusively and have our knowledge base set up with Q&A entries.The "email" thingWhen a suggested reply gets skipped, we hovered over the ⓘ icon and saw this tooltip:"Did not suggest a response because it looks like the original email does not contain any question."The message was sent via WhatsApp. Why does the tooltip reference "email" here? Is this expected behaviour, or something else?The matching feels very literalThis one was eye-opening. We have a Knowledge base article titled "Can I use contraception while breastfeeding?", Copilot only generates a suggested reply when a user types that question verbatim. The moment someone asks anything slightly differ

Hey all! Thinking through utilizing automation when possible while also giving the customer a positive experience. Where should teams draw the line between automation and personalized responses in Front, especially when dealing with sensitive logistics issues like lost or delayed shipments?

For those in logistics or similar high-volume environments:Are you routing by issue type, customer, or shipment status? Any best practices for avoiding overlap between ops and support teams?Would love to hear how others are structuring this.

Currently, Front lacks a native mechanism to "undo" a merge. Once two conversations are joined, whether manually by an agent or through automated threading logic, they are effectively locked together. In the fast-paced world of logistics, this creates a "Merged Entanglement" that poses four significant operational risks:• Mixed Shipment Data: If an email regarding Shipment A is merged into a thread for Shipment B, critical attachments or instructions can easily be overlooked. A single missed detail in our industry can lead to a stalled truck or a failed delivery.• Broken Analytics: Accuracy is the backbone of our operations. When two distinct business events are tracked as one, our "Time to Resolve" (TTR) and "Messages per Shipment" metrics become skewed, providing an inaccurate picture of team performance.We propose a native "Unmerge" feature that allows users to split conversations back into their original, distinct components. Key requirements

Hi Front Community, Just a quick update for all Asana plugin users — we’ve added support for creating tasks using task templates 🎉 Task templates in Asana can be created by selecting “Convert to task template” from a task’s options (note: this feature is only available on paid plans).  Once your selected project includes templates, you’ll see a new field in the task creation flow. Choosing a template will automatically populate fields based on that template, helping you create tasks faster and keeping things consistent with your existing Asana workflows. This feature was requested here:

Hi everyone,I’ve been reviewing how we use tags in Front, and I feel like things can get messy if not structured properly.Currently, we use tags like:Billing Technical issue Follow-up UrgentBut over time, more tags keep getting added, and it’s becoming harder to maintain consistency.I’m wondering:How do you structure your tagging system (simple vs detailed)? Do you limit who can create tags? Any best practices to keep things organized long-term?Would really appreciate insights from teams who’ve scaled this well!

I tried integrate Live Chatbot widget to our documentation page but the app does not dynamically change the background image. Any suggestion? Thank you.

We are new to Front and happy to be here. We will be using Front in a new Scaled Customer Success Model. What tips would you provide in using Front for this specific model? 

Has anyone connected Front to Planhat? If so, did you find that this connection was worth your time? 

Hi,Is there a possibility to use data (e.g.Company Names) imported from Salesforce to create specific Views tied to this Data?Right now it is a workaround of adding Tags and then create a View with the Tags, but it would make more sense to use the imported data that is already there.

What recommendations do you have for any new users coming into Front for the first time?  What’s the first thing you would recommend they do to set themselves up for success in using the tool effectively?I look forward to the discussion.

I am currently exploring options to connect external services not currently available in Front. We are aware of Front´s metric and analytic capabilities but will still need a bridge or integration. The application in question is Amplitude.Since there isn't a native integration or plugin, I’m curious how others are doing this. For those of you who have moved past Zapier/Make and into Custom Plugins, was it difficult to set up the connection? 

Currently, Front’s tagging system is proactive: it works perfectly for messages coming in after a rule is set. However, logistics is often about identifying patterns after the fact.We currently have to perform manual searches and use "Bulk Actions" to tag messages. This is time-consuming, prone to human error, and often misses archived or moved threads. As such our Front Analytics reports are incomplete for the first 14 days of any new issue, making it harder to provide our shippers with accurate historical data.We propose a feature that allows Admins to apply a Tag (or trigger a Rule) retroactively.1. Selection: Create a Tag or Rule (e.g., If body contains "Toll Increase" -> Add Tag "Finances").2. Backfill Option: A button that says "Apply to Historical Conversations".3. Time Parameters: A date-picker to define the look-back period (e.g., Last 30 days, Last quarter, or Custom Range).4. Background Processing: A status bar indicating the progr