Webchat on your website, phone calls over SIP, official WhatsApp, email and browser push. The agent is configured once: same prompt, same tools, same memory. The channel only decides how the conversation reaches it.
Switching channels shouldn't mean rebuilding the bot.
Text, audio and images — plus real-time voice on the phone.
At Hal-AI, a channel is a delivery route, not a personality. The agent that answers on WhatsApp is the same one that answers in your website chat and the same one that picks up the phone: one prompt, one set of tools, one Knowledge Vault and the same long-term memory — the technology at the heart of the patent filed with the USPTO.
What changes from channel to channel is the format: a website chat accepts attachments and interactive options; a phone call accepts voice, DTMF and extension transfers. The reasoning behind it is identical.
Voice conversations are recorded as turn-by-turn transcripts too.
The platform generates the chat embed code — iframe or widget — plus a shareable link and a QR code. You decide how the customer reaches the agent: inside the site, through a link in a social profile, or from a code printed at the counter.
One agent, published three ways. Generated a new link? The previous one is invalidated immediately — no stale addresses floating around.
Attachments, photos, camera, recorded audio and interactive options. The visitor sends the receipt; the agent reads it and answers.
When the subject calls for a person, the agent hands it off. The conversation continues in the same card, with the full history in front of the operator.
Webchat conversations land in the CRM alongside WhatsApp ones, separated by channel and pulled together on the customer record.
An in-house simulator, identical to WhatsApp, so the manager can talk to the agent and tune its behavior without burning a real number.
If the customer already talked to you on another channel, the agent doesn't start from scratch: long-term memory belongs to the agent, not to the window.
The customer calls your number and the agent answers, speaking naturally, in real time. This isn't an IVR with recorded options: it's the same conversation they'd have over text, now by voice, with access to the same tools and the same systems.
SIP extensions are registered on the SIP Channels screen, with the password encrypted and the trunk registration status visible to the manager.
Same prompt, same tools, same memory as the text channels. It listens, understands and responds at the pace of a live call.
It calls your ERP or medical record APIs, verifies the order, sends DTMF when it needs to navigate another system, and resolves the issue while the customer is still on the line.
It passes the call to a human extension when the case calls for it, triggers the same agent's WhatsApp to send a document, and ends the call.
Voice runs over your own SIP trunk. If you already have a phone system, you keep your numbers and connect the agent as one more extension; if you'd rather have the phone system, the CRM and the AI in one environment, there's Hal-AI UCS Cloud.
Voice channels are configured in the console, with the extension password encrypted and registration status tracked on screen.
Webchat and voice aren't two products: they're two deliveries of the same agent. On the left, the widget published on the website; on the right, the same conversation happening over the phone.
The screen shows both channels side by side for a fictional Aurora Store order. On the left, the visitor talks through the widget published on the website and the agent replies with the delivery estimate for Route 12. On the right, the same person calls the SIP extension and the agent answers live: the timer runs, the state reads “on a call” and the transcript records every turn, including the API calls made during the conversation and the offer to transfer to a human extension. Because the brain is the same, the call picks up where the chat left off — with no need to repeat the order number or start over.
Voice is usually the most opaque channel in an operation: nobody knows what was actually said. Here, every AI-handled call is logged with a full transcript.
Without digging through recordings, and with the same rigor you already expect from your human team.
Not every message is a conversation. Some channels exist so the agent can deliver finished work to the people who need to see it.
Email is how operational reports go out as PDFs, on a recurring schedule, along with the analytical documents Squads publish at the end of a run.
The manager assigns a mission to the HAL Copilot, closes the page and gets on with the day. When the work is done, the notification lands in the browser.
There's also the agent test chat: an in-house simulator identical to WhatsApp, for trying out the agent's behavior without using up a real number.
Hal-AI is a Meta Business Partner and runs on the Official WhatsApp Business Cloud API. Official numbers are connected through guided onboarding: the company authorizes through Meta's flow, pending phone numbers show up on the activation screen and become channels on the platform.
Every official number becomes a channel on the platform, with your agent attached and your license tracked on the Channels screen. Coverage is 24/7, across text, audio and images.
For teams who'd rather not juggle three vendors: the cloud phone system, the CRM holding the history from every channel, and the AI agents handling voice and text — side by side with your team's extensions.
The platform's four conversational channels serve different moments in the customer relationship. All of them run on the same agent.
Solves: talking to existing customers in the app they keep open all day, with history that doesn't get lost.
Meta Cloud API, official templates and number protection.
Solves: capturing the visitor who just landed on your site and isn't a customer yet, without demanding a phone number before helping.
Embed, shareable link, QR code and attachments.
Solves: serving people who'd rather call — including the ones who call after hours, when nobody's at the desk.
Real-time handling, transfers and transcripts.
Solves: delivering what the agent produced — a report, an analytical document, an alert that the work is done.
Server-side PDFs, scheduling and authorized recipients.
No. The agent is configured once — personality, tools, Knowledge Vault and memory — and the channel only decides how the conversation reaches it. The same agent answers on WhatsApp, in the website chat and on the phone, with the same reasoning and the same customer history.
Yes. SIP extensions are registered on the SIP Channels screen, with the password encrypted and the trunk registration status visible in the console. The AI answers the call in real time, holds the conversation, queries the connected systems, sends DTMF, transfers to a human extension when the case calls for it, and hangs up when the conversation is over.
They do. WhatsApp and webchat land in the same CRM, separated by channel and pulled together on the customer record, with human takeover at any moment. Calls get the phone conversations screen, showing the calls active right now, the history by number and a turn-by-turn transcript of every voice conversation.
Bring us the reality of your operation — the site that doesn't convert, the phone nobody answers, the WhatsApp that ground to a halt. We'll show you what it looks like with a single agent covering all of them.