Currently building an AI voice receptionist for a veterinary clinic in Famulor. The booking flow works well overall, but after reviewing real clinic test calls I found a major issue: - emergency/urgent calls are being handled too dynamically by the LLM - sometimes calls end too abruptly after routing attempts - trust drops immediately if the flow feels uncertain After reviewing the calls, I think the correct solution is moving more logic into an IVR menu before the AI conversation starts. Example idea: - Press 1 for bookings - Press 2 for general questions - Press 3 for urgent/emergency cases - Press 4 to talk to staff Then each path would have a more controlled flow instead of relying on the LLM to classify intent mid-call. My questions: - Has anyone built a similar IVR + AI flow inside Famulor? - What’s the best way to structure this? - Any best practices for handling urgent/emergency calls without abrupt endings or confusing routing? Would appreciate any guidance from people who’ve built production voice systems in Famulor.

Hallo zusammen, ich habe mehrere Flows laufen, die nachts den aktuellen System Prompt von Assistants auslesen. Alle Flows starten dabei um 02:00 Uhr. Bei 7 der Flows erhalte ich folgenden Fehler: Assistants request failed: 429 {"message":"Too Many Attempts."} Weiß jemand, welche API-Limits hier greifen? Das erscheint mir ungewöhnlich schnell, da maximal 17 Flows parallel laufen. Hattet ihr ein ähnliches Problem oder eventuell schon einen passenden Workaround?

Submit a bug here and we will get it addressed ASAP! Etwas läuft nicht rund? Schreib uns hier deinen Bug – wir kümmern uns ASAP darum!