The call runs on the call node
Answering, conversation, transfers, hang-up, keypad, and recording use a verified, signed copy of the agent. They do not depend on the rest of the platform being reachable.
You should know how your calls and records are handled. Here are the protections and operating decisions built into CareAgt.
Answering, conversation, transfers, hang-up, keypad, and recording use a verified, signed copy of the agent. They do not depend on the rest of the platform being reachable.
Blocked callers, caller-type rules, and time limits are decided before the call connects.
Lookups are answered within seconds or skipped. A slow connected system does not stall the call.
Recordings, transcripts, and usage are written to the call node first. Queued work is confirmed as queued, never silently dropped.
Media nodes are assigned per customer. A customer’s calls stay on one node.
Published agent configurations are versioned. Earlier versions are kept and can be restored.
API keys, passwords, and tokens are sealed with a master key that lives outside the database and the code.
E-mail and password, Google, or Microsoft, with optional two-step codes. Sessions expire. A partner’s access uses a scoped key.
Roles decide who sees which agents, cases, and recordings. Group membership and custom roles keep access specific.
Names, phone numbers, and transcript text are kept out of e-mails and notifications when this mode is enabled.
Caller keypad digits are never written to logs.
Changes to an agent’s words are checked before they go live. Accounts can also require a person to review them.
Every change is recorded: who made it, what changed, and when.
Set a retention period for each account. Recordings and transcripts are deleted on schedule.
We set up your first agent with you, from your own instructions.
You test it before a single customer call reaches it.