ReplyRush help center

New Trigger Keywords Not Saving in ReplyRush – How to Fix

Denis Vithani

How to Add, Edit, and Delete Trigger Keywords in ReplyRush

If you’ve added new trigger keywords in ReplyRush but they aren’t saving or appearing, you may have missed the final confirmation step. Follow this guide to make sure your trigger keywords are added and saved correctly.

1. Adding a Keyword

  1. Navigate to the Trigger section when setting up your automation for a Post, Reel, Story, or Global Trigger.

  2. Select Keyword Trigger as your trigger type.

  3. Click the keyword input field.

  4. Type the keyword you want to add.

  5. Press the Enter or Return key. This step is important to add the keyword.

  6. Once added, the keyword will appear below the input field. This confirms that it has been added to the keyword list.

2. Editing a Keyword

In ReplyRush, keywords cannot be edited directly.

To change a keyword:

  1. Delete the existing keyword.

  2. Add the corrected keyword by following the steps in the section above.

  3. Click Save to apply your changes.

3. Deleting a Keyword

  1. Find the list of saved keywords below the keyword input field.

  2. Click the red cross (✖) next to the keyword you want to remove.

  3. Scroll down and click Save to confirm the deletion.

4. Don’t Forget the Final Save

After adding or deleting keywords, scroll down and click the Save button to confirm your changes.

Important: If you skip this step, your changes will not be applied to the automation.

Still Not Working?

If your keywords appear below the input field but Auto DM still isn’t triggering, double-check the following:

  • Trigger type: Make sure you selected the correct trigger type for your automation.

  • Permissions: Verify that your Facebook and Instagram permissions are correctly configured.

  • Linked post settings: Confirm that the correct post, Reel, or Story is linked to your automation.

Following these steps should help ensure your trigger keywords are saved correctly and your automation is configured properly.

Troubleshooting