For a tailored AlpenAgent implementation, the usual indicative range is CHF 2,000–5,000 for setup and CHF 500–1,500 per month. Usage, integrations and project requirements determine the quote. These are planning figures, not a fixed package offer. Standardised services may start considerably lower; compare the workflow you actually need before comparing the fees.
Updated: 15 September 2026. These ranges describe AlpenAgent projects, not the whole Swiss market.
Which scope does your business actually need?
If you only need messages and callback numbers, a ready-made service may be the better-value option. Check its languages, telephony and privacy arrangements first. A tailored implementation is worth considering when booking rules, access permissions, handoffs or several connected systems require specific work. Standard products can include integrations too; compare the actual deliverables.
| Quote item | Question to ask |
|---|---|
| Setup | Which workflows, tests and adjustments are included? |
| Usage | How many minutes are included and what is the excess rate? |
| Integrations | Does it send a message or act in the authoritative calendar/CRM? |
| Support | Who fixes mistakes, maintains changes and responds to outages? |
| Contract | What term, cancellation rules, third-party charges and VAT apply? |
Calculate the bill, not just the subscription
Monthly budget = base fee + excess minutes + telephony + agreed extras. Add setup and one-off integration work for the first year. Establish whether maintenance and support are already included so you do not count them twice.
Ask for two usage calculations in the quote: a normal month and a month with substantially more calls. Apply the same agreed excess-minute rate to both. Until that rate is established, a precise excess-usage total for your project would be invented.
Two hundred calls lasting three minutes each would use 600 minutes. Use your own call records for the estimate: a question about opening hours and a property damage report take different amounts of time. Ask about billing increments, hold time, transferred calls and what happens at the spending limit.
What a CHF 500 or CHF 1,000 project might involve
These are illustrative planning scenarios, not packages or customer case studies. They explain the AlpenAgent range; call volume can change the cost even for a simple workflow.
| Business | Possible monthly planning level | Scope to establish |
|---|---|---|
| Trades business | Towards 500 for a limited scope | Capture enquiries while staff are on site; define callback ownership, service area and urgent cases. |
| Garage | Towards 1,000 with booking integration | Workshop capacity, duration, vehicle details and handoff. An appointment request must not become a false confirmation. |
| Property management | 1,000–1,500 or more for complex routing | Property matching, damage reports, on-call staff and a backup contact. Do not assume guaranteed emergency recognition. |
| Beauty salon | 500–1,000 depending on calendars and usage | Staff, services, appointment length, cancellations and scheduling conflicts. |
Indicative first-year arithmetic: 2,000 setup + 12 × 500 = 8,000; 3,500 + 12 × 1,000 = 15,500; 5,000 + 12 × 1,500 = 23,000. These are budget points derived from the ranges. The quote must define scope, taxes and included third-party charges.
What the AlpenAgent quote needs to cover
AlpenAgent does not sell one universal package. The project defines conversation handling, data permissions, telephony, integrations, acceptance tests and operation. Answering inbound questions, qualification, appointments, calendars, human transfer and follow-up actions have been demonstrated in real demo implementations. Your agreed scope determines which are included; these demos are not evidence of numerous production outcomes.
Request separate entries for setup, monthly service, included and extra minutes, telephony, integrations, changes, support hours and cancellation. Ask how to return to your existing phone setup. A free trial can help you choose; it does not establish the cost of ongoing service.
A budget brief that makes quotes comparable
Bring a typical month of phone records to the quotation discussion: incoming call count, duration, calls outside opening hours and recurring requests. Separate answered calls from missed ones. You do not know how long a missed conversation would have lasted. Estimates should retain that uncertainty instead of treating every unanswered call as a lost sale.
Write down the task that must actually be completed. “Take an appointment” might mean sending a note to your team, or booking an available resource with confirmation and a way to amend it. Those are different acceptance criteria. If a callback workflow is enough, request it as a separate scope. You can then decide whether the extra booking work is justified for your business.
Separate telephony from platform charges
Swisscom notes that forwarding connection charges depend on your subscription; check your business line separately. Retell’s billing documentation distinguishes prepaid credits from legacy monthly billing. These illustrate possible third-party billing mechanisms, not a binding AlpenAgent tariff.
Establish whether you pay providers directly or agreed third-party charges are included in the AlpenAgent invoice. The quote should identify who monitors credit, receives warnings and handles a failed payment. This is an operational responsibility: a depleted balance should not first become apparent when a customer cannot get through.
Agree what counts as a change after launch
Updating opening hours is different from adding a CRM or another location with its own rules. Agree examples of included maintenance and work requiring a new order. Ask how an additional language, changed appointment logic or another calendar would be priced if you expect those changes. An unspecified promise of “support included” does not answer that question.
For the budget review, put actual minutes, invoices, correctly completed requests and internal follow-up work side by side each month. Record why a person had to take over. If staff must correct every note, there is work outside the provider’s invoice. Conversely, a person handling an exception is not necessarily a failure when that handoff was part of the design.
Finally, agree how you will decide whether to continue the trial, narrow its scope or stop. Use the outcomes that matter to your business, not a generic return-on-investment percentage. This is a recommended budgeting method, not a claim of measured savings or a customer result AlpenAgent has already delivered.
Still deciding on the delivery model? Compare AI, a telephone answering service and an in-house receptionist, then use the selection worksheet to test comparable offers. The AlpenAgent AI phone assistant page explains the service.
FAQ
Can I start with a smaller scope?
Yes. A narrowly defined task may require less work. Establish call volume and tasks first: a standard package may suffice, while custom integrations need separate pricing.
Is CHF 500–1,500 a binding AlpenAgent price?
No. It is an indicative monthly range. The quote defines usage, functions, ongoing work, third-party charges and tax treatment.
How can I avoid surprise charges?
Agree on metering, spending alerts, excess-minute rates and behaviour at the limit. Check telephony, additional integrations and changes separately.