> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spinnable.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Communication Channels
> Learn how your workers communicate with you and your team across email, WhatsApp, Slack, and the Spinnable interface
Your Spinnable workers aren't locked into a single chat interface. They meet you where you already work — **email, WhatsApp, Slack, or the Spinnable interface**. This is one of the biggest differences between Spinnable and traditional AI tools.
Think of it like hiring a human employee: they have a desk phone (Spinnable interface), email, Slack, and a mobile number (WhatsApp). They can handle conversations on all of them, simultaneously.
## Available Channels
Your worker's primary workspace — always available
Workers have their own email addresses
Message workers on the go
Collaborate in your team workspace
***
## Spinnable Interface
The **Spinnable interface** is your worker's primary workspace. This is where you:
* Start new conversations
* Review past conversations
* Monitor worker activity
* Manage worker settings and knowledge
* Give structured feedback
### When to use the Spinnable interface
* **Complex instructions** or training sessions
* **Reviewing work** and providing detailed feedback
* **Checking worker memories** or knowledge base
* **Managing permissions** and tool access
* **Bulk operations** that need your full attention
**Pro tip:** The Spinnable interface gives you the fullest picture of your worker's activities and capabilities. Use it for onboarding and major configuration changes.
***
## Email
Every worker comes with **their own Spinnable email address** (e.g., `alice.harris@spinnable.app`). This email works out-of-the-box with **no setup required** — your worker automatically receives all emails sent to their address.
### Two types of email capabilities
**What it does:**
* ✅ Worker receives ALL emails sent to their @spinnable.app address
* ✅ Worker can reply to emails
* ✅ Works immediately, no configuration needed
* ✅ Perfect for most use cases
**Example:** Forward customer inquiries to `alice@spinnable.app`, and Alice will respond automatically.
**What they enable:**
* ✅ Worker can send emails FROM your personal/company email address
* ❌ Worker does NOT automatically receive emails to your inbox
* ⚠️ Requires Read Email tool + explicit instruction to check inbox
* ⚠️ Replies to those emails go to YOUR inbox, not the worker's
**When to use:** You want emails to look like they're coming from you (`you@yourcompany.com`) instead of the worker's Spinnable address.
**Common misconception:** Connecting Gmail/Outlook as a tool does NOT make your worker automatically respond to your inbox. You'll need to:
1. Add the **Read Email** tool
2. Explicitly instruct the worker to check your inbox
3. Understand that replies will land in YOUR inbox
### Email threading behavior
* **Spinnable treats each email as a new conversation**, but your worker sees the full email thread history for context
* If someone replies to your worker's email, the worker understands the conversation flow
* Each thread maintains its own context within the Spinnable system
### Custom worker email address
**Standard and Premium plan** users can give their worker a custom email address (e.g., `support@yourcompany.com` or `valeria@yourcompany.com`) so that all email sent and received by that worker appears under your own domain — no Gmail/Outlook integration required.
Custom worker email is available on the **Standard plan and above**. See the [Using a Corporate Email](/guides/corporate-email) guide for full setup details.
If you are on the Basic plan or prefer to use an existing Gmail or Outlook account, you can also configure your worker to send from that address using the Gmail/Outlook tools. Here's how that flow works:
1. Connect Gmail/Outlook tool to your worker
2. Tell the worker to send emails from the connected email using the tool (e.g., `support@yourcompany.com`)
3. Recipients reply to that address
4. **Those replies go to YOUR inbox** (not the worker's Spinnable inbox)
5. You need to forward them to your worker's @spinnable.app address OR instruct the worker to monitor your inbox using the Read Email tool
### When to use email
* **Customer support** inquiries
* **Asynchronous communication** that doesn't need instant response
* **External stakeholders** who don't have access to your other tools
* **Formal communications** that need email trail
- **CC your worker** on relevant email threads to bring them into the loop
- **Use clear subject lines** — they help your worker categorize and prioritize
- **Forward emails** to your worker's address instead of copy-pasting (preserves threading)
- **Set expectations** in your worker's job policy about email response time and style
* **Assuming connecting Gmail/Outlook = automatic inbox monitoring.** Connecting Gmail or Outlook gives your worker the *ability* to read or send from that account, but it does NOT make the worker automatically monitor the inbox or always send from that address. You need explicit configuration for each. See the [Using a Corporate Email](/guides/corporate-email) guide for the full setup.
* Not forwarding full email threads (worker loses context)
* Forgetting to add the worker's email to your contacts (emails might go to spam)
* Sending time-sensitive requests via email instead of WhatsApp or Slack
***
## WhatsApp
Workers can communicate via **WhatsApp** using your account's configured phone number. This is perfect for on-the-go communication.
### Two types of WhatsApp setup
Before diving into setup, it's important to understand the two distinct WhatsApp modes. They serve different purposes and are **not interchangeable**.
**What it is:** A Spinnable-managed WhatsApp number shared across all your workers. It is set up and maintained entirely by Spinnable — you do not configure it, scan any QR code, or connect your own phone number.
* ✅ Works out-of-the-box, no setup required
* ✅ All workers accessible via a single number using `/commands`
* ✅ Maintained by Spinnable
* ❌ Cannot join WhatsApp groups
* ❌ Workers do not have individual WhatsApp identities
**This is the default for all accounts.** Most users never need anything beyond this.
**If the shared Spinnable number is temporarily unreliable**, wait a few hours and try again — do not attempt to reconnect, scan a QR code, or link your own number. Those actions apply to the **custom number** flow below and will not fix a temporary issue with the shared number. See [Troubleshooting WhatsApp](/troubleshooting#whatsapp-shared-number-temporarily-unreliable) for more.
**What it is:** An optional dedicated WhatsApp number you provide, linked to a single worker. This gives that worker their own WhatsApp identity.
* ✅ Worker has their own dedicated WhatsApp number
* ✅ Direct messaging without `/commands`
* ✅ Can join WhatsApp groups
* ⚠️ Requires a separate phone number and QR-code linking
* ⚠️ The worker takes over that WhatsApp account completely
**Only use this when you intentionally want a worker to have a dedicated WhatsApp presence.** It is not a fix for issues with the shared Spinnable number.
See the [Custom WhatsApp Number](/guides/custom-whatsapp-number) guide for setup instructions.
### Setup (shared Spinnable number)
WhatsApp setup is **account-level**, not per-worker. One phone number applies to all workers.
Click your profile avatar in the bottom-left corner of the sidebar, select **Settings**, and add your phone number under the **Profile** tab.
**Common issue:** Not setting up your phone number in your profile → worker can't recognize you as the manager when you message them.
Each worker has a unique **4-digit alphanumeric WhatsApp ID** (e.g., `A4B9`).
Find it in: **Worker → Settings tab**
Two ways to initiate contact:
**Option 1: Switch between workers**
* Message your configured WhatsApp number
* Type `/firstname` or `/firstname lastname` to switch to that worker
* Start your conversation
**Option 2: Direct access with WhatsApp ID**
* Message your Spinnable WhatsApp number
* Type `/WorkerWhatsAppID` (e.g., `/A4B9`)
* Worker responds immediately
**Other helpful commands:**
* `/help` — Get list of available commands
* `/list` — See all your workers and their IDs
### External users
Want someone outside your organization to message your worker via WhatsApp?
1. Ask your worker to send a WhatsApp message to the external contact
2. Contact receives message from your Spinnable WhatsApp number
3. They can reply directly — no special commands needed
**This is the simplest approach.** The worker establishes the connection.
1. Share your Spinnable WhatsApp number with the external contact
2. Give them the worker's WhatsApp ID (e.g., `A4B9`)
3. They message your number with `/A4B9`
4. Worker responds
**Note:** This requires sharing the worker's ID ahead of time.
### File Support
Workers can send and receive files through WhatsApp—documents, images, PDFs, and more.
**Supported files:**
* Documents (PDF, DOCX, XLSX, TXT, CSV)
* Images
* Spreadsheets and data files
* Whatsapp Voice notes
**File size limit:** 16 MB per file
**How to use:**
* Attach files to your WhatsApp messages as normal
* Workers download and process file contents automatically
* Ask your worker to create and send files back to you
Reference files by name in your messages: *"Review the contract.pdf I just sent"*
### WhatsApp Groups
**Requires a custom WhatsApp number.** Your worker needs a [dedicated WhatsApp number](/guides/custom-whatsapp-number) to participate in group chats. Workers using the shared Spinnable number cannot join groups.
**How it works:**
* Add your worker's custom WhatsApp number to any WhatsApp group
* The worker reads every message in the group and **decides autonomously** whether to respond
* When relevant, the worker jumps in to answer questions, take action, or provide information — just like a human teammate
* The worker maintains separate context for each group conversation
**AI Capacity usage:** Workers in WhatsApp groups are exposed to all messages in the group, which can increase AI capacity consumption. Start with small, focused groups to keep usage manageable.
**Best starting point:** Try adding your worker to a small, focused group — like a project team or customer support channel — before scaling to larger groups.
### When to use WhatsApp
* **Quick questions** while away from your desk
* **Mobile-first workflows** (field workers, traveling, etc.)
* **Personal, informal communication** style
- **Set up your phone number first** before trying to message workers
- **Switch workers explicitly** using `/firstname` to avoid confusion
- **Share worker WhatsApp IDs** with external contacts who need access
***
## Slack
**Slack billing impact:** Spinnable workers join your Slack workspace as real members — not as Slack bots. If you're on a **paid Slack plan**, each worker will count as an additional paid seat on your billing.
Workers can join your **Slack workspace** and participate in channels and threads, just like human teammates.
### Setup (takes \~10 minutes)
**Prefer a video walkthrough?** Watch this step-by-step Loom recording of the entire process:
Invite your worker just like you would invite any human colleague.
Navigate to your workspace and select "Invite people to \". Add your worker's email (visible in the worker header, or just ask them) and send.
**Important: Don't allow auto-join for the @getspinnable.ai domain.** Every Spinnable worker uses this email domain, so enabling auto-join would let any worker — not just yours — join your workspace. Always use individual invites.
Your worker handles the entire setup process autonomously — no action needed from you. Here's what happens behind the scenes:
1. **Your worker emails you** to let you know they've received the invitation and are starting the setup process
2. **You'll see a Slack notification** that the worker has accepted the invite — but they're not done yet
3. **Your worker emails you again** once everything is fully configured
The whole process typically takes around **10 minutes**. Just be patient — your worker is handling sign-up, verification, and app installation all on their own.
**How to confirm setup is complete:** Once fully set up, your worker will automatically update their **profile picture** in Slack. That's your visual confirmation that they're ready to go.
**Don't message your worker right after the Slack invite notification.** The invite acceptance is only the first step — the worker still needs to finish installing the Spinnable app. Wait for the confirmation email before trying to interact with them on Slack.
Once setup is complete, add your worker to relevant Slack channels like any other team member.
### How workers behave in Slack
* Workers must be **@mentioned** to respond
* They read **only the message where they're mentioned**
* **Exception:** In threads, workers read the **full thread** for context.
**Example:**
* You post: "Hey @alice, can you draft a response to this customer complaint?"
* Alice reads only that message (unless it's in a thread)
* Workers **always reply in threads** by default
* This keeps channels clean and organized
* They maintain conversation context within each thread
* Workers can participate in **public channels**
* Workers can participate in **private channels** (if invited)
* Workers can receive **direct messages**
* They behave the same way in all contexts
### Common mistakes
**Don't do this:**
* ❌ Forgetting to @mention the worker (they won't see the message)
* ❌ Trying to add Slack as a "tool" (Slack is a **channel**, not a tool)
* ❌ Expecting workers to monitor all channel messages (they only read @mentions)
* ❌ Messaging the worker before setup is fully complete (wait for the confirmation email)
### When to use Slack
* **Team collaboration** where workers participate alongside humans
* **Real-time discussions** that benefit from threading
* **Channel-based workflows** (e.g., #customer-support, #content-review)
* **Transparent communication** where the whole team sees worker contributions
- **@mention workers explicitly** to trigger responses
- **Use threads** for multi-turn conversations
- **Set channel etiquette** in worker's job policy (e.g., "Only respond to messages in #support")
- **Introduce your worker** to the team when they join a channel
***
## Voice Calls
Talk to your workers by voice for real-time collaboration. Click the **Call** button on any worker's page to start a voice conversation.
Voice calls are currently in **beta**. Workers can use tools and complete tasks during calls, but are slightly less reliable than text-based communication.
### When to use voice
* **Real-time discussions** that benefit from back-and-forth dialogue
* **Hands-free work** when multitasking or away from keyboard
* **Quick questions** that don't need written documentation
* **Brainstorming** where you want to think out loud
***
## Multi-Channel Operations
Here's what happens when the same worker operates on multiple channels:
### Simultaneous operation
Your worker can handle conversations on **all channels at the same time**:
* Responding to emails
* Chatting on WhatsApp
* Participating in Slack threads
* Answering questions on the Spinnable interface
**They don't get confused.** Each conversation is tracked separately.
### Context and memory
**How it works:**
* Each channel maintains **separate conversation threads**
* There's **no automatic context sharing** between channels
* Your worker's **overall memory is unified** (they remember who you are, your preferences, past work)
* Channel-specific preferences can be set through feedback
**Example scenario:**
* You email your worker: "Draft a blog post about AI"
* Later, you message on WhatsApp: "How's that blog post going?"
* The worker WON'T automatically connect these — they're separate conversations
* **Solution:** Reference the email or provide context in your WhatsApp message
### Tone adaptation
Workers **automatically adjust their communication style** based on the channel:
* **Email:** More formal, structured
* **WhatsApp:** Casual, concise
* **Slack:** Collaborative, team-oriented
* **Spinnable interface:** Professional, detailed
You can reinforce this by giving feedback like: "Be more casual on WhatsApp" or "Keep Slack responses brief and actionable."
### Memory question
**Q: "If I teach my worker something on email, will they remember it on WhatsApp?"**
**A:** Yes. Your worker's memory is unified across all channels. However, whether they apply that learning on a specific channel depends on how you instruct them.
For example:
* General instruction: "Always use bullet points" → applies everywhere
* Channel-specific: "Use bullet points in emails only" → applies to email channel
***
## Security & Access Control
You can control who can contact your workers via email and WhatsApp.
### Blocking external users
Go to **Worker → Settings**
Toggle settings to:
* Block external emails
* Block external WhatsApp contacts
Only users within your Spinnable account will be able to reach the worker.
For comprehensive security guidance, see our [Security Best Practices](/guides/security-best-practices) guide.
***
## Next Steps
Give your workers access to Gmail, Slack, and other integrations
Learn how to organize and scale your team of workers
Keep your workers and data secure
Train your workers through conversation and feedback