Answers before you put AI on the phone.

Yes. Most teams start by forwarding missed, busy, overflow, or after-hours calls from the number customers already know.

Yes. Conditional forwarding can send calls to Havio only when your team does not answer, is busy, or outside coverage hours.

It is a phone-carrier rule that routes calls to the AI receptionist only under specific conditions, instead of replacing your main line.

Yes. Transfer rules can use caller intent, urgency, location, language, account type, or service category.

It answers from approved business knowledge: hours, services, locations, policies, FAQs, booking rules, and escalation paths.

Yes. The greeting, tone, required fields, disallowed claims, and fallback rules are configured before launch.

The agent should not improvise. It can transfer, create a callback task, or say that a person will follow up.

Yes. It can collect required details, check rules, book or request a slot, and send the outcome to your calendar or CRM.

Havio recommends clear AI disclosure and region-aware consent language before the agent handles live callers.

Recording and transcript settings depend on your plan, region, and consent requirements. The setup defines what is retained.

Data deletion and export requests are handled through the privacy and DPA process for the account.

Sensitive or regulated calls should route to approved human fallback instead of letting the agent advise beyond its allowed scope.

Plans are built around included monthly minutes, active agents, phone numbers, integrations, support, and concurrency.

Carrier failures that never connect to the agent are not treated as handled calls. The AI-handled part of a transferred call counts toward included minutes; downstream carrier or destination charges are separate when they apply.

Standard extra usage is modeled at EUR 0.08 per additional minute unless a custom Enterprise term overrides it. Higher-volume teams can move to Scale or custom terms.

Each plan states its included numbers, onboarding scope, and support level. Complex integrations are scoped separately.

Yes. Calendar workflows can check rules, request or reserve slots, and leave a structured booking record.

Yes. CRM workflows can create notes, update lead fields, attach summaries, and trigger follow-up tasks.

Yes. Webhooks and automation tools are useful when a workflow does not need a full custom integration.

Yes. The agent can create support tickets and alert the right channel with caller intent, urgency, and next action.