Channel Points vs Chat Commands: A Guide for New Twitch Affiliates

You hit Affiliate. Channel points unlock. You sit down to set them up and get a familiar piece of advice: “you also need a chatbot.” So you open Nightbot, or StreamElements, or whatever the tutorial you’re following uses, and start building chat commands.

A few hours in, things stop adding up. StreamElements has loyalty points that look a lot like channel points. It also has custom commands that fire on chat. Twitch has channel points and a redemption menu. The bot has commands and a loyalty system. Are these the same thing? Different things? Do you need both? Tutorials don’t say. Most assume you’ll use one and ignore the other.

This post walks through what each system actually is, when to reach for each, and how to set up both without doubling your work.

What each system actually is

Channel points and chat commands aren’t the same thing, and they aren’t competitors. They’re two different surfaces with different mechanics. Most new affiliates default to chatbot setup because that’s what tutorials cover. The result is a chatbot doing things that channel points would do better, and a half-empty channel-point menu nobody touches.

Channel points are Twitch’s native engagement system. Viewers earn points by watching the stream, roughly 320 per hour for non-subs, more for subscribers and active chatters. They spend those points on custom rewards you create as the streamer: sound effects, scene changes, custom requests, “make me drink water” prompts, anything you can configure. A redemption can fire instantly or sit in a queue for you to review. The native menu lives in Twitch’s chat UI next to the input box, and you can extend it with Twitch Extensions on your channel page.

Channel points are free with Affiliate. You don’t need a third-party tool to set up basic redeems. You do need one if you want triggers, conditions, or analytics on top.

Chat commands are a separate system that lives entirely in chat. A viewer types !command, a bot responds with text or fires an action. Chat commands don’t require earning. Any viewer can use any command at any time. They can carry parameters: !so @username includes a target. They can pull dynamic data: !uptime reads the current stream length and posts it.

Chat commands need a chatbot. The major options are Nightbot (cloud, free, simplest), StreamElements (cloud, free, bundles many things), MixItUp (desktop, free, more powerful), and Firebot (desktop, free, open-source). All four handle the basic command patterns.

Channel points use earning and redemption. Chat commands use typing and instant response. Knowing which is which from the start saves a lot of rework.

When to reach for which

The decision isn’t “channel points or chat commands.” It’s “for this specific action, which surface fits the use case better.”

Use chat commands when the action is informational

If the result is “viewer wants to know something,” chat commands are the right surface. They’re free for the viewer, instant, and don’t require earning.

The classic informational commands every channel should have:

• !schedule, when do you stream
• !socials, your other platforms
• !discord, your Discord invite
• !setup, your gear list (or a link to it)
• !uptime, how long you’ve been live
• !followage, how long the asker has followed
• !so @username, shoutout a raider or guest

These don’t belong in channel points. There’s no on-stream impact, no reason to gate them with earning, no benefit to queuing them. Free, instant, in-chat is correct.

Use channel points when the action has on-stream impact

If something happens on the stream when the action fires (a sound, a scene change, an overlay, a custom request you act on), channel points are the right surface. The earning makes it feel intentional. The cost gates it so it isn’t spammed. The optional queue lets you review redemptions like TTS or song requests before they fire.

What belongs in channel points:

• Sound effects, jumpscares, stings, music swaps
• Scene changes (face cam toggle, BRB swap, “show my desktop”)
• TTS messages from viewers
• Custom requests that need queue review (song requests, “draw something on my whiteboard”)
• Special-status redemptions (VIP grants, sub-tier-only options)
• Hydrate or stretch reminders, where the act of viewers “spending” on it makes it feel like a gift

The earning model matters here. A 2,000-point sound effect feels like an active community engagement. A free !soundeffect chat command feels like spam after the third use. Same outcome, different perceived value, because of the surface.

Use both when the same outcome should be available through both

The clearest example: you want viewers to be able to remind you to hydrate. Set up a !hydrate chat command that posts a free reminder in chat. Also set up a “Make me drink water” channel-point redeem that costs effort and triggers an overlay alert with a sound when redeemed.

Both work. They reach different viewer types. Free chatters get the casual reminder. Active redeemers get to feel like they’re “making it happen.” You’re not doubling your work, you’re offering the same outcome through both available channels.

A second example: a !followage chat command that lets any viewer check how long they’ve followed, plus the “Highlight My Message” channel-point redeem (built into Twitch by default) that adds a colored border to a viewer’s message so it stands out in chat. Both are about recognition through different mechanics. The chat command is for everyone, the redeem is for viewers who want to spend points to make sure you see them.

The pattern: identify the action, ask “what surface fits this best,” then ask “is the same action worth offering through the other surface for a different viewer type.”

Discovery: viewers can only use what they know exists

Both surfaces have the same problem. The best chat command is useless if viewers don’t know it exists. The best channel-point redeem dies if it’s buried in a flat menu nobody opens.

Channel-point discovery is hard because the native menu is a flat list with no descriptions. Chat command discovery is hard because !commands is recursive: viewers have to know to type it. Pinned chat messages decay. Bot timers spam.

Five surfaces solve discovery for both redeems and commands:

1. Twitch’s native channel-point menu for redeems and the chat input box for commands. Built-in. Visibility is low. Viewers don’t open the menu unless they know to look.
2. A !commands chat response for the command list. Free. Recursive: viewers have to know to type it. Best for chat-active streams.
3. A pinned chat message with the menu inline. Visible briefly, but decays as chat scrolls. Manually maintained.
4. An in-stream overlay that displays both lists on stream itself. Maximally visible. Requires custom build, takes on-stream real estate.
5. A Twitch Extension panel on your channel page. Sits in the channel-page UI by default. Viewers see it without typing or scrolling. Requires a one-time install. The BetterStreams Twitch Extension is one of these.

