Browser Guide

TouchPoint Software is a web-based product, which means you will use a browser to access it. A browser is a software application that lets you visit web pages on the Internet. Popular browsers include Google Chrome, Firefox, Safari, and Microsoft Edge. Currently, Google Chrome is the most widely used browser in the world, and is also considered one of the fastest and most secure. While each browser may give you a slightly different experience, all of the latest editions of these are compatible with TouchPoint.

Our mission is to make your experience within TouchPoint as smooth as possible. However, from time-to-time, you may come across some unexpected behavior. Many times this behavior occurs because of differences in the way each different browser is reading our code.

If you run into an issue like this, try the following steps to correct the problem.

  1. First, try to confirm that this is in fact a browser issue. To do this, open a browser that you don’t use often, and repeat the steps that led you to the error. If you don’t get an error, there is probably a problem with your usual browser. In this case, you need to update your browser. If you get the error in both browsers, it may point to an issue in TouchPoint. Let us know by following step 3 below.

  2. Second, if you find that you receive the error in one browser and not another, this could point to a caching issue. Cache (pronounced CASH) is a special type of temporary memory that helps your browser load websites faster. Sometimes, bad data can get stuck in the cache and cause the error. You may be able to resolve the issue by clearing your browser’s cache. For instructions on clearing your cache, we recommend that you consult http://www.refreshyourcache.com.

  3. Third, if updating your browser and clearing your cache do not resolve your problem, let us know! Click the ? (Help) icon in the top right corner of any TouchPoint page and select the Contact Support tab. If your church has designated Support Admins, only users with the Support role see the Contact Support form; other users see a list of their church’s Support Admins to contact instead. Be sure to include the steps you were taking when you ran into the error, the name of the browser that you are using, and, if possible, the version number. This information will allow us to test and reproduce the error, so our developers can correct it.

Tip

Not sure which browser you’re using or if it’s the latest edition? Go to https://www.whatismybrowser.com and the site will tell you which browser and version you are using. If your browser is out of date, it will provide a link to update it.

Session Time Out

How long is a Session?

When you are using TouchPoint, you are working within a session. Your session times out only when you are inactive for 600 minutes (10 hours). When you log back in, you return to the page you were on. Each time you continue working, the session timer resets.

Note

This does not apply to Check-In. Once you log in to Check-In, you will stay logged in until you log out. This is so you can set up your Check-In kiosks and they will continue to operate without you needing to log in each day.

Testing Online Registrations

An online registration page times out sooner than the normal session timeout. If you test a registration in one tab and leave it open without completing it, the registration times out and logs you out of TouchPoint - on every tab that is open to TouchPoint, in that browser. To avoid losing work, test registrations in a different browser than the one you are using to build the registration. This is why TouchPoint displays the following message when you select Try Registration from the Involvement’s gear menu.

../_images/Browser-TryRegistration.png

Try Registration message

Note

You will not see this message when you open the registration link from a Registration Form, but the timeout behavior is the same.



Latest Update

10/21/2026

Clarified Contact Support access for Support Admins, rewrote the registration timeout explanation, replaced the Try Registration screenshot, and removed an outdated browser-detection screenshot.