One cleaning appointment can generate several intended messages. A confirmation, customer reminder, two cleaner notifications and a later change notice are different sends. Counting only customers can underestimate the notification workflow.
What is being counted
The first result is intended message sends, not confirmed deliveries or automatically billable SMS units. It uses the appointment count, customer messages per appointment, worker recipients, worker messages per recipient, change notices and other entered sends.
For a fictional 120-appointment month, one customer reminder plus one reminder to each of two cleaners gives 360 intended sends. Add 30 changed-appointment notices to one recipient each and the total becomes 390.
This is recipient arithmetic. It does not assume the same wording goes to the customer and cleaner, or that every message should actually be sent.
The formula
intended sends = appointments × (customer messages per appointment + worker recipients × worker messages per recipient) + changed appointments × recipients per change + other sends
The “changed appointments” input represents events requiring the specified notices. A moved visit can replace a scheduled message rather than add another reminder. Enter the net workflow you intend to run, not both the canceled old notification and its replacement as though both should be delivered.
The template and event guide identifies messages to suppress after changes, cancellations or payment settlement.
SMS units and credit packs are optional assumptions
A provider can charge by message, segment, credit or another defined unit. Length, encoding, destination and provider rules can matter. The tool therefore asks for an explicit billing-units-per-send assumption before calculating a planning quantity. It does not inspect or certify a message's encoding.
To model prepaid credits, enter the assumed pack size, pack price and currently available credits. The tool calculates whole additional packs needed to cover the planned units. It does not select the best vendor bundle automatically or assume unused credits never expire.
When price is blank, cash cost stays unknown. A blank value is not silently interpreted as free messaging. Enter zero deliberately only when that is the applicable price for the scenario.
Why subscription comparisons miss this cost
BookingKoala's SMS documentation requires a separate Twilio setup. ZenMaid documents credit bundles purchased as needed. Maidily distinguishes a paid dedicated number for two-way messaging. These are different costs and administrative models. BookingKoala SMS notifications overview ZenMaid: How much does it cost? Maidily pricing and plan matrix
A number charge, registration charge and message-credit purchase should not be collapsed into “SMS included.” Conversely, the tool does not assume every platform charges separately for every basic reminder. Use the applicable current terms for the selected workflow.
Purchases versus consumption
If a company consumes 390 assumed units and has no existing credits, 125-unit packs require four packs. It will purchase 500 units and have 110 units left under this simplified model.
The cash purchase and the consumed-unit quantity are different. A quieter month may consume previously purchased credits without another purchase. Do not report every top-up as the cost of only that month's actual messages.
These pack values are a mathematical example. The tool does not promise any particular vendor offers the selected price at all volumes, or that its credits behave identically.
Delivery, billing and other limits
The tool does not verify recipient consent, sender registration, delivery, opt-out handling, legal compliance, carrier fees, taxes or a provider's charging definition. It does not send any messages.
It also cannot decide who should receive a notice. A two-person crew may require two individual operational messages, or a supported team workflow may require something different. Do not assume one crew equals one recipient unless that is actually how the system is configured.
Avoid duplicate and outdated reminders
Start with the message event and its owner. Remove a notification that serves no purpose. Make sure a reply reaches a monitored route. Suppress reminders for canceled visits and outstanding-balance messages for settled invoices.
Use the SMS buying guide for product-specific distinctions, then add the expected cash allowance to the subscription calculator. The result should be a transparent budget, not an invented all-in price.