Journey templates

At times you may find that you are creating similar journeys with similar components over and over again. At Intempt, you can save time by creating and using pre-formatted templates to interact with your customers. You can even share these templates with your team. Additionally, if you are lacking inspiration, you can use the Publicly available templates.

Accessing the templates

The templates can be accessed from the Journey builder object. There you will locate either Project or Public templates tabs.


730

Additionally, when creating a new journey, you will also be presented with available templates to use.


1904

Both the Project and Public templates are classified with the following categories:

  • Connector - journey actions are based on third-party connectors that send Emails, SMS, and create tickets.
  • Industry - either Retail & eCommerce or SaaS.
  • Lifecycle stage - Acquire, Convert or Retain. Whether your journey is trying to Acquire a customer, Convert the customer to a different stage, or Retain.


Project templates

The Project templates are templates that are available to Project members, who are signed up to Intempt. For example, if another user is from the same Project and has the access rights to access Journeys, one will be able to use the template for a journey.


1570

Public templates

The Public templates are templates that are available not only to the current Project members but also to members of different Projects and Organizations.


1578

Previewing the templates

To preview a template, simply click on it. From the Preview you can access the journey image itself, the components it consists of, the author, connectors, and description.


1286

Using the templates

To start using the template, either from the Preview or from the templates list select the Use template option. The journey will be created automatically and placed on the journey canvas. From there, you can edit and configure the journey in any way you desire.


526

Publishing journey as a template

In order to create a journey template, you need to click either on the Share button or Publish as a template from the journey canvas.


436

Afterward, you will be presented with a window where you need to configure the journey template information, such as:

  • Template cover. You can either generate or upload a cover photo. By generating, Intempt will place a snapshot of the journey.
  • Decide, whether you want to make the template Public or Private.
  • Name of the journey template
  • Industry
  • Lifecycle stage
  • Short description of the template
  • Explanation of what the journey template tries to achieve, what are the components, goals

1102

Also, when publishing a journey template, you can also send invitations to Project members to either View or Edit the template.


980

Sharing the templates

There are 4 ways of sharing the Journey templates:

  • Invitation - inviting already registered Intempt users to access the journey
  • URL - send a URL link to registered users and users outside the project or even outside Intempt to access the journey
  • Send to Email - send an email with an image of the journey
  • Send to Slack - send an image of the journey to a Slack channel


Invitation

In order to provide access rights to the users who are signed up in Intempt, simply start inputting the name or email of that user. Additionally, you can specify the provided access right for the Journey:

  • Can view
  • Can edit

988

Once the person has been invited, one will be visible in the list of people having access to the journey. From there, you can also update the access right or remove that person from accessing the journey.



URL

To share a journey with a link, users need to click on the “Copy link” button. The URL for the journey will be copied.



Anyone with the link

The “Anyone with the link” option will result in accessing the journey for each user having the URL link. Moreover, users sharing the link need also specify the access rights:

  • Can view
  • Can edit

NOTE: Users who are outside the Project and Intempt can access the Jounrye. If they are registered users, they can also request access to edit. Otherwise, they will only be able to view the object.


980

Anyone with the link and password

The “Anyone with the link and password” option will result in accessing the journey only if the user with whom the URL has been shared has been provided a password → the journey becomes password protected. Moreover, users who are providing the sharable link also need to specify the access rights:

  • Can view
  • Can edit

NOTE: The password is specified when the “Anyone with the link and password” option has been selected.


1436

Only people invited to this file

The “Only people invited to this file” option will result in accessing the journey only for users who have been given access to the journey. Trying to access the journey by users who are not invited or not signed up for Intempt will result in a screen where users will need to sign up for Intempt. Moreover, users sharing the link also need to specify the access rights:

  • Can view
  • Can edit

NOTE: Only users who have been given access to the object can access the object via the shared link → Private, meaning that the object can only be accessed by signed-up users.


1442

Send to Email

The “Send to Email” option will allow sending snapshots of the journeys to the specified email. Users need to provide the following:

  • Email(s)
  • File format
  • Subject of the Email (optional)
  • Personal note - message (optional)
  • Include a shareable link - a link to the object will also be provided in the Email. The configuration for the link is based on the previous section

980

Send to Slack

The “Send to Slack” option will allow sending snapshots of the journeys to the specified Slack channels. Users need to provide the following:

  • Slack channels
  • File format
  • Subject of the Email (optional)
  • Personal note - message (optional)
  • Include a shareable link - a link to the object will also be provided in the Slack notification. The configuration for the link is based on the previous section

982