Every customer's story in one timeline.
Phone, email and your own customer ID resolve to one profile. Orders, checkouts, WhatsApp replies and journey messages line up in one place, so support and marketing see the same customer.
One person, many identifiers
A guest checkout with a phone number and a logged-in order with an email become one profile as soon as your system sends them together. Nothing is merged on a guess.
Full lifecycle timeline
Store events, WhatsApp messages and button taps, journey milestones and profile changes in one chronological stream. Filter by type and load older history.
Search the way people type
Find a customer by phone in any format, email, customer ID or name. Filter by "did order_placed in the last 7 days" or by WhatsApp consent.
Consent per number
Opted in, opted out or unknown for each phone and email, with when it was recorded. Journeys read it before every marketing send.
Right inside the inbox
Open a conversation and see the same profile beside it: identifiers, traits and the latest events, with a link to the full history.
Simple to feed
POST /v1/events and POST /v1/profiles with an API key. Send traits like first name or city once and they are available to templates.
How it works
Send events and identity
Your backend calls the events API when customers act, with whatever identifiers it has.
Profiles build themselves
WapiSnap resolves each event to a person, links identifiers sent together, and records consent.
Look up anyone, anytime
Search Customers, open a profile, and read the whole story before you reply or launch a journey.
What a support agent sees
Instead of asking "what was your order number?", the agent sees the checkout, the order, the reminder that was sent, and whether the customer converted afterwards.
- Identifiers with consent per channel
- Traits your store sent: name, city, plan
- Active journeys and when they next act
- Every event with expandable raw properties for debugging
Careful about who is who
Wrongly merging two people is worse than keeping them apart, so merging follows strict rules. Nothing is combined on a guess, and every merge is recorded with a snapshot and shown in the timeline.
Two endpoints, one API key
The same key you use to send messages works for events and profiles.
Frequently asked questions
How do you decide that two records are the same person?+
Only when your own system says so. If one event carries both a phone number and an email, they are linked to one profile. WapiSnap never merges on a guess such as similar names or partial numbers. Two different customer IDs are never merged, and a profile that would end up with more than three phones or emails (a shared family phone, an office inbox) is flagged for review instead of being combined.
What phone number formats are accepted?+
Any common format. Numbers without a country code are read as your workspace's default country (India by default), so 9876543210, 09876543210 and +91 98765 43210 are the same person. Numbers from other countries should start with +. Invalid numbers are rejected instead of stored.
What is in the timeline?+
Events your systems send (checkouts, orders, deliveries), WhatsApp activity (messages received and button replies), journey milestones (entered, message sent or not sent and why, goal reached, left) and profile changes such as merges. You can filter by type, load older history, and expand any event to see its raw properties, which is handy when checking an integration.
How is consent tracked?+
Per phone number and per email address, not per person: opted in, opted out or unknown, with when and where it was recorded. Send it with an event or through the profiles endpoint. Journeys use it to decide who may receive marketing templates.
Who in my team can see this?+
Every role in the workspace (owners, admins, agents and analysts) can view customers and their timelines. The list is scoped to your workspace only.
Is this a customer data platform?+
No. It is a lightweight profile and event store built for WhatsApp messaging: enough to know who someone is, what they did, and what you sent them. It does not replace your CRM or warehouse, and it is not meant for storing card or payment details.
Your WhatsApp. Your AI. Your rules.
Join businesses automating WhatsApp without vendor lock-in.