Start with the call routes you expect Mossy to handle. Count those calls in a typical month and multiply by their average duration. Separate routine enquiries from longer conversations so that one average does not hide a busy queue.
For example, 120 enquiries at three minutes each take around 360 minutes. Add any planned outbound work separately and look at what happens in a peak week. Use actual call logs where you have them.
Compare the estimate with the included minutes and shared extra-minute bundles. Included minutes reset monthly. Recheck the estimate after you see the mix of calls the service is actually handling.
Count the calls the workflow will actually handle
Start with a recent month of call logs and identify which routes are in scope. A business could direct after-hours enquiries and overflow booking calls to Mossy while keeping specialist queues with staff. Count only the calls likely to enter the workflow. If your logs show overlapping routes, avoid counting a call again when it appears in a transfer record.
Group the calls by purpose where durations differ. Opening hours questions might take little time while a reschedule or service enquiry has several details to confirm. Multiply the count in each group by a representative duration and add the figures. Use a sample of calls like the ones you plan to handle so the estimate reflects actual questions.
Compare different months and account for outbound
Calculate a normal month and a busier one. A workshop may have seasonal demand or a salon may have more appointment changes in December. An allowance that covers a quiet month may need additional minutes at peak times. Keep the assumptions visible so you can replace them as soon as the workflow starts generating usage data.
Add planned outbound work as a separate line. If the team intends to call customers for feedback, estimate the number of conversations and their likely duration. Check how your specific use case will be scoped before combining it with the expected inbound total. Keep implementation and setup costs separate when you compare subscriptions.
Use the first month to replace the assumptions
Check actual minutes once the workflow is running and compare them with the estimate by type of call. If usage is higher, find out whether more calls entered the route or conversations took longer. A slower call may be useful when it avoids another contact. Review the outcome alongside the duration before trying to shorten the flow.
Check the published allowances and extra-minute bundles with your busiest months in mind. Record when the team wants to review its choice and who will look at usage. Included minutes reset each month, so use a monthly estimate for the comparison. Adjust the forecast when you add a new service, reach more callers or extend the coverage window.
Show your assumptions when you share the estimate
Keep a small table with each call type, expected monthly volume, average length and estimated minutes. If one group is based on memory, mark it for review when better records are available. Use a low and high range when calls vary significantly. The team can then see what changes the plan decision and update the figures without rebuilding the estimate from scratch.