Estimate Usage for a Tailored Call Flow

A non-standard inbound call flow often has several branches: a routine answer, a business-specific qualification path, and a request that needs a person. Those branches should be designed around the decisions your team approves. They should also be estimated as different kinds of call time, because a single average duration can hide a longer exception path.

Use scenarios rather than a generic call average

Before discovery, list a few real categories of caller request without adding customer details. For each, note the questions your team wants asked, the expected next owner, and an estimated monthly count and duration. Include a case where the caller cannot answer a key question. Label every duration assumption until you have measured data. The decision-point guide helps with the path itself; this worksheet is for the volume behind those paths.

Multiply monthly calls by expected inbound minutes for each scenario, then add the groups. Keep SMS as a separate count rather than assuming a text follows every call. If an exception moves to a human, do not invent a product behavior or billable duration for the downstream work; confirm the proposed handling and scope in the design conversation.

Distinguish the phone subscription from custom scope

Solution HD's published standard AI Phone Agent subscription is $249 per month with 500 inbound minutes and 500 SMS included. Additional minutes are $0.15 each and additional SMS $0.03 each. The standard subscription is month to month, with no setup or onboarding fee and sales-assisted initial call-flow setup. Those public terms are a baseline usage reference, not a quote for any non-standard integration or separately agreed custom work.

Illustrative month, not a quote: If a proposed call mix totals 575 inbound minutes and 520 SMS, usage above the allowances is 75 minutes ($11.25) and 20 texts ($0.60). That yields an illustrative phone-service total of $260.85 before other applicable charges. A 430-minute, 300-SMS month would remain at the $249 base. Your actual usage and any separately agreed scope determine the actual total.

Bring two lists to the conversation

First, bring the scenario counts and time assumptions. Second, list every requested behavior whose scope still needs confirmation: unusual decision rules, a named destination, or a special handoff. Keeping those lists separate lets the team discuss cost without treating a bespoke requirement as silently included in the standard subscription. It also keeps a useful question open when the answer depends on your specific operating rules.

For the current subscription details, see the Solution HD terms. To discuss a call mix or workflow for your organization, contact Solution HD.