Billing within Parallels Automation can be performed on a pre-pay or post-pay billing cycle. Due to limitations within Parallels, it is unfortunately not possible to perform per message billing, unless it is done on a post-pay basis. There are advantages and disadvantages to doing both post-pay billing, or pre-pay billing, which we outline below.
Post-pay billing allows end users to send messages forever and never use up a quota. However, performing post-pay billing requires billing implemented on the provider's side to track how many messages their customers sent and bill them accordingly. Bulletin is able to provide a monthly report outlining the number of messages sent per end user, at the providers request if performing post-pay billing. An example of the report is shown below:
Prepaid bundles are 'fire and forget' from the provider's perspective, and provides the opportunity for revenue from messages that customers purchased but never used in the time allocated. However, this can leave customers in the situation where they can't send messages due to their quota being used up. When the user attempts to send messages over their quota, they will receive the following message, and will need to purchase another bundle of messages.
Pre-pay bundles are most likely be the better way for the majority of 'small use' customers. However, 'larger volume' customers will want the ease of sending messages whenever they want to. If the users are sending large numbers of messages per month, post-pay is the best option for them. If the users are likely to send few messages per month (<1000) pre-pay may be a better option for those users.