Guide · Workflow
From lead to outcome: walk the whole workflow.
ConvoTide’s promise is one connected workflow — capture, converse, follow up, measure — instead of four tools with four copies of the truth. This tutorial follows one sample lead the whole way through and shows where each step actually lives. The names and details are illustrative examples for this walkthrough.
The example scenario
Priya scans a QR code on a shop window at 6:40 pm and asks on WhatsApp: “Hi! I saw your offer — is it still available?” She is a lead, a conversation, and — if the workflow works — eventually a recorded outcome. Here is every step, in order.
Step 1 — Capture
The QR code carries a source tag, so when Priya’s message arrives the platform creates her contact record with the source attached — not a bare phone number in a spreadsheet. Contacts in ConvoTide are created by real inbound events: messages, QR scans, links, widgets and ad referrals. The CRM never invents a contact that no conversation produced, so your pipeline is made of people who actually reached you.
Step 2 — Converse
Priya’s message lands in the shared inbox with her source visible. An available team member claims the conversation — the platform records the claim, and if a colleague already held it, the second claim is refused and names the holder. No double-replies, no “who has this customer?” The rep answers from a canned reply for the common question, edits it to fit, and the draft carries the conversation context beside it.
Step 3 — Follow up
Qualification happens in the chat. Because the deal panel sits beside the conversation, the rep creates a deal from the same view — no copy-paste into another tool. The deal enters a pipeline stage, and a follow-up task is created with an owner and a due date. If Priya replies first, the task is cancelled automatically: automation respects the conversation. If she goes quiet, the task comes due. A journey can carry the same logic for every future lead — an opted-in send step, a wait, a consent check — with every enrollment state visible (active, completed, or exited by consent).
Step 4 — Measure
Every message in the story has a status timeline built from signed webhook events — sent, delivered, read, replied — recorded in the order the events actually arrived. The deal closes won or lost (terminal either way, so reports cannot be flattered after the fact). The funnel view connects the QR scan to the outcome through the same event store, so the report and the conversation tell one story — estimates and actuals are never mixed. Reading the numbers well is its own skill: see the results guide.
Before you begin
- This walkthrough uses an example customer journey. Live message sending turns on per business once the Meta connection is verified for that business — the getting-started guide covers the sequence.
- The journey canvas shows the workflow and its branches. Use the workspace controls to configure your journey and review its steps before activation.
- See the surfaces yourself in the workspace tour, or read what each surface does in the product overview.