Creating a ticket number experience in Front

If you're transitioning from a traditional help desk solution to Front, your customers may be accustomed to using Ticket IDs as references. In this article, we'll review how you can create similar experiences for your customers using Front's Conversation ID.

Here's a link to a Loom video walkthrough.


Teammates can hold down and type ShiftO to open Front's conversation search box, where they can easily drop any Conversation ID to navigate to it quickly.


With this option, you will create a rule to send an automatic reply whenever a new conversation is created. The automatic reply will include Front's Conversation ID, which is similar in concept to the Ticket # offered through traditional help desk solutions.

Step 1

Navigate to your Setting > Responses (under the Company section) > Add a canned response.

Step 2

Write your auto-response message and use Front's dynamic variable to include the Conversation ID. You can include the Conversation ID in both the body and the subject line of the message. Note: The subject line in the canned response will replace the original email subject line.

To use the dynamic variable just type {{ and select {{conversation.public_id}}. Here's an example of an auto-reply. 


With this option, you can update your signature to include a short sentence referencing the Conversation ID.

Step 1

Navigate to your Settings > My Signature (or Signatures under the company if you want to create a team signature) > Select your signature.

Step 2

Update your signature to include the Conversation. To use the dynamic variable just type {{ and select {{conversation.public_id}}. Here's an example of a signature:

This is how it will show up in your composer:


With this option, you will leverage Front's API to create a ticket number experience for your users by creating a team rule to send all new inbound messages to a webhook, or external endpoint to be processed. This webhook will be created by your development team or Zapier, depending on the direction you go down. We'll also want to ensure the rule only applies to every conversation once when the first message is received.  I will be using Zapier to demonstrate how you can accomplish this.

Step 1

Create a webhook in Zapier: Create a new Zap > select Webhooks from Zapier and set the Trigger Event to Catch Hook. Copy the produced custom webhook URL. 

 Step 2

Create a tag that we can use to identify conversations that have received a Conversation ID. You can create a tag by going to your Settings > Tag > Create new tag. I've created a sample tag called "Convo ID".

Step 3

Create a team rule by going to your Settings > Rules > Create a new rule. You'll want to update the WHEN to just include Inbound message. In the IF section, this is where you should select the inboxes you want to apply the ticket experience to, as well as add a condition that states the conversation does not have tag "Convo ID" or whatever tag name you created in Step 2. In the THEN section, you'll want to select Send to webhook and paste the webhook URL you copied from Step 1, and include a step to add the "Convo ID" tag to the conversation, ensuring this rule won't apply to this conversation again.

I've included a rule for you to reference below. 

Step 4 

At this point we should test this rule works; this will give us confidence we are catching the correct types of messages, and will give us some sample data to work with in Zapier.

To do this, create a message which will trigger your rule. In the example above, we will send a new email to our "Andersen @ Cloud" inbox.

Step 5

Back in Zapier, hit "Test Trigger" in the Webhook step setup, and you should see the data you received from your Front rule appear: 

 Step 6

Now we have some sample data to work with in Zapier, we can create our Zap action. This step will use Front's API to append the Conversation ID to the existing subject line and send an auto-response back to the recipient.

Again, choose Webhooks by Zapier and select the Custom Request action event. You'll want to set the method to POST and the URL to https://api2.frontapp.com/conversations/{{conversation_ID}}/messages. Make sure the {{conversation_ID}} is set up as a dynamic variable, pulling from the initial Catch hook step of the Zap. Click the URL field to select the dynamic variable you want to pull into your URL.

Set the Payload Type field to "JSON".

Next, you'll want to update the Data and Headers fields with the appropriate data.

We will start by setting the sender name, subject and message body;

To add any additional data to your auto-response, please reference Front's message API endpoint for a list of possible options.

Finally, we need to create your Authorization token to authenticate the requests being made to Front. Follow the instructions in our How to create API tokens guide to create a new API token. Then, take your new token, and create a new Authorization header in your Zap:

 Once you've created these two steps, save and enable your Zap and send a message to your inbox to test the ticket workflow you've created. You should experience the sender receiving an auto-response, with a ticket ID in the subject and auto-responder message body. 

If you have any questions, we are always available to help at support@frontapp.com.

2replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Hi Andersen, thank you for this. Implemented it in our Front and works great.  However do you have recommendations for closing a ticket? I tried to create a rule saying IF 'conversation archived' THEN 'Reply With' 'Once' 'Closed Ticket canned response'.  Only problem is Front is emailing itself the closed ticket canned response, and not the initial sender who logged the ticket. Great if you had any way to achieve this. Thank you

    Like
  • Steve Shackley Hi Steve, thanks for getting in touch! Please email us at support@frontapp.com and we're happy to assist with specific workflow questions.

    Like
Like1 Follow
  • 1 Likes
  • 12 days agoLast active
  • 2Replies
  • 206Views
  • 3 Following