Blog

 

Getting started with Messaging: a guide for beta testers

Thank you for joining the Messaging beta. Messaging brings simple, secure chat to your church’s own Hubb app. You get one-to-one and group conversations for your teams, ministries and small groups, with no personal phone numbers and no separate apps to manage. Everything stays inside your church’s Hubb account, securely stored and auditable by your church administrators.

This guide covers what you need to start testing: getting the app on your phone, turning chat on for your groups, turning on Safe Messaging if you work with children and young people, and what we’d love your feedback on.

1478758

 


What we’ve already set up for you

We’ve switched Messaging on for your site, and we’ve created a Beta Test Chat group with your beta testers in it, so you can start chatting straight away. If you’d like other people added to the test group, just let us know, or add them yourself through the group’s member list in your admin area.

 


Step 1: Get the app on your phone

Messaging lives inside your church’s app, so each person testing will need it installed:

  • Visit yourchurchwebsite/app on your phone (for example, https://www.yourchurch.org.uk/app).
  • Follow the on-screen prompt to install it as an app on your home screen.
  • Allow notifications when the pop-up appears. This is important, because it’s how you’ll know when a new message arrives.
  • Log in, tap the chat icon, and you’re ready to go.

If you already have the app but didn’t allow notifications when you first installed it, log out and then log back in, and accept notifications when the prompt appears.

 


Step 2: Turn chat on for your groups

Chat is enabled group by group, so your church stays in control of exactly where conversations can happen. Any administrator who can see a group’s settings can switch it on:

  • Open the group in your admin area and go to Group Settings.
  • Open the Chat section in the settings menu.
  • Tick either or both options:
    • Allow group members to direct message each other, for one-to-one messages between people in the group.
    • Allow group members to chat in a group, for a shared conversation the whole group can see.
  • Save, and the group’s members can start chatting in the app.

You can enable chat for as many or as few groups as you like, and switch it off again at any time.

 


Step 3: Start chatting

Tap the chat icon in the app to see your conversations. From there you can:

  • Message one-to-one with anyone in a group where direct messaging is enabled.
  • Chat as a group in any group with group chat switched on.
  • Add emoji, see when your messages have been delivered and read, and pick up conversations across your devices.

Every message is stored securely within your church’s Hubb database. Nothing sits on personal accounts, and your church administrators can audit conversations if they ever need to.

Messaging-image-1 


Trying Safe Messaging in beta

Safe Messaging is now switched on for your site in beta, alongside Messaging. It gives the leaders you authorise a safe, accountable way to encourage children and young people through the week. Every message a leader sends goes to the child’s parent or guardian for approval first, and is delivered only once they approve it. Your church’s Safeguarding Lead can see the messages leaders send. Messages are one-to-one and text only, and a child is never contacted unless their parent has enabled it.

Safe Messaging isn’t switched on group by group like Chat. It applies across your whole site. Once it’s on, no one can message a child through Hubb, by chat or any other tool, unless you’ve given them Safe Messaging permission. The people you authorise can still only reach the children they’d normally message through their group access. So enabling Safe Messaging tightens who can contact children across your site, and every message those leaders send still needs a parent’s approval.

Before you start, get your family data ready. Safe Messaging only works where each child’s record is set up correctly: a date of birth entered, the child placed in the right family, and a contactable parent or guardian (with an email address) linked to them. A message can’t be sent to a child who doesn’t have a contactable guardian to approve it, so this is the foundation everything else rests on. If you haven’t done this yet, our guide walks you through it:

We’ve enabled the Safe Messaging beta on your site and given your nominated beta tester the Safe Messaging permission needed to send messages. The steps below are yours to complete.


Turning Safe Messaging on

  • Go to Site Settings, open General, and select Safe Messaging.
  • Choose your Safeguarding Lead from the dropdown. This is the person who’ll have oversight of the messages leaders send, so choose someone with a safeguarding role in your church.
  • Tick Enable Safe Messaging for this site.
  • Press Save.


Checking the settings

Before anyone starts messaging, look over each setting and read the information icon next to it. These control how Safe Messaging behaves for your church:

  • Approval expiry time: how long a parent has to approve a message before it expires. If they don’t approve it in time, it’s not delivered and the leader is notified.
  • Weekly message limit per child: the most messages a single child can receive in a week. This helps keep contact purposeful.
  • Allow children to reply: this is off by default, and you’ll probably want to leave it off to keep Safe Messaging one-way. If you’re considering turning on two-way messaging, talk it through with your Safeguarding Lead, check your governing body’s safeguarding policies, and put any extra safeguards needed in place first. It can be turned on for all children, or for children over 13 only.
  • Login age restriction: prevents account login for children under 13. By default, under-13s have no login of their own, and their parent shows the child their messages through the parent’s own account.


Sending a message and adding leaders

A leader writes a message to a child in Chat, just like any other conversation. Instead of going straight to the child, the message is held and the child’s parent or guardian is notified. They approve or reject it from a link in that notification. If they approve it, it’s delivered to the child. If they reject it or it expires, the leader is notified. Your Safeguarding Lead can see the messages leaders send.

To let another leader use Safe Messaging, give them the permission on the Site Administrators page.

 


What we’d love you to test

As a beta tester, your everyday use is exactly what we need. A few things to try and tell us about:

  • Notifications: do you reliably get a push notification when someone messages you? Does tapping it take you to the right conversation?
  • One-to-one and group chats: do both feel natural? Anything confusing about who you can and can’t message?
  • Everyday reliability: messages arriving promptly, read receipts behaving, the app picking up where you left off.
  • The admin side: was enabling chat on a group straightforward? Is anything missing from the settings?

If you’re testing Safe Messaging, we’d also love to know:

  • Setup: was turning it on and choosing your Safeguarding Lead clear? Did the settings and their notes make sense?
  • The approval flow: did the parent get the notification promptly? Was approving or rejecting straightforward? Did the right thing happen when a message was approved, rejected, or left to expire?
  • Oversight: can your Safeguarding Lead see what they need to?
  • Anything that gave you pause: wording, a step that felt awkward, or something you expected to do and couldn’t.

Nothing is too small to mention: a button that felt out of place, a notification that didn’t arrive, wording that made you pause. That’s the gold dust of a beta. And don’t worry about flagging something we might already know about. A duplicate is far better than a miss.

 


Also available now

Messaging is being actively developed, and your feedback shapes what we build. A few things you can already use:

  • Announcement-style groups: the option for only leaders to post in a group chat, or leaders and members together.
  • Chat with an end date: switch chat on for a group with an expiry date, useful for an event team or a term-time course.
  • A streamlined chat list: small refinements that make your conversations easier to scan.

Safe Messaging is in beta now too (see above), and Broadcasts, for push notifications to your whole church, is also available.

 


Send us your feedback

Found a bug, hit a snag, or have an idea? Email us at hello@hubb.church with “Messaging beta” in the subject line. Screenshots are always welcome. Thank you for helping us make Messaging brilliant for every church.