contacts-manager

To resolve fragmented user identity, you can map disparate platform IDs like WhatsApp to a single canonical contact record. This ensures consistent identity resolution and continuity across diverse communication channels and session types.

You can automate contact intake by capturing new user identities automatically, assigning default tags, and applying pre-configured routing rules. This manages operational policies and routes conversations based on allowed, blocked, or pending contact statuses.

Backfilling contacts from chat ledgers extracts historical interaction data to populate canonical contact records. This process ensures durable identity management and auditability across diverse communication channels within the Ravi runtime environment.

Yes, you can manage granular routing policies by assigning contact statuses such as allowed, blocked, or pending. This operational policy layer restricts or permits user interactions across multi-agent communication channels.

The best way to approve pending contacts is to list all pending records and approve specific users by their phone number or platform ID. This automatically assigns default tags and applies pre-configured routing policies.

You need centralized contact management to ensure auditability across diverse communication channels. It provides a unified, durable layer that tracks canonical records, platform identities, and interaction policies for multi-agent systems.