Slash Commands in RankTalk for Faster Team Workflow

Slash commands are the power-user interface of RankTalk. They are keyboard-driven shortcuts that execute actions, change settings, search history, set reminders, invoke AI features, and manage channel state — all from the message composer, without touching the mouse or navigating through menus. For team members who spend significant time in RankTalk every day, learning the slash command vocabulary is one of the highest-leverage investments they can make in their daily workflow efficiency.

This guide is a complete reference to every slash command available in RankTalk: its exact syntax, its optional parameters, the specific use cases it is designed for, the SEO agency workflows it enables, and the common mistakes to avoid for each command. Read through the complete reference once to understand the full scope of what is available. Then return to specific sections when you want to add new commands to your active vocabulary.

How Slash Commands Work

Type / in any message composer — in a channel, DM, thread, or the search bar — and the slash command palette appears above the composer showing all available commands. Continue typing to filter the list: typing /re filters to /remind, /reactions, and any other commands starting with "re." Click any command in the palette to insert it into the composer with its syntax template, or continue typing the full command manually. Press Enter to execute.

Commands that require parameters (like /remind and /status) show a syntax template in the palette that indicates where parameters go. Parameters are entered directly after the command with a space: /remind @sarah Review the Lapron report in 2 hours. The command palette shows parameter hints as you type, so you always know what format is expected.

The /remind command sets a time-based reminder that delivers a direct message notification at the specified time. It is the most universally useful slash command in RankTalk for SEO agencies, where time-sensitive commitments — KPI update deadlines, sprint closing times, client report delivery dates, overdue task follow-ups — are part of every workday.

Syntax

/remind [recipient] [message] [time expression]

Recipient options: @[member-name] for a specific person's DM, @here to notify all currently active members of the current channel, me to remind yourself only. Time expression options: in [N] minutes/hours/days, at [time] (uses your workspace timezone), on [day] (Monday, Tuesday, etc.), tomorrow morning, next [day], on [date] (April 18, Apr 18, 18 April).

Examples

/remind @sarah Review Lapron monthly report in 2 hours — sends Sarah a DM reminder in 2 hours with the message text and a link back to this channel for context. /remind @here Sprint 14 closes at 5 PM today — ensure all tasks are in Done or flagged as deferred — sends a channel notification to all currently active members at the time you set it. /remind me Follow up with TechWave link prospects on Wednesday — sends yourself a DM reminder on Wednesday morning. /remind @omar KPI updates for Lapron goals due in RankOps by 5 PM today — specific personal reminder for a teammate.

Recurring Reminders

Append every [day/week] to any /remind command to create a recurring reminder: /remind @here Weekly KPI update day — update all goal values in RankOps by 5 PM every Friday. Recurring reminders continue until cancelled. To cancel a recurring reminder, open your DM with the RankTalk Bot (which delivered the reminder) and click the "Cancel reminder" button that appears on the reminder message.

SEO Agency Use Cases

The /status command sets your personal availability status visible to all workspace members. It is the simplest and most impactful command for async team management — when every team member uses status consistently, managers can make informed decisions about communication timing, task assignment urgency, and meeting scheduling without having to ask "are you available right now?"

Syntax

/status [emoji] [status text]

