How do we avoid over-messaging supporters?

A per-contact frequency cap applies over a rolling window across every campaign and sequence, and quiet hours are applied in the recipient's own timezone.

Can we prove someone consented?

Consent is stored as a permanent record with the exact wording shown, the source, and when. It is scoped by purpose, so a transactional basis does not authorise an appeal.

Can we message volunteers for a specific shift?

Yes, if the shift is recorded as a tag or field. Segments target exactly that group.

What does WhatsApp cost us per message?

Meta prices delivered template messages by category and destination country, charged to your own WhatsApp account. Otobiz shows an estimate before a send and adds no margin.

Can beneficiaries reach us privately?

Yes, and access to those conversations can be restricted per staff member, with personal details masked for people who do not need them.

Is there a free tier for nonprofits?

Pricing is a conversation, and the shape of your programme matters more than a tier. Talk to us and we will be straight about what fits.

Can we see how an appeal actually performed?

Each send reports per recipient, and responders and clickers can be saved as a segment so the follow-up goes to people who engaged.

Can supporters ask for fewer messages without opting out?

Consent is scoped by purpose, so someone can keep receiving transactional messages while opting out of appeals. Frequency caps also limit contact without anyone having to ask.

Reach supporters without wearing them out.

Donor and volunteer contact lives or dies on trust. Frequency caps and provable consent are what keep people giving.

Nonprofits and charities use business messaging to reach donors, coordinate volunteers, and support beneficiaries. The constraint that shapes everything is trust: a supporter who feels over-messaged does not unsubscribe quietly, they stop giving, so consent handling and frequency control matter more here than send volume.

What usually goes wrong.

Appeals go to everyone, every time: Without segmentation, the monthly giver, the one-off donor, and the volunteer all get the same appeal, and the ones who give most hear from you most.
Volunteer coordination lives in group chats: Shift coordination in an unmanaged group chat has no record, no assignment, and no way to reach only the people who signed up.
Consent that was never written down: Records of who agreed to what, and what wording they were shown, are usually missing entirely, which is a problem the day someone asks.

What Otobiz does about it.

Consent recorded with the wording shown

Consent is recorded per purpose, permanently, with the exact wording the supporter saw, where it came from, and when. Suppression applies everywhere at once.

Separate transactional and marketing consent
The disclosure wording stored with the consent event
Opt-out keywords handled automatically with a confirmation

Segments so appeals land where they belong

Donors, volunteers, and beneficiaries are separate audiences with separate needs, defined by tags, stage, stored fields, and engagement.

Segments from tags, stage, custom fields, and recency
Per-contact frequency caps across every campaign
Quiet hours in the recipient's own timezone

Volunteer coordination with a record

Shift messages go to the people who signed up, with assignment, internal notes, and a record of what was sent and by whom.

Segments for a specific shift or programme
Assignment and internal notes on the thread
Every send logged with who approved it

A person on anything that matters

Campaigns, scheduled sends, and anything that writes to another system queue for approval. The approval is bound to the exact message you approved and re-checked at send time, so what the approver saw is what goes out.

Approve, edit, or reject before anything leaves
The message you approved is the message that sends
Every send logged with who approved it

Appeals you can report on

Every send reports per recipient, and responders and clickers can be saved back as a segment, so the next appeal goes to the people who engaged.

Per-recipient delivery reporting
Responders and clickers savable as a segment
Replies threaded into the shared inbox with a draft ready

What matters most here.

Common questions

How do we avoid over-messaging supporters?: A per-contact frequency cap applies over a rolling window across every campaign and sequence, and quiet hours are applied in the recipient's own timezone.
Can we prove someone consented?: Consent is stored as a permanent record with the exact wording shown, the source, and when. It is scoped by purpose, so a transactional basis does not authorise an appeal.
Can we message volunteers for a specific shift?: Yes, if the shift is recorded as a tag or field. Segments target exactly that group.
What does WhatsApp cost us per message?: Meta prices delivered template messages by category and destination country, charged to your own WhatsApp account. Otobiz shows an estimate before a send and adds no margin.
Can beneficiaries reach us privately?: Yes, and access to those conversations can be restricted per staff member, with personal details masked for people who do not need them.
Is there a free tier for nonprofits?: Pricing is a conversation, and the shape of your programme matters more than a tier. Talk to us and we will be straight about what fits.
Can we see how an appeal actually performed?: Each send reports per recipient, and responders and clickers can be saved as a segment so the follow-up goes to people who engaged.
Can supporters ask for fewer messages without opting out?: Consent is scoped by purpose, so someone can keep receiving transactional messages while opting out of appeals. Frequency caps also limit contact without anyone having to ask.