# By: Riasat Ullah # This file contains informational content that will be sent to users after registering (by email). from utils import url_paths def get_disclaimer(): content = '''

This message was produced and distributed by TaskCall. TaskCall is a service owned and provided by TaskCall Inc. To help keep your account secure, please do not forward this email.

''' return content def get_onboarding_disclaimer(recipient_id): ''' Gets the disclaimer that goes in the footer of onboarding emails. :param recipient_id: unique ID that identifies the email recipient :return: (string) html for the disclaimer ''' unsubscribe_url = url_paths.web_email_subscription_cancel + '?type=onboarding&id=' + recipient_id content = '''

This message was produced and distributed by TaskCall. TaskCall is a service owned and provided by TaskCall Inc. This email is part of a series of onboarding emails to help introduce you to TaskCall. They continue for a few weeks after you register your account. If you do not want to receive them anymore you can unsubscribe.

If you have any questions please contact us at: support@taskcallapp.com

'''.format(unsubscribe_url) return content def get_social_media_links(): ''' Gets the social media buttons that are sent in emails. :return: (string) html for the social media buttons ''' content = ''' LinkedIn Icon Twitter Icon Twitter Icon ''' return content def get_onboarding_footer_content(recipient_id): ''' Get the html content for the footer of onboarding emails that have both the social media links and disclaimer in the same div. :param recipient_id: unique ID that identifies the email recipient :return: (str) html content ''' content = '''
{0}
{1} '''.format(get_social_media_links(), get_onboarding_disclaimer(recipient_id)) return content def invoice_email_content(mth_year_txt, organization_name, invoice_number): ''' Content for invoice emails. :param mth_year_txt: month and year as text e.g. November 2022 :param organization_name: name of the organization :param invoice_number: the invoice number :return: (tuple) -> subject, email body ''' subject = 'TaskCall - Invoice is available for {0}'.format(mth_year_txt) content = '''

Your TaskCall monthly invoice is available. Please find the PDF document attached at the bottom of this email.

The balance will be automatically charged so you don’t need to take any action.

Name: {0}

Invoice number: {1}

If you want to view your payment history visit your account by following the instructions below:

  1. Log into your TaskCall Account
  2. Go to Configurations > Organization.
  3. Scroll down to the Billings section.

{3} '''.format(organization_name, invoice_number, url_paths.web_login, get_disclaimer()) return subject, content def welcome_on_board_content(): ''' Content of the email that will be sent out when a new account is created. :return: (tuple) -> email subject, email body ''' subject = 'Welcome to TaskCall' content = '''
Welcome Onboard

Start Automating
your Incident Response Today

Watch Tutorials

Here are some quick tips to get you started.

Download the mobile app: iOS, Android
Create an On-Call Routine
Create an Escalation Policy and add the routine to it
Create a Service and add the escalation policy to it
Create your first Incident
Quick Start Guide
{0}
'''.format(get_disclaimer()) return subject, content def configurations_that_must_be_set_up(recipient_id): ''' Onboarding email 1. Introduces routines, escalation policies and support hours. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: 3 Things You Must Set Up' content = ''' Set up a rotational on-call routine and add it to an escalation policy. TaskCall will automatically escalate to the secondary if the primary on-call fails to respond.

Routines, Escalation Policies and Services

1. Routines: Map out your 24 hours

Routines have layers. Each layer is like a shift (e.g. 06:00 AM to 10:00 AM). Set them up to cover your 24 hours.

Add people to the same layer to rotate responsibilities periodically.

Check templates

2. Escalation Policies: Auto-escalate to backup

Add your team routine to an escalation policy. Make sure you have at least 2 levels of support. That way no incidents will ever be missed.

Learn more

3. Services - Your system components

3.1. Define how service incidents will be handled:

  • Escalation policy to assign incidents to
  • Enable alert suppression
  • Support hours to avoid interruption when you are not working
Learn more

3.2. Integrate:

Set up an email integration or pipe alerts from your monitoring tools to the service. Connect your chat-ops.

Learn more

3.3. Dependencies:

Automatically identify impact on other parts of your system resulting from an incident on a service.

Watch tutorial

Always add your routines to escalation policies.
Incidents are created on the policies, not routines.



Watch Demo Video
{0}
{1}
'''.format(get_social_media_links(), get_onboarding_disclaimer(recipient_id)) return subject, content def live_call_routing_content(recipient_id): ''' Onboarding email 1 (if customer wants live call routing). Introduces live call routing. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: How to set up Live Call Routing?' content = ''' With live call routing provide customer call support from wherever you are. Never miss what matters.

How to set up Live Call Routing?

Note: Although a payment card is required to access live call routing, no fees will be charged during the trial after your organization is verified.

1. Create a routine: Map out your 24 hours

Routines have layers. Each layer is like a shift (e.g. 06:00 AM to 10:00 AM). Set them up to cover your 24 hours.

Add people to the same layer to rotate responsibilities periodically.

Check templates

2. Create escalation policy

Add your team routine to an escalation policy.

