How Civagent Knows It’s You in Teams, Slack, and WhatsApp

In everyday agency work, identity checks protect both staff and the public.

If an assistant cannot tell who is asking, it can deliver the wrong information, make the wrong update, or expose data to the wrong person. Civagent is designed to reduce that risk by using channel identity, confirmation steps, and audit records together.

What Civagent Recognizes Automatically

When you message Civagent through supported channels, the platform receives identity context from that channel.

  • Microsoft Teams: organization-backed user identity and display name
  • Slack: workspace user identity and profile context
  • WhatsApp: phone-number identity from the WhatsApp account

This allows Civagent to treat your request as coming from a specific, recognized user rather than an anonymous prompt.

When Civagent Asks You to Confirm

For routine questions, Civagent can respond directly.

For higher-risk requests, Civagent can require extra confirmation before proceeding. Typical examples include:

  • requests that affect records or workflows
  • requests involving sensitive or restricted information
  • requests where identity confidence is lower than required by policy

This is a safety layer, not a failure. It is how Civagent helps prevent mistaken or unauthorized actions.

What Happens If Identity Cannot Be Verified

If Civagent cannot verify identity with enough confidence, it will not take a sensitive action.

Instead, it can:

  • provide a safe, limited response
  • ask clarifying or verification questions
  • route you to a human process when needed

Default behavior is to fail safely rather than guess.

What Gets Logged and Why

Civagent maintains logs for key events related to requests and actions. This helps teams answer practical questions such as:

  • who requested an action
  • when it happened
  • what was approved, denied, or deferred

These records support internal trust, oversight, and operational clarity.

Quick FAQ

Can someone impersonate me?
Civagent relies on the identity controls of the channel you use, plus confirmation checks for sensitive actions.

What if I switch devices?
If you are still authenticated in the same channel account, Civagent treats you as the same user identity for that channel.

Why did Civagent ask me to verify this request?
Because the request was classified as sensitive or confidence was below the policy threshold for automatic action.

Will Civagent act if identity is unclear?
For sensitive actions, no. It will request verification or route to a safer fallback.