Can you find a way to make these ONE unified product. That would be nice!

In order for us to fully take advantage of Messaging, we need to have the ability for other staff members to access messaging without access to the other pieces of the Tithely suite.

If a person plans a visit, I'd like for the person to be added to a Planned Their Visit list and have Messages handle the comms rather than Sites PYV feature.

This works fine in Sites and in ChMS, so I'm not sure why Tithely thinks its problematic for Messaging. But I think messages would be more widely read if they come from our church domain.

The ability to add code to any website that includes a Messaging widget/popup.

Can you add message variables so we can quickly insert these into a message. ie: "first name", "email", "custom field 1", etc.

It would be great to have the ability for someone to "sign up" or "subscribe" to the email messaging and be auto added to the "people" (like signing up for an email list) - similar to how it works with the text portion of messaging (as I understand it)

I understand that a Messaging subscription is currently only $5/month. However, a 200 SMS messages limit per month is pretty limiting. A small church could potentially manage within that constraint, but medium to large-sized congregations would hit the limit in one or two blasts. Either increasing the limit or offering additional tiered plans with higher limits would make Messaging more viable to use. Currently, 200 messages a month is hard to recommend for others to use when alternatives like Clearstream exist.

We are excited to try out the texting side of the messaging. I think it could be helpful to receive an email alert when a text is sent to us. That way we are more quickly notified when someone has communicated with us and it is less likely to be missed.