Hi Vaden
One possible approach would be to use the caller ANI in an Architect flow and call a Data Action that queries the Analytics Conversations API for interactions within a defined time window (e.g., last 7 or 30 days). The result could then be evaluated in the flow to determine whether the caller is a repeat caller and adjust routing or messaging accordingly.
Another option could be to maintain a lightweight lookup (database or data table) where the ANI and interaction counts are updated after each call, allowing the inbound flow to quickly check if the caller has contacted the centre frequently.
Hope this helps.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 03-10-2026 17:03
From: Vaden Green
Subject: Using Call.Ani to query prior customer interactions in architect inbound call flows
I am trying to build into an Architect Inbound Call Flow a lookup of the current call ANI against past interactions (last week, month, etc) to change the call handling for the repeat caller. The thought is that we could be more proactive in helping frequent callers.
Has anyone built something like this for their Genesys Cloud implementation?
#ArchitectandDesign
#Telephony
------------------------------
[Vaden] [Green]
[Oregon Health & Sciences University]
[Unified Communications Engineer]
------------------------------