Nole in Slack 💬

Nole doesn't wait for an invite — say hi and it's there. Three ways in:

• Drop it in a channel: /invite @Nole, or just start typing @Nole in any public channel — it joins itself and quietly catches up on recent context before answering.
• DM it directly: open a DM and talk to it like a teammate. No @ needed in there.
• Two speaking styles: @Nole your question in a channel/thread, or the /nole your question slash command (only you see the command typed; the answer posts for everyone).

That's it. No setup screens, no config — Nole's already read the room by the time it replies.

Plain English in, a grounded answer with evidence out:

• @Nole what deals closed this week?
• /nole how are we doing on support volume?
• @Nole who's our top closer this quarter?
• @Nole why did support tickets spike on Tuesday?

Every answer comes with its receipts attached — the deal, the ticket, the Slack thread it's grounded in. Want the full company snapshot instead of one question? Just say "deep brief" — Nole fans out ~21 parallel queries across every domain (sales, support, product, revenue, hiring…) and hands you back one synthesized read.

Nole isn't one voice — it's a team of 11 named specialists, each living in their own domain. @-mention one by name (first name, handle, or display name all work) and your question routes straight to them:

• Alexa — Growth. Where your traffic comes from and which channels actually convert.
• Joe — Sales. Pipeline health, win rate, and what the field is asking for.
• Maya — Marketing. Reviews the copy you actually send.
• Sam — Customer Success. Who's at risk of churning and who's ready to expand.
• Priya — Product. What customers keep asking for, and what's breaking.
• Raghav — GTM. Lead funnel health, dark pipeline, and whether campaigns are landing.
• Gyanchand — Data Nerd. Hidden connections your dashboards don't show.
• Nick — RevOps. MRR movement, expansion vs. contraction, revenue leaks.
• Chris — Engineering. Bug backlog, release velocity, support-to-eng escalations.
• Neeti — People. Hiring pipeline, candidate briefs, interview prep, culture fit.
• Zara — Solutions Engineering. What's possible with our products — APIs, Zapier, integrations we don't even have yet. Ask her anytime.

Forgot the lineup? Just ask: /nole experts or @Nole who can help? pulls up the full roster on demand.

Some questions don't belong to one desk. Mention two experts and Nole gets them both to weigh in:

• @Nole @Joe and @Maya weigh in on Q3
• @Nole @Joe why did we lose Acme? (single expert, straight answer)

Two clearly-relevant experts get a joint answer; anything bigger, ask for a deep brief instead.

No time given, just a link, right now:

• @Nole meet
• /nole create a Google Meet link

Give it a name and a time, and Nole drafts the calendar invite — you get a Send button to confirm before anything actually goes out:

• @Nole set up a meeting with Rohan at 12:30pm for 30 minutes
• @Nole meeting with Kavya tomorrow at 12pm about the roadmap
• /nole schedule a call with the design team Thursday at 4pm for an hour

Times default to IST. Drop an agenda right in the message ("… about the Q3 roadmap") and it lands in the invite description. Two teammates share a name? Nole shows you a quick picker instead of guessing.

Heads up: Nole matches names against your teammates' accounts. If it comes back empty-handed, skip to "When Nole draws a blank" below.

Read-only, no surprises:

• @Nole what's on my calendar today?
• @Nole am I free at 3pm?
• @Nole when's my next meeting?

• Spin up a doc: @Nole create a doc titled Q3 Plan
• Share a file: @Nole share the roadmap with Priya — you'll confirm before anything actually goes out.

Stuck on how Nole itself works (not your data — the product)? There's a shortcut just for that:

• /nole help how do I hire an agent?
• /nole help where do I find Discoveries?

This routes to Nole's own support brain — the same one behind the Help Center's chat widget.

See a great message worth remembering? React to it with a bookmark-style emoji (📌 or 🔖) and Nole quietly files that message — and its whole thread — into its knowledge base. Next time it's relevant, Nole already knows.

Booking a meeting means matching a name to a real account, and Nole can only match people it actually knows about. If it comes back with "couldn't find so-and-so":

• Try their exact name as it shows in Slack, or @-mention them directly in a normal message (mentions carry their exact identity — no guessing needed).
• Double-check they're actually in your Slack workspace.
• Still stuck on someone who clearly exists? Flag it — that's useful signal, not user error.

(True story: someone hit exactly this with a real teammate, we dug in, found the gap, and fixed it. If you hit a wall, tell us — that's how Nole gets sharper.)