AI + Workflows

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 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

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 einzubeziehen. * Wie man die Team-Zusammenarbeit verbess

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.

Hello.  I am looking for any suggestions on how to use system variables in Connectors.  I have a moderate amount of comfort working with APIs.  I have a Connector set up and working - POST requests are working and creating records in our third party app without issue.I cannot seem to be able to figure out how to pass system variables through our POST request.  I can create dynamic variables in the Connectors, but these do not seem able to access basic system data.  I have tried every variation I can think of - {{user.name}}, user.name, etc. but all this does is pass {{user.name}}, user.name, etc.to the created record.  I’m hopeful system variables can be passed through the Connectors and I am just missing something very obvious.  Any input is welcomed and appreciated.  Thank you!

I’m trying to set up a rule in Outlook that will automatically follow up on an archived email in a specific mailbox after 7 days, sending a reminder to respond. 

Hey everyone,I’m working on setting up a Knowledge Base for internal use, with the goal of providing reference documentation for a team that interacts with my department. The idea is to create a centralized resource where team members can easily find the information they need without constant back-and-forth.I’d love to hear your insights! Here’s what I’m considering for an effective setup:

Hello everyone, I am looking to use the Knowledge Base to answer our client’s non-technical FAQ’s s. This would increase our productivity by not having to ask a teammate the same questions repeatedly. Has anyone had experience with this? In a perfect world we would be able to set rules for auto response with these answers as well.  Looking forward to hearing everyone’s ideas and experiences with this.

As we’re in setup, does anyone have any good advice in terms of keeping it simple but impactful in terms of the connectors we’re building. How should we think about connectors and their applications within Front. We have a development team and want to make sure we’re prioritizing the right work for connectors. Looking for a framework to help us think about this prioritization. 

Hello, since this morning we have not been able to send our emails via front (we receive however),we have gmail addresses and others specific to our company, none of which work when sending.I checked Front Status nothing is declared,It worked perfectly until yesterday,anyone have an idea???

We are currently utilizing two e-mail addresses for two workspaces.  These sometimes overlap.  I was wondering if anyone has had success in going from multiple e-mail addresses to just one and still be able to assign tickets automatically to the proper workspace?Did you utilize Rules to make this successful?

Hi All,I’d like to learn more about how Front interacts with Global Distribution Systems (GDS) and how that relationship is structured. Specifically, does Front collect Passenger Name Records (PNRs), and does it offer a plugin or integration that allows PCCs to be connected, enabling ticket issuance from GDS bookings?Looking forward to your insights. 

Hello,I am trying to set some custom rules and I am missing AND condition. There is only OR condition available. I have seen Front demo videos that showed AND condition but it is not possible for my to change OR to AND. I have Growth plan but I don’t see any difference with Scale plan here https://front.com/pricing when looking at workflow rules.

Hey guys im new here and i just wanted to know more about - How do you use custom fields in Front to create an escalation procedure for critical conversation? I would really appreciate if anyone can answer to this post thanks!Archie

With Front folders, you can sort by date and reply status. I wish there was a way to re-order threads arbitrarily, similar to cards in a Trello list, so that we could have a shard todo-list style work queue.Anyone have ideas on how to do something like this, whether within Front or through an integration (e.g. with Trello or Slack)?