What Sales is for

Your agent answers whoever writes in. Sales handles everything after that: the person who asked about a price and never came back, the cart left halfway, the customer who has not ordered in months, and the businesses that would buy from you but have never heard of you. It covers both sides of selling: winning the customers you have, and going out to find the ones you don't.

Leads. One board of everyone who wrote to your agent and is not a customer yet, warmest first, with what you owe each of them and by when.
Journeys. Sequences of messages on WhatsApp, email and the other channels your agent answers on, that go out on their own at the right moment: cart recovery, win-backs, reorders, renewals, a stalled B2B deal. They stop when the customer buys, and hand the chat to your agent when they answer.
The AI Sales Team. Four AI workers (an Analyst, a Prospector, an SDR and an Account Executive) who run your outbound pipeline, from working out who to sell to all the way to the close.
Segments, templates and Monitoring. Live customer groups, the WhatsApp templates journeys send, and a dashboard of which journeys, ads and segments actually make you money.

It fits a service business that gets enquiries on WhatsApp and has to call people back, an online store that wants carts and repeat orders followed up, and a B2B company that needs a pipeline of new accounts. The journeys and the sales team share the same customers, the same context and the same board, so nothing gets dropped between keeping a customer and winning a new one. You do not need a store to start: connect your channels and tools as you go, or begin with nothing but a list of customers.

Sales has no WhatsApp number of its own. It runs on one of your AssistantLabs agents. The agent's contacts are your leads, its channels send your journeys, and when a customer answers a journey message, the agent is the one who replies: it answers questions, checks stock and closes the sale on the same number. You can jump into the chat from your phone whenever you like.

Leads: everyone who wrote in, warmest first

The Leads board answers one question every morning: who should I call today? Everyone on it is a real person who wrote to your agent, with the conversation one click away.

You decide who is a lead. Pick the labels your agent puts on conversations that count as an enquiry, and the ones that never do (suppliers, partners, your own numbers, spam). Keep only people who actually wrote in, and hide paying customers. You can add more sources: a record type in your CRM (a sign-up, a form enquiry), the companies in your CRM (a churned customer you want back), and add someone by hand: the one who rang, came from a friend or you met in person.
Warmest first. Each lead is marked hot, warm, cooling or cold from what they did: when they last wrote, whether a meeting is booked or held, whether they keep not answering. A purchase always outranks a reply. Tap the mark to see exactly why. You set how fast a lead cools down.
Filters for the day. Call today, Overdue, They are waiting, Never called, Going cold and From an ad. A lead who came from one of your ads carries an “ad” badge, with the ad one tap away.
Leads by stage. The top of the board shows how many leads sit in each stage and points out where they are piling up, with a link straight to them.
One page per lead. What they said, in their own words; everything that happened to them across your apps; which journey messages they got and which step they are on; and their record from the CRM. Step to the previous or next lead without going back to the board.
Write to them from their page. While the 24-hour window is open, reply right there, and the page tells you how long you have left. Writing yourself quiets the agent on that conversation, so you never talk over each other.
Log a call in one tap. Buttons like “Called, no answer” record the call, move the stage and set the next step and its date together, so the board never shows half an update.
Work in bulk. Select several leads to push them to tomorrow or next week, move them to a stage, or give them an owner.

The stages and the buttons are yours to name. Each one can also set something off: move the lead, add a label, hand it to someone on the team, set a reminder, notify you, send the lead a WhatsApp message, send a booking link, start or stop a journey, or send the lead to your own system. A stage can also chase a lead that has sat in it untouched for too long. And a button can start a journey you build on the spot: pick an approved template, or take the one Sales suggests, which it submits to Meta for you, and pressing the button sends it.

Stops by default. When you log an outcome that closes a lead, like “not interested”, any journey still running on that person stops, without you setting anything up.

