How WSC organizes service and sales on WhatsApp

An account can connect several numbers (up to its plan's limit) and mix the two ways of connecting. Each conversation stays on the number the customer wrote to.

• Official API: the number is verified by Meta, sends approved templates and runs mass campaigns.
• Wpp Web: connects an existing WhatsApp by scanning a QR code, in a minute, with no approval process.
• Each number can have a name (Sales, Support), a default queue and, if you want, a dedicated person.
• Restrict a number to some members: a seller sees only the conversations of their own number.

The team answers in one place, with the full history of each customer. Every conversation has an owner, a status and the next step.

• Assign, transfer and close conversations; filter by mine, unassigned or by number.
• Internal notes in the middle of the conversation, visible only to the team.
• Quick replies: type / and pick a ready-made answer.
• Text, audio, images, documents, buttons and lists, with delivery and read status.

Queues group people by subject (Sales, Support, Billing) and decide who receives each new conversation, without anyone having to pick it up by hand.

• Round robin takes turns among the people in the queue; least busy picks whoever has fewer open conversations; manual lets the team claim them.
• Opening hours per queue, with an automatic message outside them.
• Conversations enter a queue through the number's default queue, a flow, an automation, an AI agent or a manual transfer.
• Closing a service returns the customer to the start: the next message is routed again.

The monitoring screen shows managers how each queue is doing right now and how service went over the period.

• Average wait time: from entering the queue to the first human answer.
• Average handling time: from assignment to the end of the service.
• Peek at any conversation without interfering, and transfer it to another queue or person.

Every customer who writes becomes a contact, and every opportunity becomes a deal on a kanban, linked to the conversation.

• Several pipelines, with your own stages and currency.
• Tags and custom fields to segment and find customers.
• Import and export contacts by CSV.
• Open the deal from the conversation and the conversation from the deal.

Send a message to a list of contacts and follow the result as it happens: sent, delivered, read and answered.

• Pick the audience: all contacts, tags (with exclusions), a custom field or a CSV, and the number that sends.
• Templates with variables per contact (name, order, date).
• Answers fall into the inbox like any other conversation.

An automation reacts to something that happened and runs a sequence of steps. It is the way to standardize the routine without depending on memory.

• Triggers: new message, first message from a contact, keyword, button reply, new contact, assigned conversation, tag added or a schedule.
• Steps: send a message, buttons, list or template; add or remove tags; assign; update a field; create a deal; wait; call a webhook; close.
• Conditions (if / else) to take different paths.

A flow is a conversation drawn as boxes and arrows: a menu, questions, answers and the moment a person or the AI takes over.

• Starts with a keyword, with the contact's first message or by hand from the inbox.
• Send messages, buttons, lists and media; collect answers; branch by condition; tag.
• Hand over to a queue, to a person or to an AI agent, which can bring the conversation back to the flow.

Create as many agents as you need, each with its own instructions, knowledge base and numbers. The agent answers customers and routes them when the subject calls for a person.

• Knowledge base with your documents and policies: answers cite what is written there.
• Routing rules: when the customer talks about price, it goes to the Sales queue; when the AI does not understand, it goes to a human.
• A playground to test the agent before putting it in front of customers.
• In the inbox, the AI also suggests replies for the person who is answering.

Issue charges (invoices) for your contacts, automate monthly fees, and let a reminder schedule handle the follow-up before and after the due date.

• One-off invoices or recurring charges that generate the next invoice by themselves.
• Reminder schedules: messages a few days before, on the due date and after, which stop when the invoice is paid.
• Mark as paid by hand or through your system, using the API.

Invite the team and decide what each person sees and does, module by module. Four ready profiles cover the common cases, and you can create your own.

• Administrator manages everything; Agent serves conversations and contacts; Seller also handles deals; Viewer only looks.
• Custom profiles with permissions per action: view, reply, transfer, export, send campaigns…
• Whoever leaves the team loses access at once; the history stays in the account.

Press ⌘K (Ctrl+K on Windows) anywhere to jump to a screen, find a contact or ask the AI assistant about your operation in plain language.

• Questions such as how many conversations are open today or who has not answered yet.
• It respects the permissions of whoever asks: it only sees what that person sees.
• Before changing anything, it shows what it is going to do and asks for confirmation.