Delivered engagement — identifying details removed
Personalized wall-art businessCustom prints and e-commerce
WhatsApp orders for personalized wall art.
- The need
- Each personalized artwork takes several messages to get right. With many WhatsApp conversations running at once, the team needed to collect order details, track progress and know when a customer needed help.
- What we automated
- We connected WhatsApp to an AI order assistant and a custom CRM. The assistant handles routine exchanges, while the team sees order status and takes over complex conversations with their context intact.
Illustrative stock photo, not project imagery.Yunus Tuğ / Pexels
Delivered engagement — identifying details removed
This page documents only the structure or implementation supported by the recorded sources. No measured outcome or testimonial is currently approved for publication.
From WhatsApp message to tracked order and escalation
Use Previous and Next to follow the anonymised journey. The map explains the delivered system without exposing client data or production configuration.
Delivered system · anonymised view
WhatsApp orders, CRM updates and human takeover
A public, sanitized reconstruction of the delivered journey. It shows system responsibilities without customer data, prompts, credentials, internal URLs or production configuration.The operational problem
Order details and customer questions were being handled inside many simultaneous chat threads. Without a shared operational record, the team had to reconstruct context, track progress manually and decide when to step in. A chatbot alone would not solve that problem: the business needed parallel conversation handling, explicit permissions, live order visibility and a clean human takeover path.
This page separates implemented structure from unverified outcomes or claims. Existing public identities remain bounded by each case's declared status and sources. Any new or expanded identity, testimonial, metric, or verified outcome requires claim-specific evidence and publication approval.
Current-state flow
The repeated handoffs the system is designed to replace or make visible.
- 01
A WhatsApp message is linked to the correct conversation and order context.
- 02
The AI agent responds in natural language, collects missing order details and advances requests that remain inside its approved scope.
- 03
The custom CRM updates the order state in real time so the team can see progress across active conversations.
- 04
When a customer requests a person or the issue exceeds the agent's permissions, the conversation moves to the escalation interface with its context preserved.
Constraints and risks
These conditions shape the architecture before automation begins.
Parallel conversations need isolated context
Every reply must remain attached to the right customer and order, even while many personalized requests are active at the same time.
Natural language does not mean unlimited authority
The agent can guide and process approved order steps, but exceptions, sensitive issues and actions outside policy must stop and move to the team.
A handoff cannot lose the conversation
The assigned team member needs the order record, recent messages and reason for escalation before replying, so the customer does not have to start again.
System design
A traceable path from intake to action, with uncertainty surfaced before it becomes an operational error.
WhatsApp conversation layer
Incoming messages are connected to the right order context and remain available as part of the operational history.
Bounded order agent
The smart agent handles several order conversations in parallel, uses the approved business tone and escalates when the next action falls outside its permissions.
Custom CRM and takeover interface
A purpose-built workspace shows live order state, conversation ownership and the context the team needs to continue an escalated discussion.
Responsibility by design
The system does not treat every task as an AI task.
Deterministic responsibilities
Repeatable rules own validation, state, and system changes.
- Connect each WhatsApp event to the correct conversation and order record.
- Persist customer messages, agent replies, order state and conversation ownership.
- Synchronize approved order updates with the custom CRM in real time.
- Open a human-review item when a customer requests a person or a permission boundary is reached.
- Keep the handoff reason and conversation context visible to the assigned team member.
- Record whether the active conversation is owned by the agent or a person.
Bounded-AI responsibilities
AI assists with narrow interpretation work and exposes its basis.
- Respond in natural language that follows the business's approved tone and order information.
- Identify which details are still missing before an order can move forward.
- Maintain the relevant context while several customer conversations progress independently.
- Answer and act only within the permissions defined for the order-processing role.
- Explain the next step or escalate the conversation when the request is ambiguous, sensitive or out of scope.
Human approvals and exceptions
People keep authority over consequential and ambiguous cases.
- Define the product information, conversation rules and actions available to the AI agent.
- Take over whenever a customer asks to speak with a team member.
- Resolve complaints, unusual customization requests and issues outside the agent's permissions.
- Approve consequential order changes and decide when a resolved conversation can return to automated handling.
Integration surface
Connect to the existing operating environment without pretending every tool is a system of record.
- Customer conversation intake, outbound replies and continuity across the order discussion.
- E-commerce order context
- Approved product and order information used to understand the request and keep the conversation grounded.
- Custom CRM
- Real-time order status, conversation history, ownership and internal tracking for the operations team.
- Escalation workspace
- A focused interface for reviewing the reason, taking ownership and continuing the WhatsApp conversation.
What the engagement should deliver
Not just a demo: the operating model, working system, tests, controls, and handover needed to own it.
- WhatsApp integration for personalized order conversations
- Smart order-processing agent with natural-language responses
- Parallel conversation handling with separate order context
- Custom CRM for real-time order tracking and team visibility
- Human escalation interface with conversation context and ownership
- Permission boundaries and handoff rules for out-of-scope requests
Limitations and next phase
Start narrow enough to validate the operating model before expanding its authority or scope.
- The public system map is an anonymised reconstruction; customer data, prompts, credentials, internal URLs and production configuration are omitted.
- Agent responses depend on the completeness and freshness of the approved product, policy and order information available to it.
- Ambiguous personalization details, complaints and actions outside the defined permissions require a team member.
- Conversation and order synchronization depends on the continued availability of WhatsApp and the connected commerce systems.
- No response-time, conversion or order-volume metric is published because no approved measurement was provided for this case study.
Possible next phase
Use the CRM history to review where handoffs occur, refine the agent's permissions and improve the order states only where the recorded conversations support the change.
Your workflow will be different
Turn the blueprint into a system shaped around your tools and controls.
Bring the current steps, owners, systems, and recurring exceptions. The first conversation is for mapping the workflow and deciding whether a custom build is justified.