Agent identity & reachability
Every agent gets its own email and phone number
Real channels. Real identity. Threaded conversations. Logged calls. Compliance-ready voice and email — not just chatbot bubbles in a browser.
Why identity matters for agents
An agent without its own email and phone number is a tool reachable only through UI bubbles. With its own identity it becomes a colleague: customers email it, suppliers call it, other systems send it notifications. HybridClaw provisions a real email address per agent (on your domain or a hybridai.one subdomain) and optionally a real phone number with voice and SMS routing.
Three channels, one identity
All three channels land in the same audit log and the same memory as web and Slack interactions.
Own address per agent, DKIM/SPF-configured. Inbound mails get parsed (including attachments), outbound mail comes from the agent account.
Voice
Real phone number via Twilio. Inbound calls are transcribed and handed to the agent, outbound calls can be scheduled.
SMS
With an SMS-capable number the agent can send and receive SMS — ideal for one-step confirmations and push notifications.
What this enables in practice
- Vendor onboarding via email. The finance agent can exchange KYC documents directly in the email thread with the supplier — no human in the middle.
- After-hours call answering. The support agent picks up the call, answers standard questions and creates a ticket entry. When complexity rises: warm transfer to a human.
- Outbound research calls. The sales agent calls the target account to confirm reachability or contact person — with transcribed history landing in CRM.
- Automatic attachment processing. Inbound invoices arrive as PDF attachments, get parsed and forwarded to DATEV/Lexware.
- Real address book entry. Agents show up with email and phone number in the Outlook/Google contact book of the team.
Chatbot vs. agent with email/phone
With email + phone
- Reachable like an employee
- Existing communication paths keep working
- Full audit trail from real channels
- Works with Outlook, Gmail, Teams and Twilio
- Scales to 24/7 without a shift schedule
Classic chatbot
- Reachable only in browser bubble
- Customers must adopt a new channel
- No attachment processing
- Calls get forwarded to humans
- Struggles with off-hours
Questions on agent reachability
Are the phone numbers in the EU? +
Yes. In Managed Cloud, DE numbers (national geographic, mobile or 0800-service) are provisioned via Twilio EU. Your own Twilio account can be integrated on request.
Can the agent place calls or only receive them? +
Both. Inbound calls are transcribed and handed to the agent in real time. Outbound calls can be triggered (e.g. "please call the customer at 2pm about contract renewal").
How is spam handled? +
Emails are filtered for spam and phishing before they reach the agent. Voice has configurable limits (max outbound calls per hour, blocklists).
What happens with call recordings? +
Transcripts go into the audit log, audio is optional. Retention is configurable. PII in transcripts is masked by the same mechanism as all other logs.
Does this only work in Managed Cloud? +
Email works self-hosted too (your own SMTP server is enough). Twilio Voice can be self-hosted-integrated, but Managed Cloud ships number provisioning out of the box.