Missed-call
100 minutes per month at the starting managed tier.
Fair usage · Service management
Know what's included before the first call.
A well-run AI system should be predictable in cost, safe to use and clear about who supports it. This guide explains the safeguards we scope for FlowFix AI receptionists, automations and managed digital systems.
This is a pre-contract explanation, not a claim that every feature is live or a substitute for a signed service agreement. Exact limits, fees, support commitments and remedies are agreed in writing for each project.
Indicative starting allowances
How much call time is included?
These are the indicative included monthly minute allowances for the published starter packages. Setup, monthly fees and optional build-and-handover prices are listed separately on our pricing page. Your written agreement defines which minutes count, transfer costs, safeguards and applicable charges.
After-hours
200 minutes per month at the starting managed tier.
24/7 receptionist
300 minutes per month at the starting managed tier.
Advanced receptionist
500 minutes per month at the starting managed tier.
Multi-location and bespoke
750 minutes per month for the indicative entry-level bespoke tier.
Standard configuration additional minutes may be available from £0.35 per minute where expressly quoted. Premium AI models, forwarding, multi-leg transfers, recording and other provider charges can require a separate rate. Usage limits and hard caps must be agreed before launch; no unlimited usage is implied.
Voice minutes and allowances
What a fair-use agreement should specify
Included call minutes
The monthly allowance, which call legs count towards it, whether usage is billed in whole or partial minutes, and how transfers affect usage.
Call limits and concurrency
Maximum individual call duration, simultaneous calls, acceptable traffic patterns and safeguards for unusually high activity.
Transparent overages
Per-minute or other excess-usage charges disclosed in advance, with the option to agree alerts, hard caps or approval thresholds.
Usage alerts
Monitoring and notice thresholds, for example before an allowance is exhausted. Actual alerts and caps depend on provider and integration support.
Human escalation
Approved transfer numbers, business-hour behaviour, failed-transfer handling and which cases must reach a person.
Third-party charges
Telephony, AI model/API minutes, booking platforms, SMS, email, hosting, payment processing and other external charges are itemised where applicable.
Responsible usage
Reasonable safeguards protect both sides.
- AI assistants should be used for the agreed customer-service and business workflows, not unsolicited bulk calling, harassment, impersonation, scams or abuse.
- Use controls should guard against repeated malicious calls, automated traffic spikes, costly loops, duplicated bookings and unapproved external actions.
- Card details, sensitive identity information, regulated professional advice and urgent safety decisions require appropriately limited workflows and human review.
- Rate limits, provider outages, suspicious activity or agreed spending caps may require a controlled pause or handover rather than unbounded usage.
- Data collection, caller AI disclosure, applicable recording notices and retention must match the client's privacy obligations and the final agreement.
Managed service versus handover
What ongoing management can mean
Managed subscription
Operating checks, routine updates, supported configuration adjustments, monitoring and agreed incident handling within a clearly documented scope. Major integrations, new features and redesigns are separate projects unless included.
Build-and-handover
Transfer of agreed deliverables, configuration and documentation under the contract. The customer is responsible for their hosting, API providers, platform subscriptions and ongoing operations unless they buy optional support.
Support response times
Coverage hours, severity categories, initial-response targets and emergency procedures are agreed per plan. A requested response time is not an uptime or resolution-time guarantee.
Changes and new integrations
New booking platforms, business locations, campaign accounts or substantially different call flows need feasibility checks, testing and a change order when outside the original scope.
Before you sign
Your proposal should answer these questions.
- What are the exact included deliverables, monthly allowance and minimum contract term?
- What will happen when a minute allowance, spending cap or provider limit is reached?
- Which third-party accounts, data and licences belong to the client?
- Which support hours, maintenance windows and escalation contacts are available?
- Who is responsible for caller disclosures, source-data accuracy, permissions and approvals?
- How are cancellations, offboarding, access removal and data export handled?
Predictable service, sensible safeguards
Get the allowance and support plan in writing.
Discuss your call volume, integrations and operational requirements before choosing a monthly or build-and-handover package.
Compare starting pricesRequest a consultation