Your team is busy. Your phone stays available.

AlpenAgent’s AI phone assistant answers calls for Swiss SMEs, records requests and appointment preferences, and hands callbacks or unclear cases to your team with full context — according to your operating rules.

Employee speaking on a business telephone

What the phone assistant handles in the workflow

3 tasks · 1 clear boundary
01

Answer calls

The assistant records the request, contact details and desired next step — even when your team cannot answer.

02

Ask for missing details

It asks only for information required by the approved workflow. Names, addresses and Swiss German are tested deliberately during the pilot.

03

Prepare the record and callback

Each conversation becomes a readable handover with the request, open points, urgency, availability and accountable next step.

One conversation, three possible outcomes

Choose a typical call. The demonstration shows the next permitted step, not a made-up success rate.

CALLERI need a service appointment next week.

ASSISTANTWhich day and time window would suit you?

CALLERTuesday morning, if possible.

Status
Appointment request recorded
Open
Check availability
Next step
Team callback or calendar confirmation

Illustrative demo data · no production recording

Automation ends where responsibility begins

Define before the pilot

The assistant may

  • Record requests and contact details
  • Ask approved follow-up questions
  • Note callback requests and time windows
  • Create a structured handover

Your team decides

  • Complaints and unclear cases
  • Professional or legal statements
  • Binding commitments without a tested integration
  • Changes to knowledge and rules

An appointment is confirmed automatically only when the calendar connection, availability and booking rules have been tested. Otherwise it remains an appointment or callback request.

What do missed calls cost in your case?

Move the four sliders. The calculation remains an adjustable assumption, not a forecast.

Illustrative annual potentialCHF 0

Excludes setup, telephony and ongoing operating costs.

Start with one controlled call type, not a major project

A pilot tests real operations rather than a perfect demonstration.

  1. 01
    Choose a case

    An appointment request or callback, for example — not the entire switchboard.

  2. 02
    Write the rules

    Required fields, approved answers, escalations and accountable owner.

  3. 03
    Test difficult conversations

    Interruptions, names, addresses, dialect and incomplete details.

  4. 04
    Document the result

    What works, what does not yet work and which expansion is responsible.

Questions before the first test

Clear answers · no black box
Does the assistant book appointments automatically?
Only when a tested calendar connection and clear booking rules are in place. Otherwise, it records an appointment or callback request.
What happens with complaints or unclear requests?
These cases are not automated further. The assistant records the available details and hands them to the designated person or group.
Can Swiss German be tested during the pilot?
Dialects, names, addresses and interruptions need their own test set. The pilot documents which variants work reliably rather than making a blanket promise.
Next step

Check a real case before it becomes a project.

Bring one typical process and one difficult exception. In the call, we clarify which data are missing, where a person must decide and whether a pilot makes sense at all.

Direct contactFrutigen · Switzerland