Convot Convot
Back to Canned Responses (Shortcuts)
Canned Responses (Shortcuts)

Per-App Shortcuts

Shortcuts are scoped to a single app - here is what that means and how to manage them across multiple apps.

Updated June 11, 2026

Each Convot app has its own set of shortcuts, independent from shortcuts in other apps. This is deliberate: a Shopify app developer supporting two different products often needs very different canned responses for each one.

What “per app” means

  • Shortcuts created under App A do not appear in conversations for App B.
  • When you open the Shortcuts panel in a conversation, the list shows only shortcuts for the app that conversation belongs to.
  • The slash trigger (/) in a conversation also only searches that conversation’s app.

Managing shortcuts per app

Each app’s shortcuts are managed at Settings → Apps → [your app] → Inbox → Shortcuts.

To switch apps in the shortcuts settings, use the app selector at the top of the Settings sidebar - each app has its own Inbox → Shortcuts page.

Duplicating shortcuts across apps

Convot does not currently sync shortcuts between apps automatically. If you need the same shortcut in two apps, create it manually in each app’s shortcuts settings.

💡

If you support multiple apps and find yourself duplicating many shortcuts, consider which ones are truly app-specific (product-specific setup guides, billing policies) vs. universal (greeting, closing, “let me check on that”). Keep universal ones as mental templates and add them to each app once.

Who can create and edit shortcuts

Any agent with access to the app’s settings can create, edit, and delete shortcuts. There is no separate permission for shortcuts management - it follows the same access level as other app settings.

Shortcuts created by one agent are available to all agents on that app.

Shortcut names must be unique per app

Within a single app, shortcut names must be unique. You cannot have two shortcuts both named /thanks. If you try to save a duplicate name, you will see a validation error.

Next steps

Was this article helpful?