weiter lesen: https://docs.famulor.io/de/updates/changelog#-whatsapp-koexistenz-—-business-app-auf-dem-handy-behalten

Niceee

you’re spotting exactly what breaks in production voice systems: high-stakes intent (emergency) + open LLM routing + unclear handoff = trust loss. Your IVR-first instinct is right. In Famulor, the most reliable pattern is usually: 1) Deterministic menu first, AI second: Use Flow Builder and put a keypad collection step at the very start (Collect keypad input): - Press 1 → Bookings (tight, scripted flow) - Press 2 → General questions (lighter AI, strict KB) - Press 3 → Urgent/emergency (almost no improvisation) - Press 4 → Staff (transfer path) Then branch into separate subflows per option instead of one big prompt where the model classifies intent mid-call. 2) Keep emergency logic out of “free conversation”For option 3, avoid dynamic LLM decisions like “is this urgent?”Use a fixed script: - acknowledge urgency in one sentence - collect only minimum data (pet name, symptom severity, callback number) - always explain next step (“I’m connecting you to our on-call team now, please stay on the line.”) - then warm transfer (preferred) or cold transfer Also enable “Send message before transfer” so callers never experience a sudden hangup. 3) Why calls feel abrupt today: Common causes we see in clinic setups: - transfer triggered without a closing phrase - LLM ends call after failed routing attempt - no fallback when transfer fails (should route to voicemail + ticket/SMS, not end) Add explicit fallback nodes:transfer failed → apology + alternate number + voicemail/task creation. 4) Structure that works well in Famulor - Inbound assistant #1 (main line): menu + routing only - Branch flows: booking / FAQ / emergency / staff - Emergency branch: deterministic + warm transfer to on-call - Booking branch: can stay more AI-driven (calendar tool, confirmations) - Staff branch: immediate warm transfer with short briefing to staff Note: one phone number supports one inbound agent, so use Flow Builder branches (or external PBX IVR routing to different numbers/assistants), not four separate inbound agents on the same number.

Ich habe mir angeschaut, was du im Chatverlauf siehst. Dort erscheint folgender Fehler: „Error code: 63051“. schau mal https://www.twilio.com/docs/api/errors/63051 Twilio nennt als mögliche Ursachen z. B. 30 Tage Inaktivität, Policy-/Account-Probleme oder einen Verifizierungs-/2FA-PIN-Mismatch. Die empfohlenen Schritte sind: Sender neu registrieren, WhatsApp Manager/WABA-Status prüfen, 2FA-PIN prüfen, damit die Einschränkung bei Meta geprüft/angefochten wird.