Genesys Cloud - Developer Community!

Hello All 

Warm Greetings,

Description

Our production Bot Flow in Architect has hit a High flow size and keeps growing as we add intents/slots. Since Common Modules aren't supported in Bot Flows, we can't offload reusable logic the usual way.

Questions:

1. Without Common Modules, what's the recommended way to reuse logic (e.g., shared auth, shared data lookups) across intents?
2. Does calling a separate Task/Secure flow (Transfer to Flow) actually reduce size, or does it aggregate the same way Common Modules do?
3. For Virtual Agent bots - does trimming instruction/description verbosity reduce flow size, or only runtime cost/latency?

Any real examples of bringing a large production bot from High back to Medium/Low would be very helpful.

Thankyou

Hi Satish,

One option worth looking at is the new Bot Flow orchestration capability released in July.

A Bot Flow can now use Call Bot Flow to call another Bot Flow directly. Genesys specifically mentions this as a way to break larger bots into smaller focused components and reuse common functionality such as identification or data collection. Each Bot Flow also maintains its own configuration and limits.

This could potentially help with your shared authentication/data lookup logic rather than duplicating it across intents.

https://help.genesys.cloud/articles/call-bot-flow-action/

https://help.genesys.cloud/421927/

I haven't used Virtual Agent myself, so I can't comment from experience on whether trimming the instructions/descriptions would materially affect the flow-size indicator.

Hope this helps!

Hi Satish,

Just wanted to answer your second question.

If I understood correctly, you want to know if re-using a task will reduce size, or if it will aggregate the same way CMs do.

Well... As far as I know, they should work on the exact same way... Meaning that if you build a task, and then call this task dozens of times on your flow, you are not adding that whole task on your flow size dozens of times, but only 1.

And CMs should work in the same way.. If you call a CM on your flow, it will add it's size to the size of your flow, but only once (assuming you call the CM again in the same flow).

So basically, if you have a lot of repeating actions on your flow, you could build a reusable task that does those actions and just call the task each time you need to perform that.