Front users

I want to optimize the rules in our company account. Several rules delete unwanted messages.All of them have a sender address as a condition. Some of them have AND condition with text in the message’s subject.Is it possible to have a wildcard in the second condition that means “anything or nothing” in its subject? Maybe a character asterisk * or just an empty field?I don’t want to do tests in the working environment.With the wildcard, I can create one rule set for both types of messages.I would like to use a wildcard in other rules, too. See the example rule and its table: 

Hello Team,  Could you please advise on whether the archived conversation will be reopened after tagging the team members? Thanks 😍

Hey team, Could you please clarify the difference between Trash the conversation and Archiving it? Thanks 😍

Which of the data points can I get in my Overview report in Front? 

Our team utilized SLA features to prioritize and manage response times, helping us maintain consistent service standards. Adding SLA warnings to the rules helps hitting your SLA targets.

Hi there,We’re a small team and half of us have a break in the logo that’s been working fine in our signatures for years. Any ideas? The code appears consistent across the team.

Hello, Seeing if anyone has found a way natively, or if there is a feature that will pull text from attachments within Front, to create rules off of?Thank you!

For anyone who has connected your ERP with Front via API.What is the most valuable (and usable) information you have found that you need to have available, within Front, that you pull from your ERP that is connected to Front?What is the information that you wish you had earlier before your integration with Front, and what problems has it solved now that you are connected? 

Hello All, We have multiple outside vendors that provide us with tracking information for products we ship.  The problem we face is that ever one of them does it differently.  We are currently having to go through multiple emails, attachments and other systems to put things together.  Most of the relevant information is available in Front in one manner or another. My question is, can Fronts AI function parse information from attachments as well as the email body and make summaries based on information found?  Alternately is there an API solution for being able to extract information from the shipping companies?  Im looking for any suggestions as we spend a lot of man hours sending the tracking information to our customers and feel like we spend too much time digging for the information prior to sending to customers. Any help is appreciated, Thank You!

Hello everyone. We are trying to pull information off of incoming emails that are requesting quotes. We want to take what they send us, compare it to our quoting system’s requirements to generate said quote, and then either automatically email the sender the information we are missing or if we have everything we need, we simply send them the generated quote automatically. Can this be done solely within Front?

I’ve been using the sequencing feature to do some marketing / sales outreach. The last round of sequences I sent out went to around 800 contacts in total and I had no issues with bounces or spam.This time around, the email we were using got marked as spam by Microsoft just before the last sequence went out and they all bounced. Has anyone run into this before? Any recommendations on where to go from here? The sequences we build for the next couple of months are supposed to be sent with this email. 

My signature line has disappeared and I cannot find a place within Front to work on this

Looking for feedback on possible options in creating an automated method of tagging emails based on which workspace the email lands in and then based on which inbox the workspace contains.The idea is to assign a company level tag if an email lands in one of the two workspaces. Which is a simple enough company level rule. If email lands in any of Workspace A inboxes then assign Workspaces A Division Tag. The next step is to assign the department that’s currently responsible for handling the email. There are multiple main inboxes with each workspace and each main inbox containing sub-inboxes. Therefore, if an inbound email arrives or is moved from a different main inbox then the tags that should remain are the Workspace Main Tag and Only the Department Level Tag. If an email lands in one of the sub-inboxes the workspace tag and department tag remain along with any other specific tags that have been applied.The challenge that I’m facing is that if the email exists within two inboxes of th

Hey everyone,I’m new to Front and really excited to explore everything it can do - both internally and externally. There’s clearly a lot of potential, and so I’m curious:What’s helped your team build consistent habits with tags, rules, or shared inboxes?I’d love to hear any best practices or little things that have made a difference in adoption or team workflows.

Does anyone know how to make it so that the CC address line is always available and I don’t have to click CC to open the line?

I’m having an issue integrating front with individual users who receive direct communication from clients on new requests and ensuring these requests are handled within our dedicated SLA times. The team dedicated to handling new incoming orders (Client Service) should be the primary team that receives all new requests, while the other handles updates on existing order (Client Experience). The issue that we’re facing is that the client services team has one inbox that handles all incoming orders, while the client experience team each use their own unique inbox to respond to client concerns or requests for updates. I’d like to utilize Front to mirror this set up within our client experience team, but still allow transparency when clients are reaching out to ensure SLA’s aren’t breached our missed by each Client experience rep.  In addition, there are times that clients will email new orders to the client experience rep and exclude the client services team what would be best method to ens

How does Front work with Microsoft DLP, aka Purview?  For compliancy, outbound messages need to be scanned for sensitive information, leakage, and security.  Also, things like labels for content, etc.

As a new Front user, I have just recently begun to experiment with the "Invite guests to conversations or internal discussions" feature. This feature allows you to bring external collaborators—such as clients, vendors, or contractors—into specific email threads or internal discussions without granting them full access to your inbox or workspace.Benefits I’ve noticed: Improved collaboration: Instead of forwarding long email chains or creating new threads, you can bring a guest directly into an existing conversation. This helps reduce confusion and ensures everyone is aligned. Streamlined communication: It keeps all related messages and participants in one place, cutting down on scattered emails and improving response times. Controlled access: Guests only see the conversations they’re explicitly invited to, which helps maintain security while still enabling collaboration. Challenges as a new user: Understanding permissions: Initially, it wasn’t entirely clear how much visibility a gu

Our organization is using ClickUp to manage work by creating a ticket for each task. In the case that we are using Front as the primary communication tool with clients, how do we ensure seamless transition between ClickUp tasks updates and collaboration comments in Front?

Anyone know where I can find a Front Consultant?  Front was already in place when I started here about two years ago and has been problematic since day one.  Our Front setup is a hot mess and generates way too many helpdesk tickets for all kinds of different reasons.  I really need someone that can look at our setup, analyze it, suggest and make changes.  I’m an IT Manager but I don’t have the bandwidth to revamp our whole Front setup.  A Google search turned up nothing and Front doesn’t seem to offer such a service that I can tell.  Any insight would be greatly appreciated. Thanks

New to Front and wondering if anyone has SLA tips and tricks for a team that covers all time zones in the US?

Hey Front Community! 👋I’m curious to hear how others are approaching Rules in Front. Have you found it easier to create rules based on custom fields at the account level or the inbox level?What has worked best for you? Have you run into any challenges with either approach?Thank you!

Hallo Front-Community,wir erleben in unserem E-Commerce-Geschäft regelmäßig saisonale Spitzen, die zu einem massiven Anstieg an Kundenanfragen führen. Aktuell haben wir damit zu kämpfen, die Reaktionszeiten aufrechtzuerhalten, ohne die Qualität unserer Antworten zu beeinträchtigen.Wir nutzen Front, um alle unsere Kommunikationskanäle (E-Mail, Chat, Social Media) zu zentralisieren, was bereits hilfreich ist. Allerdings suchen wir nach spezifischen Workflows oder Automatisierungen, um diese Spitzen effizienter zu bewältigen.Hat jemand Erfahrungen mit ähnlichen Herausforderungen gemacht? Insbesondere interessieren wir uns für: * Regeln zur automatischen Priorisierung von Anfragen basierend auf Keywords oder Dringlichkeit. * Vorlagen oder Snippets zur schnellen Beantwortung häufig gestellter Fragen während der Spitzenzeiten. * Integrationen mit anderen Tools (z.B. Lagerverwaltungssysteme), um Echtzeitinformationen in unsere Antworten einzubeziehen. * Wie man die Team-Zusammenarbeit verbess