Once a day, at the time and on the days you pick, Sales sends you one message, on WhatsApp or Slack, with the leads you owe a call today and the next step for each. A quiet day stays quiet: nothing is sent when nothing is owed. If the 24-hour WhatsApp window with a lead has closed, you can send them an approved template straight from their page, or email them (see Marketing below).

Journeys: follow-ups that send themselves

A journey is a timed, branching path built on one timeline: waits, conditions, offers, carts, bookings and reminders, measured against a goal. Someone enters it, and each step happens at its time, on the branch their behaviour picks, until they buy, answer or reach the end.

Who enters. A segment from your Shopify store, a store event (a new order, a new customer, an abandoned checkout), a segment you built yourself, or a lead button or stage that starts it. For abandoned checkouts, Sales waits first and only enrolls the people who did not finish paying. A segment fed live keeps the journey filling as people arrive, and you can also run a live journey once on everyone already in its segment.

Messages. Write the text yourself, or let your agent write it at send time from what it knows about the customer. Personalize with their name, their order, their cart, and any product's name, price and link. A step can also send an approved template, a product card, or a link to a ready cart.
Carts the AI builds. A cart step can put together the cart for each customer: complete the set with items that go with what they bought, or build a bigger basket with the offer applied. Save a setup you like as a strategy and reuse it.
Waits and clock times. “Wait one day”, or “send at 10:00”.
Conditions. Branch on whether they replied, opened, clicked, bought, booked an appointment or unsubscribed.
Offers. A personal discount code, created in your Shopify store for that one customer, or a code you already have. You set the levers the AI may use and their limits, from the smallest nudge that converts to a balance of margin and conversion, and it picks the offer for each person inside them.
Wait for something to happen. Hold the journey until a paid order or a reply arrives.
Booking and reminders. Invite the customer to book, or put a to-do for you on the lead (“call in three days”).

Each journey has a goal, in your words, which tells the AI what it is trying to do, and an outcome you choose to measure it by: a purchase, a purchase with the discount, a sign-up, a course sign-up, or a happy customer.

When to stop. Tick “stop when they buy”, and choose what happens when they reply: hand the chat to your agent, or just stop. Someone who unsubscribes is always taken out.

The 24-hour window decides what can go out. WhatsApp lets you write freely for 24 hours after the customer's last message. Inside it, every step sends as written. Outside it, a step needs an approved template: a product card goes out as a template, a text step is skipped, and the ready-cart link only goes out while the chat is open. Email steps have no window.

Building and checking a journey happens on one screen. A live phone preview beside the timeline shows exactly what the customer will see. Messages respect your business hours: one that falls due at night waits for the next open time instead of being dropped. And before you switch a journey on, you can test it on test users: Sales looks them up in your store and shows which segments they are in, can change them in Shopify so they enter the segment for real, and then plays every message in order to their own phone, with the waits cut short, including the moment the agent would take over.

Not sure where to start? Open the Sales Agent panel at the top of the app and describe what you want, for example “win back customers who have not bought in a while”. It asks what it needs and builds the journey as a draft. It never switches anything on; you review it and launch it yourself.

The AI Sales Team: finding new customers

Journeys work the customers you already have. The Sales Team goes out and finds new ones. Four AI workers own your outbound pipeline and hand each lead from one to the next, so nobody falls through.

Analyst: Source. Point it at a group of your best customers. It reads the group, enriches what it knows from their websites, finds the traits they share and builds an ideal-customer profile, with how confident it is, that you reuse in every search.
Prospector: Prospect and Enrich. It takes the profile and goes looking: businesses across the web that match it, and the public Facebook groups where those customers gather. For each business it reads their website and business directories, finds the decision-maker and a real way to reach them, confirms the WhatsApp number, and shows where it found each detail. You approve the list before anyone is added.
SDR: Outreach and Qualify. Runs a multi-touch cadence until someone replies, works the reply, qualifies it and books the meeting.
Account Executive: Discovery, Demo, Proposal and Close. Runs the discovery meeting (the pain, the budget, the timeline, who decides), gives a demo tailored to what came out of it, sends the quote and handles the negotiation, then wins the deal or records why it slipped.

