Testing the widget before going live.

A 5-minute pre-launch checklist so you're not debugging in front of real customers.

The 5-minute pre-launch checklist

Before you tell anyone the widget is live, run through this. It catches the common "why isn't this working" issues.

1. Open your site in incognito

Don't test in the same browser tab where you set everything up. Open a private or incognito window. Visit your site as a regular customer would. The widget should appear in the bottom-right within a few seconds.

2. Send a test message from desktop

Tap the widget. Fill in name, mobile (use your own personal mobile), message. Submit.

You should:

  • See a "Got it" confirmation in the widget
  • Receive an SMS on the mobile you entered, from your TapText AU number
  • See the conversation appear in your TapText inbox

3. Reply from your phone

On your business phone, reply to the SMS as you normally would. The reply should appear back in the widget conversation thread (if the customer's still on the page) and in the TapText inbox.

4. Test outside business hours

Temporarily change your business hours so it's "after hours" right now. Send another test. Confirm the after-hours auto-reply fires (not the inside-hours one).

Don't forget to put your hours back when you're done.

5. Test on mobile

Open your site on your phone. The widget should be in the same position, sized for thumbs, and easy to fill out without zooming.

Note. If the widget is overlapping a "Call Now" sticky bar or other floating button on mobile, change its position in Settings, Appearance.

6. Test on the slowest browser you've got

Edge or Safari on an old laptop. Just confirm it loads. We support modern browsers, but a stress test is free.

7. Send a friend

The most useful test: text a mate the URL of your site. Have them try the widget and tell you what felt off. Customers won't email you about a clunky form, they'll just close it.

What's NOT a real test

Testing on the same Wi-Fi you set everything up on, on the same phone you signed up with. You're too close. Use a different network and a different person if you can.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us