Make the customer record useful
Customers are the shared record behind bookings, orders, invoices, receipts, forms, review requests, notes, tags, segments, and follow-up work. A good customer profile should explain what happened without forcing the merchant to jump across modules.
Use tags and notes for stable context, not one-off message text. Keep sensitive or temporary details out of public fields and avoid storing raw private customer content where it is not needed.
Use Timeline as the relationship spine
Customer Timeline brings together authoritative activity from the modules Helm owns. It can show bookings, order lifecycle events, invoices, receipts, forms, review requests, customer creation, merge activity, and notes where source data exists.
Some historical details only appear after Helm has durable source events. For example, receipt viewed events or older booking transition details cannot be reconstructed if the source did not persist them.
Follow up from context
Use customer-message actions and Follow-ups to work from the customer record: booking links, invoices, receipts where existing policy supports resend, review requests, manual order updates, direct contact, and private notes.
Manual/copy/open paths are intentional when Helm does not have a safe sender for that exact case. Do not describe these as automatic delivery until the source-owned sender exists.
Customer import checklist
- Start with the customer fields Helm can use immediately: name, email, phone, tags, notes, and source where available.
- Clean duplicates and obvious formatting problems before importing so Timeline and follow-up work stay useful.
- Import a small sample first when possible, then review a few profiles before adding the full list.
- Avoid importing private message bodies, passwords, payment details, or temporary notes that do not belong in the customer record.