Back to GrowthDex
Growth idea action plan

Google Chat app command menu for fast and typed jobs

Pair quick commands with slash commands so users can discover instant actions from the menu and typed workflows from the slash bar instead of learning the product by guesswork.

uncommon tacticlow budget

Why this can grow a startup

A Chat app competes with inertia inside a message box. The command system gives you two different ways to win that moment. Google's command docs say quick commands live in the reply-area menu for actions that can run immediately, while slash commands work for jobs that need extra input. That split is useful because it lets the app feel helpful to a first-time user and efficient to a repeat user without forcing one interaction model to do both jobs. A thin command surface usually means the app has not translated its workflow into the place where users actually touch it.

Company example

Google's Chat command guide says quick commands are for actions that respond immediately, slash commands are for actions that require input, and users discover them from the reply-area menu or by typing `/`.

Source and metric

Source: Google for Developers: Respond to Google Chat app commands

Google supports three command types, and quick and slash commands each allow names up to 50 characters.

ActivationProductOnboardinggoogle chatcommand discoveryfirst-use UXworkflow fit
GrowthDex operator note

When to use it

Use this when Activation, Product, Onboarding is relevant to google chat, command discovery, first-use UX and you can run a bounded test with a low budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Google for Developers: Respond to Google Chat app commands and identify what is directly supported.
  2. Choose one channel context: Activation, Product, Onboarding.
  3. Define the test around Google supports three command types, and quick and slash commands each allow names up to 50 characters..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Product-Led GrowthActivationProductOnboarding

Related tactics

Slack onboarding starts at the first invocation context

Start onboarding from the first Slack surface the user actually touches, and vary the flow for App Home clicks versus slash-command intent instead of making every newcomer take the same route.

rareOnboarding, Product, Activation

Telegram group add link requests admin rights up front

Use `startgroup` or `startchannel` links with the right admin permissions before rollout, so the bot lands in the team context with enough authority to do the job on day one.

rareOnboarding, Product, Activation

Onboarding redesign when customer context broadens

Rebuild onboarding when the buyer, setup environment, or price point changes enough that the old first-run assumptions no longer fit.

uncommonOnboarding, Product, Activation

AI install wizard for 90-second setup

Turn AI setup into a short guided wizard so a user can get from curiosity to first answer in about 90 seconds instead of ten wandering minutes.

rareOnboarding, Activation, Product

Teams default install scope matches the first job

Set the default install scope to the first place the user should get value, so Teams recommends the right surface instead of forcing them through a scope choice they do not understand yet.

rareOnboarding, Activation, Product

GitHub Marketplace installable by any user before listing

Turn on installation for any user or organization before marketplace work begins so the listing, insights, and review flow are attached to a product people can actually install.

uncommonMarketplaces, Product, Onboarding
Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian