A voicemail is a recording somebody still has to listen to. The agent has the conversation instead: it asks what is needed, books what can be booked, and writes a structured record that is ready to act on when the office opens.
This walkthrough begins with a conversation coming in. Inbound communication is supported today, with routing and behaviour configured through the agent. Advanced node and state-based workflow routing is in development.
The sequence below is illustrative. Your scope, routing and handoff are configured through the agent.
Handled as a conversation, rather than left as a recording for the morning.
With the configured recording disclosure at the start.
As fields on a record, not as audio for somebody to replay.
Into the calendar, inside the same conversation.
The caller gets a confirmation; the team gets a record with the thread on it.
One thread, whichever lane a step sits in.
What the agent cannot resolve becomes a record someone can act on, not a message someone has to decode.
The hours nobody is working are still hours people call in. What decides whether those calls cost anything is what is waiting the next morning: a stack of recordings somebody has to replay in order, or a set of records with the questions already asked and the answers already on them.
Drop in your website. Alebex reads it, learns what you do, and calls you in under 30 seconds — fully trained, zero setup.