Workflows discussion

I have a question about my company workflow. I’d like to connect Front to my Quickbooks online to track orders coming in to my inventory and posting transactions. Often customers email me a Purchase Order with a dynamic link that can be routed to Quickbooks online for inventory purposes and to also send payment links back to the customer. Does anyone here have experience setting this workflow up? Any recommendations you can offer before I get started?

Does anyone else find themselves feeling overwhelmed, intimated and/or just scared when making the switch from their old email to the Front system? I LOVE the features that Front offers users, but I’m an old school believer of “if it ain’t broke, don’t fix it” lol. With my daily work I utilize email and teams for all my communications so I kind of laugh at the thought of an email that combines the two when I can easily just continue using them to be productive during my work days. Again, this is probably just me being stubborn and the fact that I don't like change. Please feel free to share with me your thoughts and/or experiences so far during your switch. Any tips/tricks you’d suggest? (Other than taking advantage of the community forums/courses/training Front already offers users?)  

Hi community,  We have an idea of greeting our customers on a birthday by email. Does anyone know whether it is possible to automate this process via Front and how? Thanks for any help.

Hey everyone,I'm currently exploring the best way to efficiently route emails from our main company channels to region-based workspaces and could use some insights and suggestions from the community.Here's the context: We utilize the email address sales@ourcompany.com as our main point of contact, which gathers web forms from our website. These web forms include a field indicating the country/region of the customer.Currently, we have a company rule in place that assigns certain countries to specific team members. However, we're looking to revamp this process to enhance efficiency and streamline operations.Ideally, we envision a solution where emails are first routed to a designated workspace based on the region indicated. From there, the workspace would apply specific rules tailored to that region, such as assigning quote requests to the appropriate Sales Development Representative (SDR).If anyone has experience or suggestions on how to set up such

Hi community,  In some cases, we use notes to save additional information about the clients. I am wondering whether it's possible to use notes data in rules using built-in Front rules or probably via Zapier?

I am trying to setup automatic follow ups for when we reply to a support email from a customer, and we don’t hear back from them in 48 and 96 hours. I have the follow rule set for the 48 hour part below. For some reason, this isn’t working / it doesn’t send any emails.  Has anyone been able to setup a similar workflow? Trying to figure out what I’m doing wrong.

Is it possible to create a workflow to automatically send welcome emails to new contacts or contacts with a certain tag? 

Hey everyone,I hope you're all doing well! I'd like to kick off a discussion on a topic that's been on my mind lately: managing rules and tags for inboxes that primarily receive website form submissions.Here's a bit of context: At our company, we route numerous website forms to an email address that serves as our primary channel in Front. Each of these forms has its own structure and includes a separate field for custom messages. To streamline our workflow, we've implemented rules based on tag-words to categorize and route these submissions effectively.However, we've encountered a significant challenge: the potential for misinterpretation. For example, a tag-word like "US" intended to assign a submission to our America Sales Team could inadvertently be applied to a form where someone simply wrote "help us" in the custom message field.I'm eager to hear from fellow community members who may be dealing with a similar setup. How are you managing rules and tag

I am trying to remove the footer that Google adds automatically when forwarding emails to an external address in a Google Group. I already followed this article, which helped quite a bit but instead of removing the footer altogether, it just added a smaller one:“To unsubscribe from this group and stop receiving emails from it, send an email to help+unsubscribe@xyz.com”  Has anyone found a solution for this? I’ve ticked off both the standard Groups footer and the custom footer. 

Would like to tag contacts in Front based on whether they are paying users or not (based on Stripe data, where we keep our subscriptions). I was surprised to see there is no Stripe app in the AppStore, has anyone built a similar workflow?

Is there a method to link multiple incoming emails through the subject line so they are assigned to the same person (when using “round robin”)? Eg. in our workflow, we receive alerts/incoming emails for each step of a booking process. So that could be:1. Partial lead2. Quote completed3. Booking made4. Contract signed5. Payment receivedEtc etc. Using the round robin method, it would break up each of the 5 workflows and assign them to different agents.  Whilst the subject is different, the one constant is the lead number within the subject line. How would we set a rule for this if the lead number is dynamic and we don’t know it ahead of time?

Hi all - maybe I am just still to new to Front, but I cannot figure out how to personalize the satisfaction survey in the signature. I have already referenced the “Front's CSAT feature” help link but it only mentions that you can, not how to do it.  We are deciding between adding our own questions or linking our own survey. Currently the resource we use for survey’s now does not work internationally at times. Any guidance is much appreciated! 

Hi all!I am curious if anyone has any examples of how you used rule sets to make your rule library more efficient/manageable. i.e. replacing multiple rules with one rule which leverages rule sets. I am curious if and how folks are leveraging this functionality to improve workflow management and overall processes. Thank you!

