Prepared with AI assistance and reviewed for clarity, relevance and unsupported claims.
A WhatsApp sales conversation workflow should make the next action clear to both the customer and the business. “I'm interested” might mean “answer one question”, “check whether you can reserve it” or “ask someone to call me”. It does not automatically mean “place an order”.
For a merchant or service SME in Morocco, the useful design question is therefore not just what the assistant should say. It is what should exist after the conversation: an answered question, a pending request, an assigned review or an agreed callback. Some conversations should end with no further action at all.
1. Separate customer intent from business commitment
Record what the customer asks for before choosing a workflow outcome. Distinguish an expression of interest from a request, and a request from a business confirmation.
For example, “Can you hold this table?” is a reservation request. “The table is reserved until the agreed deadline” is a confirmation that requires the shop's reservation conditions and availability checks to have been satisfied. The assistant must not jump between these states because the customer sounds enthusiastic.
A simple closing question often resolves ambiguity: “Would you like more product details, a reservation check or a call from the team?” Offer only options the business actually supports. If the customer is merely browsing, answer the question and leave the next move with them.
This distinction also applies to future products. See the guide to separating interest, reservations and confirmed commitments when stock or fulfilment is not yet settled.
2. Define four distinct outcomes
Give each outcome its own completion condition. Otherwise, a generic “lead handled” status can hide unfinished work.
- Product question: provide the verified answer, or record the exact question that still needs a person. An answered question does not require an order record.
- Reservation request: identify the item and variant, check the relevant conditions and obtain confirmation from the authorised source or person. Until then, label it requested, not reserved.
- Quote review: gather the information needed to assess scope and assign a reviewer. Do not imply that a total or delivery date has already been approved.
- Human callback: agree on the contact method and timing preferences, create a task and have the responsible team accept it before promising a slot.
Each outcome also needs a customer-facing statement. “Your request is awaiting a stock check” is more useful than “Thank you for your interest”, because it explains what remains undecided.
Where the next step is a quotation, the rules for listed prices and scoped quote reviews help define what the assistant may share before approval.
3. Give every open action an owner and completion rule
A next step is not operationally clear unless someone can identify who owns it, what they must do and how they will know it is complete. The owner may be a role, such as the furniture sales desk, provided the team knows who is covering it.
Use a compact action record:
- Customer request and relevant product reference.
- Information already confirmed.
- Outstanding decision or missing input.
- Assigned owner and current status.
- Agreed timing, or a note that timing is still unconfirmed.
- Completion evidence, such as an approved quotation sent or a callback outcome recorded.
Distinguish waiting for the business from waiting for the customer. If staff need a measurement, the task should say so. If the customer has already supplied it, the request should return to the review queue rather than remain indefinitely “pending”.
More statuses offer detail but increase maintenance. Start with a small set that changes what staff do, rather than labels that merely describe mood or sales enthusiasm.
4. Example: a furniture enquiry becomes a confirmed callback task
Consider a hypothetical furniture shop. A customer likes a dining table but wants to discuss access to an upstairs apartment before deciding. The product has not been reserved, and delivery feasibility has not been checked.
Customer: “I like this table. Can someone call me about getting it upstairs?”
Assistant: “Yes, I can request a callback about access and delivery arrangements. Is this the best number, and what time range would suit you?”
Customer: “This number, tomorrow afternoon.”
Assistant: “I'll send that preference to the furniture team. The callback time is not confirmed yet, and the table has not been reserved.”
The task includes the table reference, the access question, the preferred number and the requested time range. It does not require a full delivery address merely to arrange the call. Staff can request more detail if needed for their assessment.
Suppose the assigned salesperson accepts the task and confirms an available afternoon slot. Only then does the customer receive the agreed callback time. The task is now confirmed as scheduled, not completed. After the call, the salesperson records whether further assessment, a quotation or no action is required.
5. Handle interruptions without creating duplicate commitments
Customers may change their minds, send the same request again or speak directly with a staff member. Check the existing open action before creating another task. A second message about the same callback may be an update, not a new callback request.
When a salesperson takes over, pause automated progression for that conversation. Otherwise, the assistant might request measurements while the salesperson is already discussing them, or announce a reservation that staff are still checking. The guide to preventing automation from interrupting human conversations explains this boundary.
Define what happens after an unsuccessful call, a missed internal review or a customer withdrawal. An attempted callback is not the same as a resolved enquiry. Record the attempt and follow the agreed contact preference rather than automatically starting repeated calls or messages.
If a task cannot be created or assigned, do not tell the customer it is booked. Keep it visibly unresolved and use a manual fallback.
6. Check whether the workflow ends honestly
Review a sample of hypothetical paths before launch: a question answered with no further interest, an unavailable reservation, an incomplete quote request, a changed callback time and a cancelled request. For each, compare the customer message with the actual internal state.
The essential check is simple: does the message promise more than the business has confirmed? Also verify that every open action has an owner and every closed action has a reason. “No further action requested” is a valid outcome, not a workflow failure.
A WhatsApp sales and order enquiry assistant with human handoff should follow these outcome rules. Its value is not in pushing every conversation towards an order, but in making the appropriate next step explicit.
To discuss mapping these outcomes to your team's actual responsibilities, contact FlowAgent about this workflow.