Everything sits on one pipeline board, from Prospect through Enrich, Outreach, Qualify, Discovery, Demo, Proposal and Close to Won, and prospects move across it as each worker advances them. You stay in charge: the workers do the legwork, and you approve, step in or take over whenever you want.

Groups are where it starts. A group is a named set of people, reused anywhere: a Shopify segment, a CRM segment that is re-read every time you send, a label, a purchase, a custom field, your agent's contacts, or a CSV you upload (extra columns are kept as custom fields). Build a profile from a group to find lookalikes, or move its people straight to outreach and attach a journey.

Segments, templates and results

The tools around the journeys: who they reach, what they are allowed to send, and whether they worked.

Customers. Your customers, grouped the way journeys need them: abandoned carts, VIPs, lapsed buyers, open opportunities. Segments are live, so their counts refresh on their own as customers move, and you point a journey at one in a click.
Segment Builder. Combine your agent's contacts (narrowed by channel, label, CRM segment, a field, a purchase or when they last wrote), a Shopify segment, a list you upload, or people a form or Zapier sends to a webhook. Leave people out, too. A segment fed by a webhook is live: people join the journey as they arrive.
Recommended segments. Right after you connect Shopify, Sales suggests segments based on your store. The ones you approve are created in Shopify, ready for a journey.
WhatsApp Template Builder. Design a template, preview it, and submit it to Meta for approval. These are the messages a journey can send outside the 24-hour window. The workspace's language decides the language of every template you submit. Add a header image by uploading it, pasting a link or picking a product photo from your store, and send yourself a test.
Monitoring. Which of your journeys, ads and segments actually make money. Revenue each journey earned, de-duplicated and reconciled with your Shopify store; customers in motion; conversion; compared with the previous period, and filtered by ad or segment.
Funnels, overlap and sources. Tap a journey to see its step-by-step funnel and where people drop off. A heat map shows which pairs of journeys work best together on the same customers, and a sources view shows the revenue each ad and source drove and the journey it feeds most.
Outcomes you can trust. Journey by journey, how many people reached the outcome you set, grouped by kind so sales and sign-ups are never added together, with how Sales knows: they used the journey's code, came through its link, bought within the window, or said so in the conversation. A journey with no outcome set says so instead of showing zero.

Templates sent outside the window are paid messages on WhatsApp. What WhatsApp charges, and what stays free explains the rates.

Works with your other apps

Sales does not keep its own copy of your customers. A lead is a contact of your agent, so whatever Sales writes about them shows up wherever that contact does. Here is what connects, app by app.

Agents

The biggest connection, and the one Sales cannot run without. Your agent's contacts are the lead board, its labels decide who is a lead, and journeys send through its WhatsApp and email using its approved templates. When a customer replies to a journey message, Sales hears about it and the agent carries the conversation, with the journey's goal in front of it so it knows why the customer was contacted. The agent also writes the AI steps of your journeys, picks the products, and can book a lead inside the chat. Channels are connected on the agent, in the Agents app, and every channel you add there is one more place your journeys can reach customers. The Agents app

Booking

Switch it on in Settings › Integrations › Booking, and Sales can use your diary. You can book a lead in while you are on the phone with them, add a booking step to a journey, and set any stage or button to send your booking page or let the agent book them inside the chat. Every appointment appears on the lead's timeline, and two funnel stages, “meeting booked” and “meeting held”, move on their own from the diary. Booking creates the appointment itself, so the calendar, the confirmation and the reminders work as usual. The Booking app

Helpdesk

A lead and a support customer are the same contact, so they share one history. Helpdesk tickets show on the lead's timeline next to your calls and journey messages, so you know about an open complaint before you ring someone about an upgrade. When a customer answers a journey with a problem rather than a buying question, the agent opens a ticket in Helpdesk and the journey steps aside until it is solved. Both apps answer from the same Shopify install, so order questions and order follow-ups read the same store. The Helpdesk app

