Hi Taleb,
Hmm...A "resume IVR / resume bot" experience isn't something Genesys offers out-of-the-box or a packaged solution, yet.
Your - checkpoint + external store + ANI‑based re‑entry design is exactly the architecture anyone would recommend.
Additionally, Data Tables also allows you to store - last completed step, timestamp or any other variables, hence can be used as a 'checkpoint ledger for quickly looking up the ANI, CustomerID etc'
/about-data-tables/Other patterns / use-cases I've referred -
- store checkpoints & not the complete trancsripts/dialog.
- versioning the checkpoints
- branch instead of forcing the resume,
- if the bot and stored state diverge, route the user to a "clean restart"
Thanks
------------------------------
Ashiesh Sharma
GCX- GCP, ARC, SCR, QM
BT plc
------------------------------
Original Message:
Sent: 02-02-2026 16:36
From: Taleb TJ Mouslmani
Subject: Resume where Dropped in VA interaction
Hey All,
Has anyone implemented a "resume IVR / virtual agent" experience in Genesys Cloud for voice where a caller can reconnect after a dropped call and continue where they left off with a bot? From an architecture standpoint, I'm leaning toward externalizing bot state (checkpoints vs. full dialog context) using Data Actions to a store (DynamoDB or a Data Table for low volume), then on callback detecting a returning caller via ANI (with optional resume code or re-auth) and routing back into the bot at the checkpoint using reusable tasks. Curious if anyone has built this in production especially for voice and what patterns, guardrails, or Genesys native capabilities worked best (or didn't).
#Architect
------------------------------
Taleb TJ Mouslmani
Technical Solutions Architect, Global Solutions & Architecture
------------------------------