Workflows discussion

Hello,Is there a way to view history of changes to email subject Front? to see who updated the subject title. 

I have two minor gripes about front chat and was curious if anyone knew of a workaround.  After replying replying to a chat message directly from a chat inbox it assigns it to the person replying and the chat disappears as it moves from the chat inbox to the teammates assigned inbox. This is minor but it is annoying to have to reply → click to your assigned inbox and find the message → continue conversation.  Is there a better workflow there?   We have ticket statuses enabled for our chats. Once you have replied and you are actively chatting with a customer it is a bit annoying to have to constantly select the “send as open” option from the dropdown when replying. Is there a workaround there without having to change your default send option in personal preferences? Ideally we would like to be able to quickly chat back and forth with a customer without having to manually select a send option or have the chat disappear and reappea

Hello, I use a custom view to alert me when we have staff working on conversations in the wrong in box which works great. I move the conversation off to the correct in box but would like to add one more step. To track these wrong in box conversations (stats purposes) I’m now placing a tag on them manually. Is it possible to build a rule using the view settings to add a tag automatically? The rule would add the tag 📫 to any conversation captured by the settings for the view I have set up. Is this possible?  Thanks, Harry

Hello, Is it possible to create a dynamic variable to use a conversation name? For example, when we authorize a claim the claim number is in the conversation name during the email exchanges. Once the email is authorized it would be great to add the variable into our authorization template for responding and save several steps that might get missed. 

I exclusively use FRONT however, it is MUCH easier to right click/print and drag/drop attachments from Ouitlook. My issue is that there are so many emails that stay in the Outlook inbox it makes the ones I want to print hard to find. Does anyone know of an easy way to keep the Outlook inbox clean besides manually filing/deleting emails ?

We’re looking to enforce tagging when a support ticket is marked as Resolved — ideally from a predefined list of tags we use for resolution classification. We’ve been able to enforce tagging when conversations are moved or archived, but this doesn’t appear to apply when someone simply changes the status to Resolved (e.g., using status buttons or automatically in sending a response).We rely on tagging for resolution audits and postmortems, so ensuring consistent tag usage at closeout is important.Before submitting this as a feature request, I wanted to check if anyone has successfully configured this in their workspace.Here’s a screenshot of the rule that isn’t working the way I’d hoped: 

Hello, What we would like to do is provide a web link in an account's description box such that is would take them to a specific Knowledge base page related to dealing with that particular account. I do not have admin ability, and it appears this is not possible but is it possible as an administrator or is there some other way to accomplish this? We of course can put a note to go to Knowledge base and search for the article but that is rather convoluted with too many steps. This might also be done with a rule but that would be far more complicated than adding a link if possible. Can you add comments via a rule that contain a web link?

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: 

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.

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?

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

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

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?

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 einzubezieh

I created 2 inboxes managed by 2 different teams. We are merging the teams, what is the best way to consolidate the inboxes moving forward while keeping the history separate?

Hey folks,  I used the tool of shifts in Front for my team, and I wanted to share with all of you that this has been a great way to know who is working at which time and to define the worktime for the team so everyone who is available or outline can be responsible for the correct tasks. How to make this? Defining their shifts is essential because that will help us determine the correct OOO times for the team. I love it! I can see the fluency of the team's work in the analytics session.

Hey team, I have learned about Front and the great tools we as a company have to make decisions most effortlessly as a team. What tips do you have to start using Front for a company? We already used Front and the essential tools, but not everything is organized correctly. So, what are the first steps you took to make Front the best thing for your company?  Thank you! 

One of many things I use Front for is to view my team members’ calendars to see when all parties are available to meet.  I am constantly scheduling in my line of work (consulting)… so I have to look at 3-4 peoples schedules within 1-2 weeks, find openings that we have in common, take note of those openings, then provide the client will all possible options.  Is there any scheduling assistant tool or integration that can help with this? To me this would be an amazing AI feature… not sure if that already exists as well.  I would love to select team members and get a “summary” of all of our availability so I can copy/paste that in an email to a client. Or even prompt AI to get this information for me using the Front calendars.  Does anybody have answers or ideas?  

Given that fields like IP Address and Current Hour are available when building chatbot Dynamic Variables, you can utilize these to route visitors arbitrarily to one of a couple of paths. This example shows using the last part of a user’s IP address (a number from 0-255) to route the user through path A or B;Example of A/B testing chatbot pathsIf their IP ends in 128-255 - sent them through Path A, otherwise (0-127) it’s Path B - this gives us a ~50-50 split.Why do this?You might want to test a new iteration of a path and check it’s performance with a small group of visitors (maybe limit it to 10%) before rolling out the change more widely.