Contact Church

Members have somewhere to write.
The church has somewhere to answer.

People with a question do not always know who to ask

People with questions about the church end up messaging whoever they have a contact for. The leader, the pastor, or whoever answered last time.

The request becomes a private message on somebody's phone. If that person travels, falls ill, or steps down from the role, the request leaves with them.

Contact Church is the church's own support channel inside the app: people choose a subject, write, and follow the answer in the same place where they already see their cell group and the church announcements. The request lands in a queue that belongs to the church, not on somebody's phone.

On the church side, one queue instead of twenty scattered threads

Whoever is on duty opens the list, enters the conversation, replies, and closes it once the matter is settled. The history stays with the contact, so whoever replies tomorrow reads what was already said, even when someone else handled it before.

  • ✓ Every contact arrives with a subject and an author, before anyone opens it.
  • ✓ The conversation goes back and forth as many times as it needs to, until someone from the church closes it.
  • ✓ In churches with more than one campus, each campus manager sees only the contacts from their own.

Messaging is the church speaking to a group of people. Contact Church is the other way round: a person speaking to the church.

Frequently asked questions

That is not the idea. What changes is where the request lands: instead of reaching the personal number of whoever happened to be nearby, it reaches the church, with a subject, an author, and a history. WhatsApp still serves everyday conversation.

It does. Subjects live in the church's settings, and a new account starts with a ready-made list:

  • I want to join a cell
  • Events
  • Courses
  • Appointments
  • Thanks
  • Complaints
  • Finance
  • Social assistance
  • Other

You can rename them, turn off what the church would rather not receive, and create the ones that are missing, and changing the list later does not touch the contacts that already exist.

They can, by creating the subject. It is not in the default list because a prayer request is not a support ticket like the others: whoever writes is not waiting for the church office to get back to them, they are asking for intercession. A church that wants to receive them here creates the subject, and it starts showing up for whoever writes.

Administrators see every contact. A campus manager sees only the ones from their own campus. In a church with several campuses, a member's request stays with the people who care for them, without having to be forwarded by the head office.

They do. A new contact raises a notification in the app for whoever answers, plus email and push for anyone who has turned it on. Nobody has to remember to open the list to find out that someone is waiting.

They do. The reply raises a notification in the app, plus email and push for anyone who has turned it on. The notice says there is an answer and carries the link, without carrying the conversation with it. What was said stays where it belongs.

No, and that is deliberate. A contact reopened months later turns into a conversation with no beginning and no end. When the matter comes back, the person opens a new contact, and the earlier one stays in their history and in the church's.