Have at least 2 levels of support so calls can be forwarded to the secondary if the primary does not respond.

Learn more

3. Create your services: For IVR options

Assign the escalation policy incoming calls should be assigned to.

Set support hours to send callers to voicemail in off-hours.

Learn more

4. Select a phone number

Go to Configurations > Live Call Routing and select a phone number of your choosing. Calls coming in to this number will be routed to your on-call team members.

5. Configure greeting and IVR options

Use a text-to-speech greeting or provide your own audio. Set up IVR options with the services you created.

6. Voice message and call recording

Let callers leave a voice message when you are unavailable. You can also record the call itself for training purposes.

7. Instant call analytics

Analyze how effectively your team handles calls. Get a real time view of your costs.

{0}
'''.format(get_onboarding_footer_content(recipient_id)) return subject, content def incident_handling_content(recipient_id): ''' Onboarding email 2. Asks users to download the mobile app. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: How to handle incidents?' content = ''' Acknowledge. Review details and snapshots. Check system wide impact. Run diagnostics tests on your server. Add responders. Keep stakeholders updated. Resolve when you are done.

How to handle incidents?

Get it on App Store Get it on Google Play

Basic Incident Flow

Get notified by push notifications, SMS, voice calls and chat-ops.
Acknowledge so everyone knows you are working on the incident.
Review incident details and snapshots to understand the problem.
Reassign or add responders if you are stuck.
Escalate to your backup support if you cannot respond.
Resolve when you are done.

Run Diagnostics

Without having to manually go through your system part by part, quickly run a diagnostic test from the tip of your fingers with our Rundeck integration.

Learn more

Custom Actions

Execute actions on your own servers securely with TaskCall. For example, restarting a server or changing the limit of a parameter.

Learn more

Run Multiple Actions Together

Using response sets run several actions at the same time with a click of a button. Automate the process of assembling your team and notifying stakeholders, so you can spend more time on resolving incidents instead.

Learn more

Search Faster with Tags

Find the right point of support faster by filtering with tags.

Learn more
{0}
'''.format(get_onboarding_footer_content(recipient_id)) return subject, content def auto_identify_system_impact_content(recipient_id): ''' Onboarding email 3. Talks about identifying system impact, past incidents and similar ongoing incidents. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: Automatically identify system impact and similarities' content = ''' TaskCall automatically identifies impact across your system from an incident so you can visualize the impact and find the root cause faster.

Find impact on dependencies and learn from similar incidents

Visualize Impact

TaskCall automatically evaluates and identifies the impact of an incident on all connected parts of your system. The list of impacted technical and business services are shown on the incident details page. Visualize how it spreads to other components from the dependency graph.

Wacth Video Tutorial

Learn from Past Incidents

TaskCall automatically analyzes data to find similarities across incidents and present them to you so you can see what was done in the past to resolve the issue.

Learn More

Know about Similar On-going Incidents

TaskCall will automatically identify and ensure you know when there are other similar incidents going on at the same time. This will help you take a more wholesome approach to the solution and cooperate with other teams.

Learn More
{0}
'''.format(get_onboarding_footer_content(recipient_id)) return subject, content def conditional_routing_content(recipient_id): ''' Onboarding email 4. Introduces conditional routing and AI alert grouping. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: Content Based Incident Delegation' content = ''' Handle monitor alerts based on the content. Dictate how alerts should be handled if certain conditions are met.

Conditional Routing

Handle monitor alerts based on the content. Dictate how alerts should be handled if certain conditions are met.

Content based delegation

Delegate incidents to different responders based on the source or the presence of certain values in the body of the alert.

Watch Demo
Suppress alerts

Suppress unnecessary alerts with “Conditional Routing” or configure “Services” to use AI and automatically group similar alerts into one incident. Take care of the extra noise so your responders can focus on what matters.

Watch Demo
Extract additional details from alert

Insightful information might be available in certain fields of alerts that TaskCall does not inherently process. Extract them and update the title or description of the incident to help responders understand the problem faster.

Watch Demo

Not every alert matters.
Contextualize them with TaskCall so you can focus on what matters the most.



Learn More
{0}
{1}
'''.format(get_social_media_links(), get_onboarding_disclaimer(recipient_id)) return subject, content def analytics_content(recipient_id): ''' Onboarding email 5. Introduces analytics. :param recipient_id: unique ID that identifies the email recipient :return: (tuple) -> email subject, email body ''' subject = 'Onboarding: Are you efficient?' content = ''' Analyze how effective your incident response is and understand if your teams are overworked.

Analytics for growth

Analyze how effective your incident response is and
understand if your teams are overworked

Incidents

Understand how often incidents occur and how fast you respond to them.

Impact

Understand which parts of your system are impacted the most and how much it is costing you financially. Evaluate how you should allocate resources.

Team stress level

Understand whether your team is overworked or not. Know they are most effective. Learn about their work habits. See how they compare with other teams.

Make business decisions based on data.



Learn More
{0}
{1}
'''.format(get_social_media_links(), get_onboarding_disclaimer(recipient_id)) return subject, content