Channel-Agnostic Conversations

Your prospects don't care about your channel strategy. They message on WhatsApp, reply to email, fill a web form, start a web chat, DM on Instagram — often in the same conversation. If your CRM treats these as separate threads, you lose context, duplicate work, and miss revenue signals.

**Common pattern:** Team adopts WhatsApp Business. All conversations forced there. **Result:** - Leads who prefer email get ignored - Web chat transcripts lost when agent switches - Instagram DMs never reach sales - No unified timeline for the prospect - Reporting by channel, not by customer

**Root cause:** Tooling designed for channels, not conversations.

RevenuePilot's model: **One customer, one conversation timeline, many channels.**

**Identifier resolution:** - Email → contact record - Phone/WhatsApp → contact record (normalized E.164) - Instagram/Messenger → contact record (platform ID) - Web form → contact record (email + fingerprint) - Web chat → contact record (session + email capture) - CRM sync → existing contact match

**Deduplication:** Automatic merge on email, phone, or external ID. Manual merge with audit trail.

| Channel | Inbound | Outbound | Media | Automation | |---------|---------|----------|-------|------------| | Email | ✅ | ✅ | Attachments | ✅ | | WhatsApp | ✅ | ✅ | Images, docs, voice | ✅ | | SMS | ✅ | ✅ | Text | ✅ | | Web form | ✅ | — | File upload | ✅ | | Web chat | ✅ | ✅ | Images, files | ✅ | | Instagram DM | ✅ | ✅ | Images, voice | ✅ | | Messenger | ✅ | ✅ | Images, files | ✅ | | Phone (via integration) | ✅ | ✅ | Recording | ✅ |

**Future channels** plug into the same conversation timeline via the connector framework.

**What the rep sees:** One chronological feed per contact.

- 09:12 — WhatsApp inbound: "Interested in pricing" - 09:15 — Email sent: Pricing PDF + Calendly link - 09:18 — WhatsApp outbound: "Sent pricing to your email" - 09:45 — Web form: Demo request (auto-merged) - 10:02 — Email open tracked - 10:05 — Calendly booking: Demo scheduled - 10:10 — WhatsApp: "Booked for Thursday 2pm"

**No channel switching. No context loss.**

Workflows trigger on **conversation events**, not channel events.

**Examples:** - "No reply 24 hr" → send follow-up on **preferred channel** (last used by contact) - "Lead qualified" → notify owner via **Slack + email** - "Risk detected" → create task in **CRM + assign in inbox** - "Meeting booked" → send confirmation on **booking channel + email**

**Channel preference learning:** System observes reply patterns and defaults to contact's preferred channel for outbound.

**Traditional:** "WhatsApp: 45 conversations, Email: 32, Web chat: 18" **Unified:** "45 active conversations across 38 contacts. 12 qualified, 8 in pipeline."

**Metrics that matter:** - Conversations per contact (channel diversity) - Time-to-first-reply (any channel) - Touches to qualification (cross-channel) - Channel preference distribution - Channel failure rates (bounces, blocks, opt-outs)