CASE STUDY 02 / CUSTOMER EXPERIENCE
Customer supportAcknowledgments & priority alerts.
Acknowledge critical customer confirmations and notify administrators of high-priority tickets in Telegram, with staff approval for customer replies.
System overview
Inspect the workflowsEmail and Messenger feed a shared ticket process, with dedicated acknowledgment paths and clear responsibilities for the support team.
Message received
Capture Gmail and Messenger conversations and associate incoming messages with ticket and order context.
Priority identified
Identify critical size confirmations and route high-priority tickets to the appropriate acknowledgment path.
Admin notified
Notify administrators in Telegram so they can claim a ticket and inspect the relevant customer context.
Staff reviews
Staff review knowledge-assisted drafts and tracking updates before approving customer delivery.
Critical confirmations acknowledged · approved replies
- Controlled acknowledgments
- Critical confirmations use a dedicated receipt path while staff retain approval of customer replies.
- Human review
- Ticket claiming, knowledge retrieval, and reply editing keep staff accountable for support decisions.
- Recovery & reconciliation
- Stalled-state monitors and ticket-sheet reconciliation bring incomplete work back into view.
THE CHALLENGE
The operational challenge.
Support staff need to connect email and Messenger conversations with ring-size confirmations and shipment details. Missed handoffs can leave both customers and staff unsure of the next step.
THE SOLUTION
The system design.
Gmail and Messenger intake feed a shared ticket process. Critical ring-size confirmations have a dedicated receipt-acknowledgment path, while high-priority ticket alerts reach administrators in Telegram. Staff claim tickets, retrieve approved knowledge, and review customer replies and tracking updates before delivery.
DESIGNING THE SYSTEM
Key engineering decisions.
Surface the critical message.
Ring-size confirmations are prioritized, acknowledged, and surfaced to administrators through Telegram ticket alerts. Staff claim tickets and review knowledge-assisted drafts before approving replies.
Model the actual order.
Tracking supports multiple ring variants with color, size, and quantity. Ring-size confirmations are recognized and acknowledged as part of the support flow.
Verify uncertain outcomes.
Sent-message verification helps reconcile uncertain sends. Four stalled-state monitors, a Gmail error handler, and daily Sheets reconciliation support recovery.
SYSTEM ARCHITECTURE
Integrations and recovery paths.
The overview above shows the main path. Explore the architecture for the integrations, decision points, and recovery paths behind it.
INSIDE THE SYSTEM
Explore the actual workflows.
Inspect the intake paths, integrations, review steps, and recovery routines behind this system. Open any screenshot to read the original n8n canvas.
Intake & routing
Gmail ticket intake & routing
Classifies inbound email, records ticket state, routes administrator alerts, and handles customer acknowledgments.
Messenger ticket intake
Records Messenger tickets and separates new-ticket alerts from follow-up notifications.
Order intake & duplicate checks
Order-context workflow showing cached authentication, duplicate checks, intake claims, and customer lookup.
Human review
Telegram administrator actions
Draft canvasAdministrator action paths with knowledge retrieval and review-assisted reply drafting.
Secure reply editor
Separate editor paths for retrieving, validating, and submitting staff-reviewed replies.
Knowledge & reporting
Knowledge-base PDF ingestion
Draft canvasValidates uploaded PDFs, checks prior ingestion, and routes documents into a vector-store embedding pipeline.
Ticket-sheet synchronization
Mirrors email and Messenger ticket records into Google Sheets, with a scheduled reconciliation path.
Monitoring & recovery
AI generation recovery monitor
Finds stalled AI generations, sends a Telegram alert, and records that review was requested.
Acknowledgment review monitor
Finds stalled size acknowledgments and brings them to staff attention in Telegram.
Tracking-send recovery monitor
Checks stalled tracking sends and records alerts to avoid repeatedly notifying staff.
Reply-send recovery monitor
Finds stalled reply sends and coordinates notification records with Telegram alerts.
Workflow failure email
Routes execution failures from an error trigger to an administrator email.
WORKFLOW OUTPUTS · REDACTED SAMPLES
Acknowledgments, alerts, and tracking updates.
These supplied screenshots illustrate customer communication, priority handling, and staff tracking entry. Identifying details have been partially redacted in the supplied images.
The examples show the interface and message content. They do not establish successful approval, end-to-end execution, delivery reliability, or measured production results.
Customer acknowledgment
The email acknowledges receipt of ring variant details under a support ticket and explains that the team will review them before providing a tracking update.
High-priority Telegram alert
The alert marks the size confirmation as high priority and presents the message alongside actions to accept the ticket or open the Gmail thread.
Staff tracking form
The staff form collects a tracking number and optional link, with separate color, size, and quantity fields for each item. Its submission action requests Telegram approval.
Customer tracking email
The customer email presents tracking information and a shipment item breakdown, including color, size, and quantity for multiple ring variants.
EVIDENCE & OUTCOMES
What the evidence shows.
The source documents 11 workflows and 263 nodes across two inbound channels. Selected tests include a 60-row observation: 59 Gmail records and one Messenger record.
Tested configuration awaiting client handoff. The sample records are test evidence, not a claim about production traffic.
Limitations and next steps.
Response-time improvements and production savings have not been measured. Handoff and live operational validation remain next steps.
Technology stack.
- n8n
- Gmail
- Botcake
- Supabase
- OpenAI
- Telegram
Source: owner-supplied case study and diagrams. Scope and test results are reported in the document, not independently audited.