Front users

How do I import my emails with the help of API to front from an email platform other than Gmail and Microsoft 365? 

Hey Team, Is there a way to setup domain based routing to multiple inboxes? Will each inbox receive a copy separately or is there a way to route a single copy to a inbox based on load balancing? 

Hi all,I’ve been exploring automation features in Front and I’m curious how other teams balance automation with maintaining a personal customer experience.Automation definitely helps with:Faster response times Reducing manual workload Organizing conversations efficientlyBut at the same time, I’ve noticed that too much automation can sometimes feel less personal for customers.For example, I’ve seen workflows where:Auto-replies are sent instantly Conversations are routed automatically without reviewI’m wondering:How much automation do you currently use in your workflows? Have you ever reduced automation to improve customer experience? What’s your approach to keeping responses efficient but still personal?Would love to hear different perspectives and real examples!

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!

Hello Team,I’d like to get the community’s perspective on how best to interpret workload metrics at the inbox level.For my team, I typically track performance using tickets created vs. tickets resolved across each inbox. However, in the Front workload report, we have the following metrics available:New conversations Moved into inbox Moved out of inbox Resolved conversations Unresolved conversationsGiven these, I’m trying to establish the most accurate way to calculate true ticket creation and resolution per inbox.My current approach is:Created = (New Conversations + Moved into Inbox) – Moved out of Inbox Resolved = Resolved ConversationsThe idea is to reflect the net workload that actually lands and stays within an inbox, rather than inflating volumes through internal

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?

Our company has been using Front for many years across nearly every department, including Support, Sales, Ops, Sales Support, and Finance. As we’ve grown more distributed, we are looking to move away from a "one-size-fits-all" business hours setting to get more accurate analytics and finally implement SLAs for all teams.We have a complex geographic footprint: Global Support: Distributed worldwide, providing near 24/7 coverage. Ops & Sales Support: Primarily U.S. East Coast (Mon–Fri, 8–5). Finance: Based in Europe, operating on a completely different workday. After looking into Front’s documentation, I see there are a few ways to structure this (Workspace-level vs. Inbox-level hours), but I’m wary of the trade-offs.I’m curious to hear from other global teams: which of these approaches have y

The recent update put the delete button behind an ellipses. That’s a terrible idea. My laptop does not have a delete button. Give me my button back :(

Hi everyone!We recently expanded Copilot to a few more of our teams at their request. They saw it being used by other teams and were interested in the conversation summaries and suggested replies.As we roll this out further, I would love to hear from those who have used these features for a while: The "Honeymoon" Phase: How has the sentiment evolved? Does the team still find the summaries valuable daily, or has it become "background noise"? Accuracy: How reliable are the conversation summaries? Do your teams find them accurate for long threads, or do they still feel the need to read the entire history anyway? Suggested Replies vs. Manual Edits: Do your agents find the suggested replies "ready to send," or are they mostly using them as a skeleton and spending significant time editing them? Knowledge Base Integration: F

Does Front automatically change your availability status from “Available” to “Busy” when you join a meeting that is on your Outlook calendar and synced to Front? Right now, when I join a meeting through my Front calendar my availability doesn’t change automatically, so I still appear available. It feels like this is a feature that should automatically work.

All outbound emails through Microsoft365 receive - Remote server returned '550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP. Can anyone assisit in troubleshooting. Sending emails from outlook no worries, just front. P.S. we are in trial mode.

We’ve released Front Desktop v3.71.1, which resolves an issue that caused a “file not found” error when the application was installed in directories containing space characters.

Hi everyone,I was wondering if anyone has set up a rule that automatically takes tickets that have been in a “Waiting” status for a certain period of time and sends an automated response like:“Closing the loop here as we haven’t heard back from you. Please feel free to reach out if you have any additional information.”Then moves the ticket to a resolved status.Tried creating this ( see below) but for some reason when I test conversation for this rule, Front gives me a warning message saying “Condition isn’t supported for testing”. If anyone has any idea why this is happening, it’ll be super helpful!Thanks!! 

We've revamped the Connectors Academy course to reflect all the recent improvements to the no-code framework—and this time, you'll build something you can actually use right away.The updated course walks you through building a Connector with Asana that lets teammates create a new task in Asana directly from Front. Along the way, you'll learn how to:Chain multiple app requests together to pull in workspaces, projects, and tasks from Asana Build dynamic dropdown menus that let teammates select the right project, task, or any other context—adaptable to any use case, like selecting the correct order for a customer! Use pagination and other new Connector features recently added to the platform Arrange complex logic visually in the flow builder, including using app request nodes to perform external actions without writing that logic inside a dynamic variableHead o

Hello Front Community! 👋 I'm Greg, Front's Director of Corporate IT & Enterprise Security, and I'm thrilled to share how our team is leveraging Front to revolutionize our internal IT support. It's been a while since my last update, and with all the exciting product enhancements over the last year, I couldn't wait to give you a fresh perspective on our journey.Some of these features that I am going to talk about are in beta, so contact your Front account team or our Support team should you have any questions or want to try them out yourself! Quick Snapshot of Our IT LandscapeOur mighty team of five handled an average of 120 tickets per month in 2024. We're proud to report an average ticket resolution time of

Hello! So our plan is to quickly setup and use Front to handle all customer feedback, organise it and make sure we do not miss anything important. We will have a few mail channels and maybe a couple of other types in time to come. Based on your real world experience what are the most important steps to follow in order to ensure a clean base setup in front?

Since there’s no native Google Chat channel, how is your team bridging the gap between internal chat and Front without losing context?

Hi everyone,I manage a shared inbox environment where multiple team members handle a fairly high volume of operational emails from different regions. One workflow that has helped us a lot in Front is combining Rules + Tags + Assignments to keep things organized and avoid overlap.Here’s how we structured it:• Automatic tagging by keywords or sender domain – For example, emails from certain partner domains automatically receive tags like Vendor, Logistics, or Client Support.• Rules to assign conversations – Based on the tag or email subject pattern, the message gets automatically assigned to the responsible team or teammate.• Status visibility using tags – We also use tags such as Pending Vendor, Internal Review, or Waiting for Customer so anyone opening the conversation can quickly understand where things stand.This helped u