Skip to main content
Starting a new Touchpoint

See the initial stages of beginning a Touchpoint

Laura Montgomery-Hurrell avatar
Written by Laura Montgomery-Hurrell
Updated over 8 months ago

Jump to:


You can create a new touchpoint on any existing Workflow in:

  • Mobile Event Capture, Prospectus Requests, 

  • Applications, 

  • Rapid Response, 

  • Event Manager, 

  • Pre-applicant Open Days,

  • Applicant Open Days

You can create an unlimited number of touchpoints on each workflow. If you have a super busy workflow you may want to pause before creating your new touchpoint. This article explains how to pause a workflow.

Adding a new Touchpoint

Click the Plus icon to add a Touchpoint, the Pencil to edit an existing Touchpoint, or the duplicate icon to clone a Touchpoint.

The Touchpoint is always set to draft on its creation. Once you are satisfied with the Touchpoint, you can amend the status at the top of the page to Live. 

While this can be done at any point, you will no longer be able to edit the Touchpoint once it is Live. You can bounce between the steps at any point of the editing process - just remember to save your work!

Step 1: About

Use this step to set the details of the Touchpoint, such as name, description and action.

Available actions:

Email Touchpoints are the most common form of communication due to the low cost of sending them and the ubiquitous nature of email. This makes them the best way of regularly communicating with students.

SMS Touchpoints are very useful for easily communicating a short message. Each SMS Message credit is for a message which is 160 characters long, but you can link several together within the text to form a longer message.

Please note: Sending SMS uses up your SMS Balance. Using emoji in your SMS can use up more characters than expected.

SMS Touchpoints are great for quick updates when you think students are not likely to be near a computer to pick up an email. This makes them great for use with the Applicant or Pre-App Open Days apps.

Letter Touchpoints are a more traditional way of communicating with students. The CRM will generate a PDF, which contains the content of the Touchpoint. The PDF can then be printed onto plain or headed paper and posted to the student. Posted communications can be very effective, but are more time-consuming to manage and cost a lot more to send than email or SMS messages.

Label Touchpoints are a useful way of sending information to students. For instance, if you send a couple of brochures in a poly-bag, you can stick labels generated by the CRM to the bags and post them. This will print the student’s title, first and last names, and their full address. This cannot be changed.

Cloning and Archiving

Sometimes you may want to clone a particularly effective Touchpoint, or create a backup in case you want to revert changes later. Lean more about cloning Touchpoints here.

Equally, you may have some Touchpoints that are not appropriate any more and want to file them out of sight. Learn more about archiving Touchpoints here

FAQs

Q. I built my whole email in Template Builder and now get the error message "Content text in content cannot be empty". Why?

A. This is because templates are designed to be "envelopes" around the touchpoint content, and the platform thinks you have not entered any content.

A workaround is to use the "Replace with content" merge tag on the last full stop of your template, and place that full stop in the touchpoint. This counts as content, and your touchpoint can now be set live.

Did this answer your question?