The emoji is optional but strongly recommended — it allows the status to be read at a glance without reading the text. Common status emojis: 🟢 (available), 🎯 (deep work), 📞 (on a call), 🔕 (do not disturb), 🏖️ (out of office), 🤒 (sick — use when you're unwell to set the right expectation), ✈️ (travelling). To clear your status: type /status with no parameters.

Status Duration

Append a duration to auto-clear the status after a specified time: /status 🎯 Deep work — back at 2 PM until 2:00 PM. The status clears automatically at 2 PM. This prevents the stale status problem — a team member who set "On a call" three hours ago and forgot to clear it, leaving colleagues confused about their actual availability.

Recommended Status Vocabulary for SEO Agency Teams

The /ai command is a shortcut to the AI Composer that pre-fills the prompt with the text following the command. It is the fastest way to draft a message with AI assistance: instead of opening the AI Composer and then typing the prompt, you type the full prompt inline in the message composer and invoke the AI in a single step.

Syntax

/ai [prompt text]

The prompt text can be as brief or as detailed as needed. /ai Write a sprint kickoff for Sprint 14 produces a generic kickoff. /ai Write a sprint kickoff for Sprint 14 for the full team — Lapron is priority client, 18 tasks in RankOps, goal is 8 DR40+ links by April 18, KPI updates by 5 PM daily produces a specific, actionable kickoff ready to review and send.

The Inline Prompt Technique

The most efficient AI Composer usage pattern: type /ai, then type the complete prompt inline without pausing, then press Enter. This initiates the AI Composer with the prompt already written and the first generation beginning immediately. Because you typed the prompt inline rather than in a separate modal, the entire draft-to-send workflow (typing the prompt, generating, reviewing, inserting) takes under 30 seconds for a well-prepared prompt. Compare this to writing the same message manually — 5-10 minutes for a complex sprint message — and the time savings are significant.

Chaining /ai with Other Commands

/ai cannot be chained with other commands in a single command string — it must be the only command in the message composer. However, you can use /ai after a /remind to address both communication needs sequentially: first set the reminder with /remind, then open a new composer line and use /ai to draft the related team announcement. These two commands together handle the full workflow of communicating and confirming a time-sensitive commitment.

The /search command opens a filtered message search modal that searches the complete message history accessible to you (all public channels plus private channels and DMs you are a member of). For agencies managing six or more clients across multiple channels, /search is the fastest way to locate specific information without scrolling through channel history.

Syntax

/search [query] [optional filters]

Available filters (append after the main query): in:#[channel] to search within a specific channel, from:@[member] to filter by author, after:[date] and before:[date] to restrict by time range. Example: /search Lapron backlinks in:#client-lapron after:april-1. Filters can be combined: /search site audit from:@omar after:march-15 before:april-1.

Search Query Best Practices

Search works best with distinctive, specific terms from the message you are looking for. Use client names, task names, specific metrics, and proper nouns. Avoid common words that will appear in many messages ("meeting," "update," "team"). For messages that contain links, search for the domain or service name rather than the URL: "Drive" to find Google Drive links, "Lapron" to find all messages mentioning the client by name.

When /search Is Most Valuable

The four scenarios where /search saves the most time: finding a specific client decision made in a channel message weeks ago (client channel search with date range), locating a specific file link shared in a channel (search for the file name or the tool it relates to), finding previous communications from a specific agent about a topic (from: filter combined with a topic keyword), and verifying whether a specific topic has been discussed before creating a new message about it (search to avoid duplicating information already in the channel history).

The four channel management commands — /pin, /invite, /archive, and the notification commands @here and @channel — handle the most common channel administration actions from the message composer without navigating to channel settings.

/pin — Pin a Message to the Channel

/pin [message link] pins the referenced message to the current channel. To get a message link: hover over the message, click the three-dot menu, and select Copy Link. Paste the link after /pin and press Enter. Alternatively, hover over any message and click the three-dot menu, then select Pin to Channel without needing the /pin command. The /pin command is most useful when you want to pin a message you just sent without navigating back to it in the feed.

/invite — Add a Member to a Channel

/invite @[member] to #[channel] adds a workspace member to the specified channel without navigating to the channel's settings panel. This is the fastest way to add someone to a client channel after a task reassignment, add a new team member to all relevant channels during onboarding, or add a specialist to a client channel for a specific technical discussion.

/archive — Archive the Current Channel

/archive in any channel triggers a confirmation prompt before archiving. Archiving requires Admin or channel manager permission. Archived channels retain their full message history but no longer appear in any member's sidebar. Use /archive when: a client engagement has ended and the client channel is no longer needed in the active workspace, a sprint-specific channel has served its purpose and the conversation is complete, or a temporary project channel has concluded.

@here and @channel — Notification Commands

These are not slash commands in the traditional sense but are available from the command palette and function as notification triggers. @here in a message sends a notification to all currently active members of the channel (those with Available or Deep Work status, excluding DND and Invisible). @channel sends a notification to all channel members regardless of status. Both commands appear in the slash command palette when you type / followed by "here" or "channel."

This section provides the slash command quick reference in table format, sorted by usage frequency for a typical SEO agency, along with the most common mistakes to avoid for each command.

Building a Slash Command Habit in Three Weeks

The most effective approach to integrating slash commands into daily workflow: start with one command per week for the first three weeks. Week 1: master /ai — use it for every message that takes more than two minutes to draft. Week 2: add /remind — set at least two reminders per day using the command instead of relying on memory. Week 3: add /status — update your status at the start and end of every focused work session. By week four, these three commands are automatic habits, and the remaining commands can be added opportunistically as specific use cases arise.