One of the rule features that I love is requiring a tag before an email can be moved or archived. However, I’m struggling with how to utilize this with a large number of tags.Our company works with hundreds of schools, and routing emails to teams is partially based on the school that the email is regarding. We have rules set up to automatically tag emails with the relevant school tag, however there are times when an email needs to be manually tagged.Since school tags are required to ensure messages are routed to the correct team, I want to set up a rule to require the school tag be added on an email before it can be moved. However, listing all of our 1,000+ school tags in the rule is not practical, and it’s difficult for team members to pick from when the list is that long.We do have additional subsets of these tags based on where the school is located (ex. Canada, UK, etc) that are added automatically when one of the school tags is added. I had initially looked

Does anyone use unique setups to mimic shifts by shared inbox? This is not currently available (idea submitted), only shifts by workspace. Our support team is scheduled on specific shared inboxes based on day of the week. Example:Mon: Voicemail InboxTues: Voicemail InboxWed: Main Email InboxThur: Main Email InboxFri: Voicemail + Email InboxesWe use teammate groups in round robin assignment rules, and add shifts based on reps working hours.Reps are assigned to teammate groups based on the inboxes they are trained on (example using the above schedule, the associate would be assigned to teammate groups: Voicemail Reps, Main Inbox Reps).The issue we have is that reps will receive assignments from the Voicemail Inbox and Main Inbox every day, vs only receiving Voicemail conversation assignments M/Tu and Email Wed/Th. The only workaround I have come across is creating a daily assignment rule per shared inbox which requires f

Hi,  Oftentimes, the responses to emails from our clientele are derived from previously scheduled requests. Since there is no way to predict if the request is going to be a new request, a rescheduling request, or something for a complete department adding on the load balancing seems like it would put us a disadvantage. What ways have you found are the best rules or reasoning for implementing the balancing in that case? 

Hello friends,I am impressed with workflow when using Front. Immediately I finish writing my prayer, I send it both to the recipient and to the archive box for safety. This facilitates my workflow. I just do it instantly and it is easy to retrieve. For me workflow is the most beautiful thing using Front.

Hi friends,In our company we deal with prayer requests. Front knowledge base has facilitated my workflow in the smooth response to prayer requests.I have used tagging teammates to so that we work together and help each other. And this has been very effective indeed. 

We’re working on beefing up a few of our review websites and are struggling a little bit with the cadence of sourcing these.  Right now, we have emails come in from our NPS letting us know when we have a 10/10 come in. It then gets assigned to the the relationship manager and they are supposed to reach out via a template.  I’m curious if there is a way to remove the manual email outreach for each relationship manager and automate that template sending and still including the individualized signatures (so it looks like a personal email from the “account rep” in the eyes of the customer)

We’re just about to launch Front with our team (YAY!) and one of the key features we’ll be using is Round Robin. I was just wondering, if one of our team members goes on leave and turns on their ‘time off’ settings, what happens with emails that would normally go to them in the round robin routing?  I hope this makes sense! I thought there was a learning path that covered it, but I can’t seem to find it. Thanks in advance! 

Hi there everyone!A fellow coworker and I are brainstorming ideas for how we can use Dynamic Objects within our workflow. We have started using it in a few small cases and would really like to see how much farther we can go with it.What are some ways in which you use dynamic objects in your workflow? We have a few applications that don’t have existing plugins in Front that I could see being extremely helpful via dynamic objects. I believe there is a way to build those out ourselves, or am I mistaken?Thanks for any help!

Harnessing Front's Power with Slack Integration: Streamlining Communications and Boosting Efficiency 1. Does Front's Slack Integration Reduce Direct Slack App Usage? Have companies observed a decrease in direct Slack App usage after implementing the Front Slack Integration, especially for common tasks like interdepartmental communications about order fulfillment and invoice payment? 2. Centralized Action in Front: How has the Front Slack Integration, in conjunction with Front’s comment and Dynamic Object features, enabled companies to streamline action and conversation within Front, promoting centralized activity and increased efficiency? 3. Advocating for Front: What strategies have worked successfully to promote Front as the primary communication platform and central hub for workflows, instead of the Slack App itself? 4. Efficiency and C

Does anyone have specific use cases of how they have added in dynamic objects to increase efficiency of their teams? 

I am new to the Front Community, but my employer has been using Front for approximately 4 years now.I am in the process of completing the FCA exam and needed to add a post. 

HiOur team of 5 receive email requests into the shared inbox from a defined pool of around 50 service users. Sometimes it might be two or three months between an email from the same person.Currently, we’re finding that a new email request will often attach to an old thread from that same service user, even if that thread was previously archived (sometimes months, even years ago!) The new email will also be assigned to the same person who dealt with the original thread.Similarly, if the same service user sends over multiple requests in a short period, they all end up attaching to each other and being assigned to the person who dealt with the original request.This can make it harder to spot the new requests, as it looks they are already assigned and being dealt with by another team member.I suppose what I’m asking is, is there an easy way to prevent new emails attaching to old archived threads? Thanks for any ideas!GarethPS We ar