Scheduling, SMS, and outbound calls
Read appointments and patient context from your EHR, then have HUM run the conversation and write the result back as a structured outcome.
Appointment-aware reminders
Build a call list from a FHIR Appointment query (or push one from a scheduled job). HUM dials each row with the visit context already loaded into the agent prompt.
Two-way SMS with AI
Bi-directional, A2P-compliant SMS on the same numbers used for voice. Inbound replies route into a SMS-channel flow where the AI answers, calls your tools, schedules follow-ups, or hands off to a human inbox. STOP / HELP / START are processed automatically.
Outbound voice campaigns
Throttled outbound campaigns with retry policies, voicemail drop, and answering-machine detection. Outcome data (confirmed, rescheduled, no-answer) is posted back via webhooks.
Order, result, and visit notifications
Push order and result events from the BlueHive provider network — or your own HL7 gateway — and trigger HUM to call, text, or notify the right team.
Order received → patient outreach
When a new order lands in the network, fire an event that builds a small call list and dials patients with prep instructions or scheduling next steps.
Result ready → notify staff
Use webhook subscriptions to alert clinic staff or providers — including a callback flow that confirms receipt before marking the result acknowledged.
Visit outcome → CRM / EHR
Every HUM call can capture structured outcome JSON (e.g. confirmed, rescheduled_to, declined_reason) that gets posted to your downstream system on completion.
Connected to 20,000+ providers nationwide
HUM is part of BlueHive — the same network that powers occupational health, drug testing, DOT physicals, and provider-to-employer communication across the country. Order events, scheduling requests, and provider context can flow through the network and trigger the right voice or SMS workflow in your clinic.
- Provider directory & lookupFind the right clinic in the network with marketplace lookup tools available to flows.
- Same compliance postureHIPAA-grade controls, audit logs, blocklists, and BAA available on Enterprise.
- Tenant API keysIssue scoped API keys per integration, rotate without downtime, and audit usage.
Connect any CRM with one signed HTTP contract
HUM resolves callers against your CRM and writes finished-call activity back — with no CRM-specific code in the call path. Register a connector (base URL plus a shared secret) and implement four endpoints; HubSpot, Salesforce, Zendesk, or your own system can speak it.
Caller lookup & auto-create
On each inbound or outbound call, HUM posts the number to /contacts/lookup to resolve a contact — and optionally /contacts to create one it can’t find — so every call is attributed to the right record.
Call activity sync
When a call ends, HUM posts the transcript, AI summary, and structured outcome to /calls. Every request is signed with HMAC-SHA256 and a bearer secret you verify on your side.
Pre-call enrichment hooks
Pre-call HTTP hooks pull CRM context — recent orders, balances, appointment history — into the agent prompt before Bea ever speaks, within a strict latency budget so the caller never waits.
Webhooks, MCP, and a public OpenAPI
Everything HUM does is automatable. Subscribe to events, expose tools to agents, or drive HUM directly from your own backend.
Signed webhook events
Subscribe to call.completed, voicemail.received, outcome.captured, sms.received, and more. Each delivery is signed so you can verify it came from HUM.
MCP tools for agents
Expose your internal APIs as Model Context Protocol tools. HUM agents call them mid-conversation, with per-flow allowlists and per-org secrets.
Tenant API keys
Issue scoped API keys per integration. Use the same OpenAPI spec for every endpoint — schedule calls, fetch transcripts, manage call lists, and more.