Skip to content

Weave AI Assistant ​

At a glance ​

LocationSidebar → Chats → Spun Concierge conversation → Weave tab (phone: More → Weave)
PlanAll plans, including the free tier
Related features5

Built-in AI assistant that can answer questions about Spun features, help with tasks, look up conversations, and provide suggestions. Accessible via the side panel or as a detached floating window. Supports streaming responses and uses live workspace tools - the same read layer that powers the Spun API/MCP surface (conversations, messages, contacts, labels, campaigns, tasks, projects, team, groups, calendar events, delivery status, follow-up queue, scheduled messages, business overview and signals, message stats, translation) - plus SQL analytics over your inbox data. The Chat / Labels / Both switch above the Weave chat decides what it reads: Both (the default) reads conversations and labels together, Chat reads only conversations and messages, Labels reads label data and message counts but never message content. In Labels mode the text of messages, the last message preview of a chat, the text of scheduled messages and contact notes are not available to Weave, in its chat tools or in its analytics queries, so a question about what someone wrote is declined with a note to set the switch to Chat or Both, while counts, dates, senders, labels and contact details still work. Weave can also submit, draft, and schedule WhatsApp messages: these NEVER send directly - every Weave-submitted send follows the organization's AI-send policy (Settings -> AI Assistant) and lands in the AI Sends approval queue for a human to approve or reject (draft-only mode saves durable drafts instead), even when the org allows autonomous sending for API keys. Approval cards show "via Weave (user name)". Weave can also file a bug report or feature request on the user's behalf: it gathers a short description, lets the user attach a screenshot, and files a support ticket - replies appear in the Tickets tab, and Weave can hand off to Human Support from the same card. Ask Weave to move a lead along your pipeline and it suggests the move rather than making it: only a forward move can be suggested, the suggestion waits with the reason Weave gave until a person approves it, and moving a lead back to an earlier stage is done by hand on the board. Ask Weave to remind people in a group who have not sent a voice note (or any message) by a set time and it explains the group check-in rule and offers to create it with a confirmation button (workspace managers only): it finds the group by name and asks which one when several match. The rule never sends on its own - every reminder waits in Approvals - private reminders only reach members who already have a private chat with your number, and a member whose number is hidden can only be reached by a reminder posted in the group. Other actions (labels, chat operations, navigation) always show a confirmation button before anything changes. If the organization disables AI/MCP access in Settings -> AI Assistant, Weave keeps working with its built-in analytics only and cannot send, draft, or schedule messages, or file tickets. In the Human Support conversation a photo opens the image editor before it is sent, with any caption placed in the message box, and help content that only applies to WhatsApp is left out in a workspace without WhatsApp. The Weave tab is available to every member of a shared inbox, while the Human Support and Tickets tabs appear only for the owner and for members whose share has the Human Support checkbox on. When Spun support has written and you have not read it yet, the Human Support tab shows the number of unread messages (99+ when there are more), and the badge clears when you open that tab. In WhatsApp groups Weave knows who sent each message (the sender's number and the matching contact name) and can list a group's members, so it can count activity per employee or per member across groups; the organization's privacy setting for Weave can hide the numbers. When Weave reports a response rate or unanswered chats, a message counts as a reply when it is sent from your connected number or written in the chat by one of your own people: team members' WhatsApp numbers, contacts with a staff label (a label named exactly Staff, Employees or Team members, or your full business name followed by team, staff or employees, for example "Arkan Real Estate team", which is the label Weave uses when it saves a pasted staff list; a single word of the name such as "Arkan team", and labels such as "Travel agents" or "Team leads", are never treated as staff), or an employee list you confirm in the Weave session, written as "Employees:" followed only by the phone numbers, with no names or any other words (a list that also has names or instructions does not count; to count named staff, let Weave save them as contacts with the team label). It then reports both figures, "sent from this number" and "replies by your team". If none of these are known, Weave calls the figure "sent from this number" and never a response rate, so a team that answers groups from their own phones is not reported as 0%. For per-employee questions (how many messages each employee wrote, how fast each one answered customers) Weave reads one staff activity report covering up to 92 days: messages per team number, groups active in, first and last message, median response time and the share of requests answered within 1 hour, where a request is a group message from anyone outside the team, its response is the next team message in that group (counted up to 24 hours), and a message within 10 minutes of a message from the team counts as a reply to the team, not a new request. For per-group questions (which groups are busiest, which have the most requests still waiting, who writes most in each group) Weave reads one group activity report over the same rules: per group, busiest first, the messages, messages per day, messages from people outside the team, team replies, the five most active members, requests with no team reply within an hour (or a time you name) and the median response time, plus totals across all groups; when no team numbers are known it reports only what was sent from this number. A member whose number WhatsApp hides is listed as a hidden-number member with no number, usually under the profile name they set in WhatsApp, and is still counted and labelled in every report, never silently dropped. Once that person's own chat is linked to a contact from its "Not identified yet" card in the contact panel, Weave uses the contact's name for them in every group report, past messages included. Weave can also answer voice-note questions for a chat or group ("who left voice notes in the sales group today and what did they say?"): it lists each voice note with the sender, the sender's WhatsApp profile name, the length and the transcript, and summarises them per sender; a note whose transcript is still being prepared or failed is reported as such, and only true voice notes count, not audio files sent as attachments. The time range picker at the top of the Weave tab decides how far back Weave looks: 24h (the default), 3d, Week, Month, All, or Custom (pick a start and end date). Weave can only see messages Spun holds, which means everything since the WhatsApp number was linked to Spun plus the recent history WhatsApp handed over at link time, so All never reaches older messages than that. Weave reports times in the timezone of the device you are using. When Weave offers to remember a goal or preference for the session, it shows a "Save this preference" button rather than asking you to type a code. Step-by-step help for group analysis (saving your staff list as contacts, the time range, saving a prompt to run again) is the guide Analyze Your WhatsApp Group Chats (docs.spun.com/guides/analyze-group-chats), whose Voice notes section covers voice-note questions. To run the same group analysis from ChatGPT, Claude or another connected AI (who wrote each group message, hidden-number members, the monthly call allowance), see Connect ChatGPT, Claude or another AI assistant to Spun (docs.spun.com/guides/connect-ai-assistants-mcp). Step-by-step help for check-in rules (creating a rule, the Check now dry run, approving reminders in Approvals, the Check-ins today dashboard card) is Check-in Rules (docs.spun.com/features/check-in-rules). A manager can also ask Weave to link a hidden-number group member they recognize to the right contact (for example "the member shown as ~Layla in the Reservations Review group is Layla Haddad"): Weave proposes the link, the manager confirms it, the contact must already exist, and the link can be undone from the contact panel. Weave proposes this link only when the user names both the member and the contact, and nothing changes until the link is confirmed. While Weave is working, one progress bubble at the bottom of the chat starts with "Working..." and the number of tool calls so far, followed by the steps it is taking, and a Stop button appears next to the message box: Stop ends the run, keeps the part of the answer that already arrived (marked Stopped), and drops every message waiting in the queue. If a long question uses up all of Weave's steps before it has an answer, Weave answers from what it already found and says plainly what it could not check. Sending just "stop", "wait" or "cancel" (or the same word in Hebrew or Arabic) while Weave is working does the same as Stop; a longer message such as "wait for the report" is an ordinary message. Messages typed while Weave is working wait in a queue and are sent one at a time when the current answer finishes. A queued message identical to the question still running, or to one sent in the last 3 minutes that has not been answered yet, is not sent again: the queue marks it "already running". AI quality: in the Weave tab, open the Weave controls (the pill next to the time range) to choose Standard or Advanced. Advanced is the default and gives deeper analysis while using more tokens. Standard is faster and uses fewer tokens. The choice is remembered per browser. Do not quote model names or prices, they change. After Weave answers a question about your chats that it can repeat on a schedule (for example "what did customers ask in the sales group today?"), it may offer "Want this every morning?" with an "Every morning at 08:00" button. Confirming saves the question as a paused workflow that goes into your Daily Summary; nothing runs until you open Workflows and tap Resume. Weave offers this at most once per question in a session, never after a SQL analytics answer or a staff or group activity report, and never when the same question with the same chats is already saved. If your plan has no free workflow slot, the card says so and keeps the paused workflow for later.

How to use ​

  1. Open Weave: click Chats in the sidebar, which opens the Spun Concierge conversation (also the row at the top of the All tab of the chat list), then pick its Weave tab (next to Human Support and Tickets); on a phone, tap Weave in the More menu. While that conversation is open, the panel button in its header (or Ctrl/Cmd+E) opens Weave as a side panel, and Weave opens by itself as a floating window next to Automations, Autopilot, AI Chatbot and Auto Reply. There is no keyboard shortcut that opens Weave from anywhere else (Ctrl/Cmd+J does nothing).
  2. Choose the time range at the top (24h, 3d, Week, Month, All, Custom). Weave only sees messages Spun holds, everything since the WhatsApp number was linked plus the recent history WhatsApp handed over at link time, so All never reaches older messages.
  3. Type your question or request.
  4. Weave will stream a response, sometimes using tools to search your inbox data.
  5. Use the retry button to re-ask with a smarter model if the first answer is unsatisfying.
  6. To report a bug or request a feature, just describe it - Weave will offer to file a ticket, optionally with a screenshot attached.
  7. To stop a long answer, click the Stop button next to the message box (or send just "stop", "wait" or "cancel"): the partial answer stays and queued messages are dropped.

FAQ ​

  • How do I use Weave?
  • What can the AI assistant do?
  • Where is the AI chat?
  • How do I ask Weave a question?
  • Can I report a bug or request a feature through Weave?
  • Can Weave move a lead to another stage?
  • Why did Weave only suggest the stage move instead of doing it?
  • Can Weave tell me who left voice notes in a group and what they said?
  • Which requests in our groups got no reply today?
  • How active was Omar in the groups this week?
  • Who is in the X group?
  • Can Weave remind people who did not send a voice note?
  • Who sent voice notes in the ops group today, and how long was each one?
  • Which members of a group did not send a voice note today?
  • Can Weave summarize a week of voice notes from one person?
  • How do I stop Weave while it is working?
  • Why did Weave not send my message again?
  • What does "already running" mean in the Weave queue?
  • Why does Weave say our response rate is 0% when my team answers from their own phones?
  • How do I open Weave?
  • Is there a keyboard shortcut for Weave?
  • How far back can Weave look?
  • Why does Weave not see my older messages?
Was this page helpful?

Spun Docs - the documentation for Spun, the WhatsApp team inbox by Spun Life LLC.