How Tealeaf Academy increased student engagement 3x

Written by Mailgun Community

Categories: Customer Success

5 minute read time

This post is written by Kevin Wang, Chief Instructor at Tealeaf Academy (Launch School). Tealeaf Academy is an online school for developers, and offers intensive, project based online bootcamps on web development. If you think this post is useful, you should check them out!

At Tealeaf Academy, creating a “Study Together, Progress Together” experience for our students is at core of our way of teaching. One of our core tools is the discussion board where students ask questions, share ideas, collaborate on homework assignments, and teachers quickly jump in to help students get unstuck on problems. One of our recent priorities was to reduce friction in discussion board usage and encourage more discussions with a complementary email notification and a “reply-to email to post on discussion board” workflow. Once we implemented the below code using the Mailgun Routes API, activity on our discussion board increased three fold, and questions are now typically getting answered within an hour, sometimes even minutes, and students are able to move on the next set of tasks a lot quicker. Here’s how we did it:

Our workflow would go as the following:

  1. When a post (most likely, a question) is created, all course participants are notified by email notification
  2. Course participants can reply to the email notifications directly from their email inbox, without having to sign into the course
  3. That reply will be posted on the online discussion board, and are also sent to other course participants, to keep the conversation going.

Why we choose Mailgun

The key piece of this workflow is to receive and parse inbound email messages. We looked around for several email service providers, and in the end picked Mailgun because:

  1. It is very developer friendly – We are developers, and Mailgun speaks to us. The APIs expose a lot of low level options that allows tweaking. We like the Routes in particular – It’s a nice layer of abstraction that makes integration with apps very easy. (see how we use it below)
  2. It is the most feature complete service we have found – we can use Mailgun for transactional emails, campaigns as well as email lists – it’s nice to have just one service provider to handle everything we need.
  3. The price is reasonable and the upgrading path to dedicated IP and custom DKIM is nice, even we do not need it yet.
  4. The support is top notch. There is a live chat that I can talk to their developers directly on issues and it has been very useful for us to get issues resolved.

Setting up the email infrastructure

  • The first step was to create a new domain on Mailgun. In our case, it’s which we use for sending and receiving emails.
  • Next, we created a MailgunGateway as our wrapper for Mailgun’s API. This wrapper takes care of all our interactions with Mailgun through our account. Here we use Mailgun’s send_batch_messages API to send HTML emails. It allows us to send a message to multiple receivers with a single API call. We keep our API key as environment variables on the server for extra security. There is also a simple delivery filter such that no emails are sent in the development environment; On staging, all emails are sent to Chris (my co-founder) and myself, so we can test out things without fearing to spam our users; Only on the production environment emails are sent to real users.
class MailgunGateway  
  def send_batch_message(options={}),
        from: default_sender,
        to: delivery_filter(options[:to]),
        subject: options[:subject],
        html: options[:body],
        :"h:Reply-To" => options[:reply_to],
        :"recipient-variables" => options[:recipient_variables]
        ) if Rails.env.staging? || Rails.env.production?


  def default_sender
    "Tealeaf Academy "

  def api_key
    @api_key ||= ENV['mailgun_api_key']

  def messaging_api_end_point
    @messaging_api_end_piont ||= 

  def delivery_filter(emails)
    Rails.env.production? ? emails : ","

Send email notifications for new post or comment

Once a post or comment is created, we send an email notification to all course participants. We are sending emails synchronously for now, but as we have more users, we’ll probably want to offload this to a background job.

class Courses::PostsController < AuthenticatedController  
  expose(:posts) { course.posts }

  def create
    post.user = current_user
    redirect_to course_home_path(course)


class Courses::Posts::CommentsController < AuthenticatedController  
  expose(:posts) { course.posts }
  expose(:comments) { post.comments }

  def create
    comment.user = current_user
    redirect_to course_home_path(course)


The CourseNotifier is the class where we put our application specific logic on notifications. Note that MailgunGateway is injected in as the default gateway – this is from when we used to have multiple email service providers for campaigning, lists and transactional emails. It is less of a need now that we consolidated all email delivery needs to Mailgun!

class CourseNotifier

  attr_reader :course, :gateway

  def initialize(course,
    @course = course
    @gateway = gateway

  def notify_course_participants_on_new_discussion(discussion)
      to: notification_recipients(discussion).map(&:email).join(", "),
      subject: notification_subject(discussion),
      body: discussion_notification_text(discussion),
      reply_to: reply_to_address(discussion),
      recipient_variables: recipient_variables(



  def notification_recipients(discussion)
    course.participants.reject {|participant| == }

  def notification_subject(discussion)
    discussion.is_a?(Post) ?
    "[Tealeaf Academy] #{} Posted a New Message on the Discussion Board" :
    "[Tealeaf Academy] #{} Replied to a Message on the Discussion Board"

  def reply_to_address(discussion)

  def recipient_variables(recipients)
    vars = do |recipient|
      ""#{}": {"name":"#{}"}"
    "{#{vars.join(', ')}}"

  def discussion_notification_text(discussion)


<p>#{} says on the course dicussion board:</p>

<p>Reply to this email directly or <a href="{course.slug}/home">view it on the discussion board</a></p>

The replytoaddress is where we insert the post token into the “Reply-To” header. The content of the emails are quite simple so we just put them here in the class. If we had a more elaborate email style, we would have used template rendering to handle it. With Mailgun’s sendbatchmessage API, we can call the API just once to send to multiple recipients, and the recipient_variables method is where we customize email messages for each receiver to include their names to add a personal touch.

Handling inbounding messages in the application

Heading over to Mailgun, under “Routes” in the Control Panel, we created a route as the following:

  • Filter Expression: match_recipient(“reply+(.*)”)
  • Action: forward(“”)

When a user replies to an email, they reply it to an email address such as “”, and this route will forward the email to a web hook that we expose to handle incoming messages.

class Api::IncomingMessagesController < ApplicationController  
  skip_before_filter :verify_authenticity_token

  def create
    user = User.where(email: params['sender']).first
    post = Post.where(token: params['post_token']).first
    text = params["stripped-text"]
    if post && user && text.present?
      comment = post.comments.create(user: user, text: text)

Here, we use the sender’s email to find the author, and use the post token to find the post that this reply should be collated under. Mailgun gives us the very useful stripped text which strips away the original message part to only contain the actual reply! In the end, we return a 200 header to tell Mailgun that this interaction is successful, otherwise Mailgun will think our server is down and will faithfully keep trying to call our webhook.

The result from implementing this workflow is impressive – activity on our discussion board increased three fold, and questions are now typically getting answered within an hour, sometimes even minutes, students are able to move on the next set of tasks a lot quicker and we are very happy how this turned out.

Modified on: March 13, 2019

Stay up-to-date with our blog & new email resources

We'll let you know when we add new email resources and blog posts. We promise not to spam you.