Customer records
One record per person, whichever door they walk through.
A customer who reaches you on WhatsApp today and the widget next month is one person, not two strangers. That single memory is the part a bot-per-channel cannot do.
A customer who reaches you on WhatsApp today and through your website next month is one person. Most setups treat them as two, because a bot per channel keeps its own memory and neither one knows the other happened.
Gojify keeps a single record per person that survives every conversation on every channel, with the whole history behind it. Two things sit on that record and they do different jobs. Contact fields hold facts you decided to collect, so the medical-aid number or the vehicle registration arrives as data you can filter and report on, rather than buried in a transcript somebody has to read. Tags mark what a conversation has reached, so a quote sent or a complaint opened is a state you can route on.
That distinction is what turns conversations into something you can work with. It also makes opt-out reliable: anyone who opts out is excluded by the platform on every send path, rather than remembered by a person who might be on leave.
One customer record
One record per person that survives every conversation on every channel, with the whole history behind it.
Contact fields
Decide what the agent must find out and where it lands, so the details you need arrive as data rather than buried in a transcript.
Tags
Mark what a conversation has reached, then filter, report and route on it.
Import your list
Bring your existing customers in from a spreadsheet, with their opt-in status intact.
Opt-out, enforced
Anyone who opts out is excluded by the platform rather than remembered by a person, on every send path.
Search and segment
Find anyone by name, number, tag or any field you defined, and turn that into an audience.