Where the agent answers
Phone, web, and the handoff.
Provision a number or bring your own trunk, embed the agent in your product, and hand the caller to a person when the conversation needs one.
Capability
07 / 11
Channels & transfers
Your number, or ours
Provision a number from the platform, or connect your own SIP trunk and keep the number your customers already dial. Nothing about the agent changes when the line does.
The same agent on the web
The Voice Agents Web SDK puts the agent inside your site or product, where it can also act on the interface in front of the user. Same agent, same tools, same call history.
Warm and cold transfers
Hand the caller to a phone number with or without a briefing first, or pass them to another Hamsa agent that specialises in what they asked for. Transfers are nodes in the flow, which means they can happen anywhere you decide they should.
Keypad input
Callers can respond on the keypad where speaking is awkward or unsafe (menu selections, reference numbers, confirmations), and the flow branches on the digits.
More capabilities
How the call behaves
Call controls
Tune interruption, response delay, silence timeouts, and call duration: the settings that separate a natural call from an awkward one.
Read →Designing the conversation
Flow Builder
Design the call as a graph: conversation, tool, router, transfer, and end-call nodes, connected by conditions you define rather than hope the model infers.
Read →Calls you initiate
Outbound campaigns
Upload a recipient list, pass per-recipient variables into the flow, and run collections, renewals, reminders, or win-backs with the agent you already built.
Read →


