Clear communication costs before conference day, including whether urgent SMS messages draw from separate credits. When a live delay hits, an unclear allowance can leave a transport coordinator choosing between extra spending and members waiting at the wrong pickup point.
At 5:42 p.m. on a Friday, Kojo stood beside a delayed bus in Accra with his phone in one hand and a printed passenger list folded under his arm. He was an invented composite, but the decision in front of him is entirely plausible: send an urgent update to every registered passenger, or let people continue travelling toward a departure that would not happen on time.
The message was ready. The recipient list was ready. The SMS balance was not.
The alert that could not wait
Kojo had already updated the bus status in the church’s coordination system. Members using the app could see the delay, but an urgent transport message needed wider reach. Some passengers might have disabled push notifications. Others might have limited data or might not open the app before leaving home.
SMS was the dependable second route.
Then the send screen showed that the available credits could not cover the full passenger list. Kojo had assumed urgent messages were part of the church’s subscription. The finance volunteer believed the same. Nobody had checked whether the plan included a monthly SMS allowance, charged each text separately, or required prepaid credits.
The bad ending was now possible: families could reach the pickup point and wait without knowing when the bus would arrive. A few might leave. Others could miss the conference entirely.
Kojo considered sending the message only to branch leaders and asking them to relay it through WhatsApp groups. That would save credits, but it would also create several versions of the same update. One group might receive the new departure time. Another might get a forwarded message after the bus had already arrived.
This is the practical danger behind vague phrases such as “SMS included.” A feature can exist inside the product while its delivery cost sits outside the subscription. What happens when “SMS included” still means paying per text? examines that pricing language more closely.
Communication pricing belongs in the event plan
Church software pricing often focuses on seats, members, branches, or feature tiers. Conference teams also need to understand the costs triggered by real activity.
Before approving a plan, ask how each communication channel is billed. Does the subscription include a fixed SMS allowance? Do unused credits expire? Does one long message count as multiple texts? Are delivery retries charged? What happens when the balance reaches zero during an active event?
Those questions should have written answers. A verbal assurance from a sales call will not help the transport desk on Friday evening.
The same review should cover the full escalation path. ChurchFlow, for example, is designed to route bus updates according to urgency, with push notifications for minor delays and broader combinations of SMS, push, and WhatsApp for more serious disruptions. That routing logic can help coordinators reach the right passengers through the right channels. The church still needs clear commercial terms for any paid messaging service connected to it.
A useful event budget separates the software subscription from variable communication costs. Estimate the number of registered passengers, the likely number of reminders, and the messages that could follow a delay, cancellation, or pickup change. Then add a buffer for the day nobody planned.
Build the fallback before anyone boards
With the bus still stationary, Kojo called the administrator who controlled the messaging account. She approved a credit top-up and confirmed the payment through the account’s established process. The balance appeared with only a short window left before passengers began leaving for the pickup point.
Kojo sent one concise update to the registered riders. The message named the bus, the delay, the revised departure time, and the pickup location. He then checked the delivery record instead of assuming that pressing “send” had completed the job.
The immediate problem had turned. The more valuable change came on Monday.
Kojo added a communication check to the conference runbook. One named person would verify the SMS balance before transport registration opened, again before the final reminder window, and once more on event day. The finance team would know who could approve additional credits. Coordinators would have a prepared fallback for members who could not be reached by the primary channel.
That ownership matters. Software can show bus capacity, target updates to registered passengers, and record delivery attempts. It cannot resolve an internal question about who may authorize a top-up unless the church settles that question first.
Similar failures happen when teams assume a feature label explains the operational details. Efua’s vague pricing pages shows why procurement teams need limits, exclusions, and actual workflows before choosing a plan.
Put the cost beside the responsibility
A conference communication plan should name four things in one place: the channel, its cost model, the person responsible, and the fallback if it fails.
Keep that page beside the transport plan. Review it during the final event briefing. Test a real message with the same account and delivery route the team will use on conference day. Confirm that the person monitoring buses can see the balance and knows whom to contact without searching through old chats.
On the next Friday, Kojo’s printed passenger list carried one extra note at the top: “SMS balance checked.” It was a small line, but it removed one dangerous uncertainty before the first bus moved.
Comments
No comments yet.