Why Front?SolutionsPricingResourcesContact Us
One Pager - 3 Min Read

Automation through Webhooks

Introduction to Webhooks

You may already know about Front’s Open APIs and have utilized them before to do things like fetching the details about a recent conversation or export analytics data. But are you interacting with data between your systems in a real-time dynamic way? If you aren’t using our Webhooks integration, the answer is probably no.

With traditional REST APIs (like that which you’ll find in our Core API), you can programmatically retrieve or post updates to Front. For example, I could list all of the conversations I’ve had with a particular contact or add a tag to any specific client conversation. What if I wanted to do something like add a tag based on the customer region in a CRM like Salesforce, or assign the conversation to the Account Manager? This information is dynamic and could change at any moment, and you want to leverage it in real-time.

Webhooks solve this problem and provide you the layer of interactivity you need. They introduce a “don’t call us; we’ll call you” concept to your tech stack and enable you to perform real-time logging of the activity or even dynamic updating to Front’s system.

Here’s an example to show how this could work:

webhooks

Imagine you want to have a real-time dashboard that shows the total number of new conversations vs. reopened conversations vs. archived (closed) conversations. In our old world of REST APIs, you’d have to continually call Front to see if anything has changed, when maybe only one of those calls would return any new data.

Front and Webhooks integration

Using Front, you can enable the webhooks integration and configure a rule that triggers a Webhook server notification.

webhooks 2

Once you enable the integration, you’ll see a dropdown in your rule actions to “Send to a Webhook.”

webhook 3

Define your server address here. You can use your server, own or you can even make use of middleware like Zapier, to receive the webhooks and trigger other cascading lookups, logging, or actions. Each webhook event you receive will contain information like the conversation ID, author, contact (etc.) You can find a preview of the event payload here.

What else can I do with the Webhook?

Front’s Webhooks integration is just the beginning of cascading actions. Here are just a few examples of things customers have done using webhooks through Front:

  • Log all events to a data warehouse in real-time

  • Trigger a lookup in your CRM and assign the conversation to the appropriate Account Manager

  • Create a real-time dashboard displaying information about the number of conversations touched by your reps

  • Add a comment to the conversation in Front containing additional information from your back-end systems

While Webhooks may be the trigger that informs you of new data, you’ll probably still want to leverage our Core API to do things like update the conversation assignee or add a comment. Our Webhooks integration often won’t stand alone in accomplishing your goal.

P.S. Worried about security? You can also secure your webhook by validating the payload originated from Front

If you have any questions about how to leverage Front’s Webhooks feature or just want to brainstorm, feel free to get in touch with us at api@frontapp.com

Keep learning