CRM

Sales and the CRM share one customer record: every customer, conversation and deal lives in one place, and both sides read and write the same context. The lead page shows the person's contact page exactly as you designed it in the CRM, plus calls and notes logged against their company and your meeting write-ups. A CRM record type can feed new leads onto the board. And when a lead reaches the stage you choose, for example “paid”, Sales creates the customer record in the CRM, as a company or a person, and fills in the fields you mapped. CRM segments work as live groups, re-read every time a journey sends, and as a condition inside any segment. The CRM app

Marketing

From a lead's page you can email them with one of your Marketing templates, or add them to a campaign that is still sending. Marketing does the sending. The emails a lead received show on their timeline, with whether they opened or clicked, matched by email address. The other direction works too: the people your Marketing ads bring in land on the Leads board marked “From an ad”, with the ad one tap away, and Monitoring shows the revenue each ad drove and the journey it feeds. Marketing fills the top of the funnel; Sales follows every one of them up. The Marketing app

Tasks

Tasks is where everything that needs your decision reaches you, one tap to approve. Switching a journey live from Claude or ChatGPT is exactly that kind of decision: it arrives on your Tasks board, and nothing is sent until you say yes. The call-backs Sales says you owe, and the to-dos a journey's reminder step writes, sit on the same board as the rest of your work, so one list tells you what to do today. The Tasks app

Shopify, your own systems and Slack

Shopify. Sales, your agent and Helpdesk use the same AssistantLabs app in your store, so it is one install for all of them. It brings in orders, carts, customers, products, discount codes and your store's segments.
Your own system. A form, Zapier or your website can send people into a segment through a webhook, and a lead button or stage can send the lead out to an address you choose, signed so your system can tell it came from you.
API and webhooks. A REST API, using the same organization key as the Agents API, and webhooks that tell your system the moment something happens: someone entered a journey, a message was delivered or failed, someone replied for the first time, a discount code was issued or used, someone finished or left a journey. Every webhook is signed, and a campaign never stops because your endpoint is down.
Slack. The daily “who to call” reminder can go to a Slack channel as well as WhatsApp.

Claude and ChatGPT

Install the AssistantLabs plugin from Claude's plugin directory and Claude gets Sales along with your agent, so it sees your conversations and your campaigns together: ask “what journeys do I have running, and who is hot?”, add a lead, log a call, get a WhatsApp template approved, or have it plan a whole win-back campaign. Reading everything and writing drafts is allowed by default. Two permissions are separate, because they matter: switching a journey live, since it sends real messages, and reading what a customer actually wrote. If you build with code, Settings › Developers in Sales has a skill file that teaches Claude the Sales API and its rules. To connect, open Claude, go to Customize › Plugins › Discover, search AssistantLabs and add it, then type /al and sign in on first use. Connect Claude · Connect ChatGPT

How to get started

You need an agent first. If yours is not answering on WhatsApp yet, connect WhatsApp before anything else, because that is where leads and journeys live.

Open Sales. Sign in at sales.assistantlabs.io with your AssistantLabs account. If Sales is not on for your workspace yet, you will see a page to request access.
Connect your agent. Pick the agent with your WhatsApp number. Settings › Integrations › Agents then shows what it can send on.
Decide who counts as a lead. In Settings › Leads, choose the labels that mark an enquiry, name your stages and set what each button does. If your agent does not label conversations yet, set up tags first.
Connect Shopify if you sell online. Settings › Store, then approve the recommended segments.
Build one journey and test it. Build it yourself or ask the Sales Agent for a draft, add yourself as a test user in Settings › Testing › Test users, send it to your own phone, and only then switch it live.
Go find new customers. Open Sales Team, add a group of your best customers, and let the Analyst build the profile the Prospector searches with.

Ready to start? The step-by-step guide to your first journey

Start small. One journey for the follow-up you most often forget is enough for the first week. Watch Monitoring, then add the next.

Was this helpful?