Currently, adding keyword triggers in the Bot Builder is a strictly manual, one-by-one process—click, type, save, repeat. For businesses like ours that require 50 to 200+ keywords, this results in hours of tedious work and introduces a high risk of human error.

This limitation is the #1 obstacle preventing us from building robust, production-ready keyword bots on DoubleTick today.

What We're Asking For

To make the Bot Builder scalable for serious business use, we propose adding the following bulk management capabilities:

Import Keywords from File: Introduce an "Import" button allowing users to upload a simple .txt or .csv file. The system should parse the file and automatically populate all keywords.

Export Keywords to File: Allow users to download their active keyword lists. This enables quick off-platform editing and re-uploading, saving users from having to delete and retype everything to make bulk changes.

Bulk Paste Entry: Add a multi-line text box where users can simply paste 50+ keywords at once (either one per line or comma-separated) for instant addition.

Reusable Keyword Groups: Allow users to save specific sets of keywords as a "Keyword Pack," enabling them to instantly deploy standard trigger groups across multiple bots without starting from scratch.

Simple CSV Format Example:

Code snippet

keyword, partial_match

cable clip, YES

MCB box, NO

price list, YES

ball valve, YES

Why This Matters

Without bulk management, DoubleTick's bots are realistically only viable for small-scale businesses with 5–10 keywords.

By implementing these features, DoubleTick will immediately unlock its platform for wholesalers, retailers, and agencies managing extensive product catalogs. Allowing users to build comprehensive, professional bots with ease will significantly strengthen DoubleTick's competitive edge against platforms like WATI, Interakt, and AiSensy.

We are highly motivated to see this workflow improve and would be more than happy to beta-test this feature once it's ready. Please consider prioritizing this for your next development update.