Agent contact verifications List

WhatsApp-OTP identity verification of a channel conversation (README_AI_AGENTS_OTP.md): once verified, the conversation unlocks the read-only tenant-data role of the tenant_assistant for a limited window. The target_* ids are frozen HERE at verification time — the LLM never chooses the tenant it reads from. Lives in the AGENT's tenant DB.

Field Description
AI agent
Conversation Channel-qualified conversation id, e.g. chatwoot:123 or iframe:key:ip
Contact phone (channel)
Verified account id
Verified company id
Verified user id
Registered cell the code was sent to
Verified via Options:
  • OTP
  • Account grant
grant = unlocked by an active account access grant plus a registered-number match, without sending a code (README_AI_AGENTS_ACCESS_GRANT.md)
Access grant id (master DB) Set when via=grant: the session dies instantly if that grant is revoked
OTP channel Options:
  • ---------
  • Meta template
  • Plain text
Which Graph API message actually left: the approved AUTHENTICATION template or the plain-text fallback
Sender line resolution Options:
  • ---------
  • Inbox line
  • First active line
inbox = sent from the WhatsApp line of the inbox the conversation came in through; fallback = first active line of the tenant
Sender phone number id
Sender WhatsApp number
Graph API message id wamid returned by Meta; the key to correlate a delivery status webhook
Graph API status code
Send error Graph API error body when the send failed (template and text attempts)
Delivery status Filled from the WhatsApp statuses webhook when available: sent / delivered / read / failed
Delivery status updated at
Code expires at
Failed attempts
Codes sent
Verified at
Verified session expires at
Revoked at

Agent contact verifications It has the following related modules and may be of interest to you: