WhatsApp CRM
Now liveYour WhatsApp conversations, as a sales pipeline.
A kanban board that moves a customer from New lead to Won without leaving the inbox where the conversation already lives. The cards are your contacts, and the stages are ordinary Spun labels, so nothing you already built stops working.
The pipeline is switched on for every Spun account. Open the board from your inbox and your six default stages are already seeded, in your language, waiting for the first card.
Starting takes nothing
There is no import, no setup project and no second tool. The board is on, the stages are seeded, and the contacts are the ones you already talk to.
It is already inside your inbox
The board opens next to the conversations it is about. There is no second app to keep open, no export, and no sync to keep running between two systems.
Six stages are waiting on the first open
A default pipeline is seeded for you in English and Hebrew, with a Comm Plan cadence per stage. Rename, recolor and reorder it until it matches how you actually sell.
Nothing to import
The cards are the contacts you already have and the stages are ordinary Spun labels, so there is no data migration to plan and nothing to rebuild in a new vocabulary.
The board
Columns are your stages. Cards are your contacts.
Not your chats, and not your tasks. That distinction is the whole design: a person moves through your funnel once, however many conversations you have with them.
A card is a person, not a thread
Cards are contacts. If the same customer wrote to you three times from two numbers you saved, they are still one card in one stage, instead of three half-tracked conversations drifting apart.
The conversation is one click away
The board is a view over your inbox, not a separate system you keep in sync. Open the chat from the card and answer where you always answer.
Time in stage, and overdue, are different numbers
How long a lead has sat in this stage is one thing. Whether your Comm Plan for that stage is overdue is another. The design keeps them separate on purpose, because a lead can be fresh in a stage and still owed a reply.
Stage is not ownership
Which stage a contact is in, who owns them, and who owes the next message are three separate facts. Squashing them into one field is what makes most simple CRMs lie to you.
A look at the shape of it
Illustrations, not screenshots
These are simplified drawings in the site design language rather than pictures of the running product. Real screenshots of the live board follow shortly.
Stages
Stages are just labels, so your setup keeps working
A stage is an ordinary Spun label that lives in one mutually exclusive group. A contact is therefore always in exactly one stage, and every filter, search and automation you already built on labels keeps doing its job.
One stage at a time, enforced
The stage labels sit in one mutually exclusive group, so moving a contact into Qualified takes them out of Contacted in the same operation. There is no drifting into two stages at once.
Six stages to start, in both languages
New lead, Contacted, Qualified, Proposal, Won and Lost, seeded for you with a Comm Plan cadence per stage, in English and Hebrew. Rename them, recolor them, reorder them, add your own.
Your existing label work carries over
Because a stage is a label, your saved filters, searches and label automations already work on pipeline stages. Nothing has to be rebuilt in a new vocabulary.
Stages cannot be deleted out from under history
A stage can be archived once it is empty, and the two closing stages stay put. History that points at a stage can never end up pointing at nothing.
Getting on the board
New leads put themselves on the board
The point of a pipeline is that nothing falls out of it. Two things place a contact in your first stage without anyone remembering to do it.
The first message from a new contact
When somebody new writes to you in a one to one chat, they land in your first stage by themselves. That is the moment a lead is most often lost, and it does not need a human to notice it.
Saving a contact who already wrote
Save or link a contact from a chat that already has an inbound message and they enter the same way. Both routes lead to the same first stage.
On by default for new accounts, your call for existing ones
New organizations get automatic entry switched on. If you have been with us a while, you get asked once rather than waking up to a board full of history.
An unsaved number is not a dead end
A number you never saved cannot be a card, because a card is a contact. Save and stage turns that unknown number into a contact and puts it on the board in one confirm.
Safety
Built for several people touching the same board
The move service is where this is enforced. It is one path, and every surface goes through it: the board, the chat, the contact panel and the phone.
Two people, one card, no corruption
A move says which stage it expects the contact to be in. If a colleague got there first, the second move is refused and told so, rather than quietly overwriting what they did.
A batch tells you about every contact in it
Move a group at once and you get a result per contact. The ones that worked commit; the ones that could not are named with the reason, instead of the whole batch failing or silently half applying.
Every move is on the record
Who moved it, when, from where to where, and whether it was a person, a rule or the AI. The history is append-only and written in the same transaction as the move, so it cannot disagree with the board.
A lead who comes back is a new run, not a broken number
Reaching Won or Lost closes that pass through the pipeline. If the customer writes again months later and re-enters, it counts as a fresh pass, so a returning lead can never push a conversion rate above one hundred percent.
On arrival
What happens when a lead reaches a stage
Work that fires on arrival instead of on your memory. Spun does not message the customer on a stage change, which is a deliberate decision rather than a gap, and an undo runs none of these.
Create a follow-up task
A task on your tasks board, so the next step is a job somebody owns rather than something somebody has to remember.
Set or clear a reminder
An alarm when a stage means come back to this, and clearing one when a stage means it is handled.
Add or remove an ordinary label
A second label alongside the stage, which keeps your existing label filters useful instead of competing with them.
Reset the Comm Plan clock
A new stage usually means a new cadence, so the overdue flag measures the stage the lead is in now.
Notify the owner
The person who owns the lead hears that it moved, without anybody having to tell them.
Call your own signed webhook
Your endpoint, HMAC-signed, so your own systems hear about the move and can do whatever they do.
Day to day
The rest of what the board does
The smaller things, all of them live today, that decide whether a board is pleasant to work or a chore.
- An undo on every move. Eight seconds to take a move back, or Ctrl and Z, including a whole batch in one go.
- The Lost reason before the move, not after. Dropping a card on a closing stage asks why first, and cancelling means nothing moved at all.
- Setting a stage without opening the board. From the chat itself or the contact panel, which also shows that contact recent stage changes.
- Stage chips in your filter bar. Filter the inbox by stage from the same bar you already filter by label.
- A column for contacts not on the board yet. A bounded Unstaged column of recently active contacts, so a full history never floods the view.
- A dialog for managing stages. Add, reorder and archive an empty stage. Deleting a stage is not offered at all, so history can never point at nothing.
- Two card densities. A compact card for scanning a long column, and a fuller one when you want the detail.
- A board that works on a phone. Columns snap one at a time as you swipe, and a Move to menu stays visible on touch instead of asking you to drag.
Deliberately not doing this
What the pipeline never does
These are decisions, not a backlog. They are the reason the feature is safe to run on the number your business depends on.
Moving a card never messages the customer
Automatic sending on a drag is not a missing feature, it is a rejected one. A slip of the hand that fires a message to a customer is exactly how a WhatsApp number gets limited or banned, and no board is worth that risk.
Nothing sends from somebody else on your behalf
Messages go out from your number, by your action. That stays true no matter who else can see a board.
No two way sync with another CRM, and no forecasting
The pipeline is a view of your conversations, not a mirror of another system, and it does not put a number on your deals or predict a quarter. Those are separate products pretending to be a feature.
Two boards, two jobs
This board is not the tasks board
Spun has two kanban boards and they are deliberately separate at every level, including the data.
This board moves people
Cards are contacts and the columns are the stages of your funnel. The question it answers is where each customer stands.
The tasks board moves work
Cards are work items your team assigns and finishes, with their own columns, and a task can even go to somebody who has no Spun account at all.
Later
Where the pipeline is going
Directions we intend to take this, described as what you would get rather than how it would work. None of this is built, none of it is dated, and none of it is promised with a signup.
Boards other people can see
A partner, a secretary or a client seeing the slice of the pipeline that concerns them, without getting your inbox.
Pipelines that arrive ready for your trade
A starting board that already looks like how your profession sells, plus a library of common stage setups to borrow from.
Knowing where leads leak
Reporting that answers how many made it through, how long each stage really takes, and which stage quietly loses people.
Frequently asked questions
Can I use this today?
Yes. The pipeline is switched on for Spun accounts: open the board from your inbox and a default set of stages is already seeded for you, in English and Hebrew. Nothing has to be imported first.
Do I need another CRM alongside it?
That is the point of building it this way. The pipeline is a view over the conversations and contacts you already have in Spun, so the stage a customer is in lives next to the thread where you talk to them, rather than in a second system you have to keep in step by hand.
Are the cards my chats or my contacts?
Contacts, always. A chat is just the conversation you happen to be having with that person, and one contact can have more than one. Making cards contacts is what stops the same customer appearing in three places in three stages.
What happens to numbers I have not saved?
An unsaved number cannot be a card, because a card is a contact. Instead of hiding it, the chat offers to save and stage it: one confirm turns that unknown number into a contact and puts it on the board at the same time.
Does moving a card message the customer?
No, and that is deliberate rather than unfinished. Automatic sending on a drag was rejected in the design, because one mis-drop firing a message to a customer is exactly how a WhatsApp number gets limited or banned. Messages leave when you send them.
Can two people work the board at once?
Yes, and it is built for that. Each move states which stage it expects the contact to be in, so if a colleague already moved that card, your move is refused and you are told, instead of one of you silently overwriting the other.
What happens to a lead who writes again after being marked Lost?
They can come back onto the board, and the system counts it as a fresh pass through the pipeline rather than editing the old one. That is what keeps later numbers honest: a returning lead cannot push a conversion rate above one hundred percent.
Is it in Hebrew?
Yes. The default stages are seeded in English and Hebrew, and Spun runs right to left throughout, the same as the rest of the product.
Does it work on my phone?
Yes. On a phone the columns snap one at a time as you swipe, and a Move to menu stays visible on touch instead of asking you to drag a card across a small screen. Spun runs in the browser and as an iOS and Android app.
Which plan is it on?
The pipeline is part of Spun rather than a separate product to buy. See the pricing page for what plans include today, because a summary here would drift out of date.
More on what Spun does: Features, Pricing, Tasks, and Privacy and security.
Put your leads on the board
Open Spun, open the board, and the six stages are already there. Every conversation you already have stays exactly where it is.
Open your pipelineThe pipeline is part of Spun itself, not a separate product to buy. See the pricing page for what plans include.