Guide - 6 Min ReadManage customer messages with ease
When it comes to managing customer messages, our approach is to save time sorting through, escalating, and assigning messages and spend it instead on improving the quality of the engagement with your customers. This is a guide on how to adopt that philosophy and make it simple to manage customer messages. #Setup Set your team up for success Make it easy on yourself and your team by doing some quick work on the backend that’ll make it simple for them to handle incoming messages.  Roles and permissions As you add new teammates to a team inbox and expect them to tackle customer communication, be sure to choose the right permissions for each person.  Default On any Front plan, you’ll be able to assign each teammate one of two default roles: Team Admin or Team Member. Here’s a table that covers what permissions are enabled for each role. Many leaders choose a selection of teammates to be Team Admins so they can help you create rules, track success with analytics, and keep the team inbox in check.  Custom If you have an Enterprise plan, you can create custom roles and permissions. Say you want the Team Lead to be responsible for creating all message templates and rules. Custom roles and permissions allow you to create a role with those unique abilities in Front. Then later down the line, when you want 2 other teammates to do the same, you can simply give them that same role and be on your merry way.  Shifts and load balancing  Shifts and load balancing prevent customer messages from getting backed up in your queue, while also preventing individual teammates from being overloaded with work. When you set up shifts, messages that are typically routed to someone who happens to be off duty will be flagged for someone who is on duty, so customers don’t have to wait for a reply. And, this means that when your teammate returns to work the next day, they aren’t immediately swamped with day-old emails. Another way to support your team is to set up load balancing, which places a limit on how many messages can be assigned to an employee at a given time .   You can monitor how much work each employee has in your Analytics tab. This way, you have an accurate sense of how much is on someone’s plate and can help distribute the work before your customers start to feel the impact of an overworked team.  Turn your inbox into your to-do list With Front, you don’t use a Read/Unread mentality. Instead, we use Open/Archive. With Open/Archive, your inbox is designed to be more of a checklist rather than a catch all. That way, there’s no confusion around what needs to be done: every message that’s in your inbox’s ‘Open’ tab needs to be worked on. So instead of leaving read messages left to cause clutter, snooze the ones you’ll get to later, and archive the ones that you don’t need to take action on. Easy emails to archive are: App notifications or reminders Emails informing you of something, but that aren’t prompting anything (think newsletters, daily reports, etc.) Conversations that seem to be ending (they’ll always pop back up if someone pings them again!) You can find any email in your Archive tab, so rest assured they won’t go missing. This way your open messages can be treated like your daily agenda, you inbox won’t stress you out every time you open your computer, and you won’t accidentally miss messages. #Organize & prioritize Organize your inbox There are many ways to sort and triage messages as a team in Front. You get to choose the methodology that works best for you. Assign messages an owner With Front you can give every message a clear owner so everyone knows what they’re responsible for handling. When you assign it, the message will appear in that teammate’s “Assigned to me” section of their inbox and will no longer be in the “Unassigned” tab in the team inbox. Your team can move on and rest assured it’s taken care of.  Tagging  Create tags to categorize messages by project, client, or urgency. Then, you can pin them to your workspace and drag messages into them. This way your whole team can see how to prioritize their work and what’s on the docket for the day.  #Route messages Triage and route messages No need to spend your time tagging messages, routing them to the right person, or flagging them as urgent to the team – set it up to happen automatically with rules and SLAs.  Rules  Rules are if-then automations that let you put certain actions on autopilot. Set up rules to automatically triage and route the messages for your team, so you can spend more time on your customer. There are a variety of ways that rules come in handy: Route messages to tags based on the content in the email or the sender.  Automatically assign messages by sender, subject, or keyword to a teammate with the expertise to respond. Avoid overwhelm and get back to customers faster by setting conversation limits for each teammate and automatically assign new messages to the teammate with the fewest open messages. SLAs Service level agreements (SLAs) are agreed upon response times between you and a customer, because people want to trust that they’ll get taken care of. Front’s SLA rules help your team meet these goals and stay on track. Set up SLAs and tags like “SLA breach warning” to make sure you never let a customer message fall through the cracks. #Audit & Improve Audit and improve So, you’ve set your team up for success, created rules to automate triaging, and your team is making customers happy left and right! It’s time to measure and showcase just how well your team is handling messages and find ways to improve.  Analytics  Analytics help you make informed decision and handle customer messages better. Track how quickly your messages are being resolved, how much each teammate is handling, or which customers write in the most, among other things.  Get visibility into what kind of messages you’re handling: By tagging messages by product, feature, location, customer, or project, you can track the volume and frequency of customer messages around certain topics. View a report on any tag in Analytics to figure out what kind of work your team is up to the most.  Track team performance: Track response time, handle time, resolution time, and more on a team and individual basis to see how your team is handling messages. This data helps you find ways to improve your customer communication, whether you’re deciding it’s time to hire more help, or finding a better way to distribute and escalate messages. 
Read more
One Pager - 5 Min ReadFront’s Rules Library: A collection of 26+ workflows to discover and customize as you scale
Typically, Rules aren’t that fun to talk about; like when you weren’t allowed to have dessert until you finished your broccoli.  Rules in Front, on the other hand, aren’t about restriction at all. We like to think of them as an invitation to customize Front to bring out the best in your team.  Front’s Rules are essentially the building blocks to automate customer communication and team workflows. They’re simple “if-then” conditions that reliably automate tasks to save time and increase your team's efficiency. In the backend, they look sorta like this:  Creating team Rules makes your workflow more efficient and helps you scale by automating tasks so you can spend time on your customer interactions instead. But we don’t want you to have to start from scratch.  Introducing the Rules Library, a curated collection of popular team Rule templates you can customize and use in a matter of clicks. Discover new workflows to implement for your team, and save time writing the recipe. The Rules Library serves as a source of inspiration, highlighting 26 of our most popular Rules. Not only can you discover new Rule templates for your team, but you can activate them in a snap – making managing your team much more efficient. The library is full of templates to help: Ensure your team replies on time Route messages to the right person or team Give your team appropriate visibility  Keep your inboxes tidy Increase your team’s efficiency   Ready to find new Rule templates and scale your team’s workflow? Here’s a preview of 6 actions you can automate from a template in our new Rules Library. 1. Never miss your Service-Level Agreement (SLA) Tag un-replied messages after a specific time elapsed to surface possible breaches. For example, if a support team has a 24 hour response time turnaround, you can automatically apply a tag like “SLA warning ” to messages approaching a breach to escalate them and signal to your team to prioritize that work.  Or, automatically assign messages at risk of a beach to a specific teammate so they can tackle it right away.  2. Automatically assign messages to a teammate after applying a tag and take that task off everyone else’s plate For example, perhaps Shanice handles all communication with Disney, a VIP customer. You can automatically tag their messages with a “VIP” tag, then assign them to Shanice so it’s the first thing she’ll see in her inbox.  Or, let’s say Tommy handles all escalated support inquiries related to a specific high-end component called ‘MDJ-11’. This Rule template could automatically assign him messages anytime someone on the team applies the tag ‘MDJ-11’. This saves the team time from having to manually apply the escalation tag and then also manually assign the messages to Tommy. 3. Get a notification when extra-important messages arrive Alert teammates to messages sent from a person or address. For example, Mike is the CEO of a critical account; you can use a Notify Rule template to ping your inbox whenever Mike emails any team inbox, be it support@, finance@, or complaints@, so you can keep an eye on, or even intervene, when needed. You could also configure the Rule to notify a CSM whenever their account writes into support, so they can reach out and make the personal connection.  4. Move messages to organize your team’s work Move emails to another inbox when needing to escalate an issue. For example, if a support request tagged as ‘tier 1’ can’t be addressed by that team team, the rep could apply a ‘tier 2’ tag, triggering this Rule to automatically remove the ‘tier 1’ tag and move the message to the tier 2 support inbox for that team to address.   You can even customize it to un-assign the message in the process, and route it to someone else. This saves that rep valuable time from having to manually remove a tag and move the message. Tag it and let Front do the rest so you can move on with your work. 5. Archive messages to clear up inbox clutter Archive email that don’t demand your team’s prioritization based on content.  For example, if you want to filter out non-urgent newsletter emails, you can use an Archive Rule template to archive messages containing the word “newsletter.” Remember that in Front, your inbox is your to-do list, so archive messages that don’t require action – you can always browse through ‘em later! You could also choose to automatically archive all dropbox edit notifications, calendar confirmations, or other non-personal emails that don’t require immediate attention. 6. Reply to messages that can’t wait  Send message templates to messages with a predictable reply, like when a message is received outside of business hours. For example, Rob’s shift is from 8 am - 5 pm M-F, and he wants to highlight specific resources for different accounts while he’s out. He can use the Reply Rule template to ensure each account receives an auto-reply with their personalized resources. We also like to automatically send a message template if a message hasn’t been replied to right away. We’ll let the customer know we’re on it if they haven’t heard from us within 12 hours, and then will tag the email with an “Urgent” tag so we know to look there first.  We’ll be adding more Rules to the library regularly, so check it out regularly. If none of the Rule templates in the library work, no problem; you can always create custom Rules leveraging ‘if-then’ conditions.  Head on over to the Rules Library now to explore the templates and get inspiration for your next game-changing workflow. Here’s to more time spent on what matters – we’ll take care of the rest.
Read one pager