@new_user___3392025fb6fd14623c16ea6 Yes, Famulor has built-in automation. You can create workflows for things like following up after a call on WhatsApp, SMS or email, and use the visual flow editor without code.
@petrkovacik Thanks! The response from EU teams has been encouraging so far 🙌 Calls and WhatsApp in one workflow seems to resonate, especially for teams that can’t afford to miss an inbound lead.
Answering calls and then following up on WhatsApp in one flow covers the gap where most small businesses actually lose leads, so this is well aimed. EU hosting and GDPR readiness are a sensible touch for anyone handling customer calls. Nice to see it start free.
we're building in this space too (phone number for AI agents) so this is close to home. the part I'm always most curious about with "same conversation, same script across channels" is what happens when a call and a WhatsApp follow-up from the same lead overlap in real time - does the agent lock state per contact so it doesn't say something on WhatsApp that contradicts what it just told them on the call, or is there a real chance of a timing collision there?
@galdayan We don’t lock a contact across live calls and WhatsApp sessions, so yes, there’s a chance of a timing collision. Both channels can use saved contact memory when enabled, but a WhatsApp reply started during a call may not yet know what was said on that call. We check concurrent memory updates to avoid one overwriting another, but that isn’t real-time coordination. For anything critical, both channels should check the same system of record or hand off to a person.
@ikoma appreciate the straight answer, most maker replies would've just said "it's handled." the "hand off to a person for anything critical" line is the real takeaway though - at Dial we ended up defining "critical" as anything involving money or a commitment date, and routing just those two triggers to a human review queue instead of trying to solve general cross-channel consistency. curious if you're thinking about building that kind of automatic criticality flag in, or leaving it to each business to define their own trigger list.
@galdayan I’d leave the trigger list to each business for now. Money and commitment dates are sensible defaults, but what needs human review depends on the workflow. We don’t have an automatic criticality flag today, so I don’t want to imply that cross-channel handoff is automatic.
@galdayan That’s the tricky part. “Critical” only makes sense in the context of the business and the action the agent is about to take. I’d rather let teams define those boundaries explicitly than have a general model quietly make the wrong call.
Replies
I see you build an automation build in???
@new_user___3392025fb6fd14623c16ea6 Yes, Famulor has built-in automation. You can create workflows for things like following up after a call on WhatsApp, SMS or email, and use the visual flow editor without code.
Looks great! All the best!
@ramitkoul Thanks for the support! 🙌
one agent across calls + whatsapp is the right call, nice work 🙌 how's adoption in the EU so far?
@petrkovacik Thanks! The response from EU teams has been encouraging so far 🙌 Calls and WhatsApp in one workflow seems to resonate, especially for teams that can’t afford to miss an inbound lead.
Awesome stuff! What languages are supported for this currently?
@khalidkhairx10 Famulor supports over 120 languages for speech recognition. Voice output depends on the TTS provider and model you choose. You can see the language coverage and compare voices here: https://www.famulor.io/supported-languages. We support options including @ElevenLabs @Cartesia Sonic @Fish Audio @Inworld @SpaceX
I’d probably try the voice simulation first It’s nice to hear how it actually sounds before putting it live.
@shubham_nair12 Thanks! Hearing the agent before going live makes a big difference. Let us know what you think when you try the voice simulation.
Answering calls and then following up on WhatsApp in one flow covers the gap where most small businesses actually lose leads, so this is well aimed. EU hosting and GDPR readiness are a sensible touch for anyone handling customer calls. Nice to see it start free.
@karimbenkeroum Thanks, Kareem! Glad the free option makes it easy to give Famulor a try. 🙌
The visual flow editor looks really useful. It makes setting up call handling feel much easier.
@maklyen_may Thanks, Maklyen! Glad the visual flow editor caught your eye. You can set up call handling without writing code. 🙌
we're building in this space too (phone number for AI agents) so this is close to home. the part I'm always most curious about with "same conversation, same script across channels" is what happens when a call and a WhatsApp follow-up from the same lead overlap in real time - does the agent lock state per contact so it doesn't say something on WhatsApp that contradicts what it just told them on the call, or is there a real chance of a timing collision there?
@galdayan We don’t lock a contact across live calls and WhatsApp sessions, so yes, there’s a chance of a timing collision. Both channels can use saved contact memory when enabled, but a WhatsApp reply started during a call may not yet know what was said on that call. We check concurrent memory updates to avoid one overwriting another, but that isn’t real-time coordination. For anything critical, both channels should check the same system of record or hand off to a person.
@ikoma appreciate the straight answer, most maker replies would've just said "it's handled." the "hand off to a person for anything critical" line is the real takeaway though - at Dial we ended up defining "critical" as anything involving money or a commitment date, and routing just those two triggers to a human review queue instead of trying to solve general cross-channel consistency. curious if you're thinking about building that kind of automatic criticality flag in, or leaving it to each business to define their own trigger list.
@galdayan I’d leave the trigger list to each business for now. Money and commitment dates are sensible defaults, but what needs human review depends on the workflow. We don’t have an automatic criticality flag today, so I don’t want to imply that cross-channel handoff is automatic.
@galdayan That’s the tricky part. “Critical” only makes sense in the context of the business and the action the agent is about to take. I’d rather let teams define those boundaries explicitly than have a general model quietly make the wrong call.