Cross-channel customer context: recognise and hand over
Keeping context when a customer switches channel: channel identifiers, matching rules, the risk of a wrong merge and a five-line summary for the next agent.
This section explains how a team should work when customers write and call through several channels: the daily rules of a shared inbox, recognising a customer and passing context on when they switch channel, preventing duplicate leads, routing requests to the right team, measuring response time per channel and planning an automation pilot.
The articles are less about connecting channels technically and more about making them work as one process. See which channels can be connected on the integrations page, or build your own flow with us.
6 of 6 posts shown
Keeping context when a customer switches channel: channel identifiers, matching rules, the risk of a wrong merge and a five-line summary for the next agent.
Preventing duplicate leads across channels: one number format, the open-lead rule, a dedupe window and the difference between person, lead and enquiry.
An omnichannel automation pilot: two channels and one flow, a readiness checklist, a baseline, a six-week plan, decision criteria and risk control.
Omnichannel inbox: views, ownership, statuses, bot state and a daily rhythm for running WhatsApp, Instagram and website messages from one place.
How to track an omnichannel SLA: first, next and resolution time, when the clock starts and stops, bot replies and reporting percentages instead of averages.
Routing written customer requests to the right team: intent categories, a routing matrix, mixed messages, working hours and a fallback owner.
See Vexvon live in a 10-minute demo.