The deeper analysis of these five surfaces is in Why Most Channel Point Redeems Get Ignored, which goes through the strengths and weaknesses of each in detail. The same logic applies to chat commands.

If discovery is your bottleneck, and for most new affiliates with more than five redeems it is, that’s where to look first.

Tool routing: what to actually set up

A practical setup for a new affiliate, by component.

Chat commands (chatbot side)

Nightbot. Free, cloud-hosted, simplest possible setup. The default starting point. Five-minute setup, and the basic !schedule, !socials, !uptime commands are trivial. Limited integrations beyond chat: no channel-point read access, no overlay control. Nightbot is the right answer if you want chat commands and nothing else.

StreamElements. Free, cloud-hosted, bundles commands plus alerts plus loyalty plus bot timers plus overlays plus tipping in one platform. Heavy onboarding, but everything’s in one place. Trade-offs documented on Trustpilot and elsewhere: paywall creep on previously-free features, billing complaints (charges continuing after cancellation), and sponsorship-program issues that affected creators. Worth researching their current state before committing for the long term.

MixItUp. Free, desktop-installed (Windows only). More powerful than Nightbot for chat commands that integrate with channel-point events, OBS, and other systems. Steeper setup. Real choice if you want commands to do more than post text.

Firebot. Free, open-source, desktop-installed (Windows, Mac, Linux). Bundles a chatbot with loyalty system, built-in games, setup-sharing format, and channel-point integration. Twitch-only. Friendly setup wizard. A solid all-in-one desktop option if you don’t want a cloud chatbot.

BetterStreams. Has a chat-message trigger that can fire actions when a viewer types a phrase. Not a full-featured chatbot today. If pure chat commands are what you want, Nightbot is simpler. If you want chat triggers AND channel-point automation in one config, BetterStreams covers the trigger-and-action side.

Channel points (redeem side)

Twitch dashboard. Built into Twitch. Create rewards, set costs, set cooldowns. No triggers (rewards fire and Twitch’s queue is the only response). No conditions, no analytics, no automation. Fine for a handful of static redeems. Where everyone starts.

Streamer.bot. Free, desktop-installed (Windows). Most powerful for redeem automation. Channel-point redemption is one of dozens of trigger types. The action chain you build can do anything from chat messages to OBS scene changes to C# scripting if you want. Steep learning curve documented in community reviews. Power-user choice.

MixItUp / Firebot. Both can hook redemption events to actions through their effect systems. Firebot’s setup wizard is the friendliest entry point for new users. MixItUp’s is more capable but less polished.

CastMate. Free, open-source, desktop-installed. Profile-based system that auto-switches redeems and automations based on OBS scene or stream context. Solo-developer project, smaller community than Streamer.bot or Firebot.

BetterStreams. Free tier, web-based, no desktop install. Channel-point redemption is one of 18 trigger sources. Conditions handle context-aware activation (auto-disable a redeem when you’re not in the right scene or category). Reward analytics dashboard logs every redemption, which is data Twitch doesn’t surface natively (see What Twitch Doesn’t Tell You About Your Channel Point Rewards for the full data gap). Web-based means you can configure it from your phone.

Common new-affiliate setups

Minimum viable. Nightbot for chat commands plus Twitch dashboard for redeems. No automation, but every command and every redeem works. This is fine for the first month if you’re not trying to do anything fancy.

All-in-one. StreamElements for everything. Easiest single-tool onboarding. Review the trade-offs noted above before committing long-term.

Power-user setup. Streamer.bot for redeem automation plus Nightbot for chat commands. Steeper learning curve, but the ceiling is high. The combo most experienced streamers running complex setups use.

Web-based, low-friction. BetterStreams for redeem automation and analytics plus Nightbot for chat commands. No desktop install for the redeem side. Configure from anywhere. Free tier covers basic setup.

There’s no single tier-list. Pick the simplest combination that covers what you actually want to do, and add complexity only when you hit a real limit. For a deeper look at how streaming tool stacks fit together, see How Many Streaming Apps Do You Actually Need?.

Bringing it back to discovery

The channel-points-vs-chat-commands decision is easy once you frame it as “which surface fits this action.” Informational and parameterized commands belong in chat. On-stream impact, queue review, and earning-gated rewards belong in channel points. The same outcome can live in both surfaces if it serves different viewer types.

Once you’ve set up your menu of both, the next problem is making sure viewers can find them. The discovery problem applies equally to chat commands and redeems, and the same five surfaces solve both. Of those, a Twitch Extension panel is the only one that shows your menu of viewer interactions without requiring viewers to type a command, scroll a menu, or read a pinned message.

The BetterStreams Twitch Extension surfaces every redeem and trigger you’ve configured, with descriptions, on your channel page. If you’ve enabled the Bits-purchase tab, viewers can also buy specific triggers with Bits directly from the panel.

Already on BetterStreams? Install the Twitch Extension on your channel.

Not on BetterStreams yet? See how it handles redeems and discovery.

Most new affiliates over-build their chatbot and under-build their redeems because that’s what tutorials cover. Knowing which surface fits which action from the start, and making both discoverable to viewers, saves the rework most streamers do later when they realize the chat command nobody uses should have been a redeem, or vice versa.