Name & status
Who the customer is in your business records.
Customers
Customer context that stays connected to every interaction.
NLDONA connects customer details, preferences, conversations and bookings so your team can serve people with context — while keeping access controlled.
CustomerCustomer context available
Maria K.
Contact
- Phone
- Preferred language
- German
- Upcoming
- Fri · 15:30 appointment
- Recent
- Rescheduled by phone
- Communication
- Email confirmation preferred
Illustrative customer profile — not a verified-identity claim.
Connected context
One customer. Context across every supported channel.
NLDONA can connect customer context across supported channels when the business can safely resolve the customer.
A customer should not become four disconnected records just because they used different channels.
VoiceWebsite ChatWhatsAppPublic Booking
Customer context
Bookings, preferences and relevant business activity stay linked when resolution is permitted.
Profile
Keep the details that actually help serve the customer.
A customer workspace for operations — not a sales CRM.
Contact points
Phone, email and WhatsApp details when available.
Preferred language
Serve conversations in the language they prefer.
Confirmation preference
Email, SMS or WhatsApp when configured.
Upcoming activity
Appointments and reservations linked to the customer.
Waitlist & reminders
Related waitlist and reminder records stay linked when present.
Remember useful context — not uncontrolled AI memory.
NLDONA remembers approved customer context so customers do not have to repeat the same business details every time.
Durable context is server-owned customer data. It does not authenticate the customer, and it is not free-form AI memory.
Illustrative profile fields — not a live tenant record.
History
See the relationship through bookings and context.
Relevant booking history stays connected to the customer profile.
Upcoming bookings
What is scheduled next for this customer.
Booking history
Past appointments and reservations linked to the profile.
Communication preference
How they prefer confirmations when configured.
Channel-linked bookings
Schedule changes stay linked when the customer can be safely resolved.
Customer context stays connected to the work.
Customer details matter because they connect to real schedule activity — not a standalone address book.
- Customer
- Maria K.
- Upcoming
- Fri · 15:30
- Preference
- Email confirmation
- Recent
- Reschedule completed
NLDONA shows relevant booking-linked history available to your business — not a complete interaction timeline or unlimited lifetime archive claim.
Preferences
Contact customers the way they prefer.
Conversation channel and confirmation channel may differ — when your business has those channels configured.
Keep WhatsApp contact details on the profile when connected.
Use email for confirmations when that is the preferred channel.
SMS
Send SMS confirmations when SMS is configured for your business.
- Voice call → email confirmation
- Website chat → SMS confirmation
- WhatsApp → email confirmation
Contact points
Keep phone, email and WhatsApp details connected to the customer profile.
Contact information helps locate context. It does not automatically mean verified identity.
Channels are used only when switched on for your business — not assumed everywhere.
Import
Bring your existing customer list with you.
A governed CSV import path for onboarding — with review before commit. Exact matches can be skipped; conflicts require review.
01
Upload
Start from your customer CSV.
02
Map columns
Match name, phone, email, WhatsApp and preferences.
03
Validate
Review rows before anything is written.
04
Review & import
Resolve conflicts and commit only what you accept.
Supported concepts include name, phone, email, WhatsApp, language and confirmation preference.
No blind overwrite. Import uses upload, mapping, preview and commit — not silent merge.
Identity & control
Recognise context without guessing identity.
Customer context stays under business control.
Caller resolution
A caller number may help locate candidates. Plausible context is not the same as proven identity.
- One clear match may offer useful context
- Ambiguous results require care
- Sensitive details stay behind authorization and disclosure policy
Archive with care
Customer records can be archived and managed without breaking historical bookings and business records. Privacy erasure is a separate compliance workflow — not ordinary record cleanup.
Tenant-scoped data
Customer records belong to your business tenant.
Controlled access
Team members see what they are authorised to see.
Contact ≠ identity
Phone or email does not automatically prove who is contacting you.
Protected history
Historical bookings and business records remain governed.
FAQ
Common questions about NLDONA Customers.
Short answers based on current product truth.
What is the Customers workspace in NLDONA?
It is the business-facing customer directory and profile workspace that keeps details, preferences and booking-linked context connected to conversations and operations.
Is NLDONA a CRM?
No. NLDONA provides customer operations context for appointment-driven businesses. It is not positioned as a generic sales CRM.
What customer information can NLDONA store?
Name, status, phone, email, WhatsApp contact points, preferred language, confirmation preference, and linked booking activity — including related waitlist and reminder records when present.
Can NLDONA remember customer preferences?
Yes. Approved customer context such as language and confirmation preference can be remembered as server-owned profile data — not free-form AI memory.
Can NLDONA link calls to customer context?
Where permitted, NLDONA can connect conversations to relevant customer context when the business can safely resolve the customer.
Does a phone number prove customer identity?
No. A phone number may help locate context. It does not prove identity by itself.
Can NLDONA show upcoming appointments for a customer?
Yes. Upcoming appointments and reservations linked to the customer stay visible in customer context.
Can I import customers from CSV?
Yes. CSV import supports upload, column mapping, validation, conflict review and commit. There is no blind overwrite.
Can customers prefer Email, SMS or WhatsApp confirmations?
Yes, when those confirmation channels are configured for your business. Conversation channel and confirmation channel may differ.
Can I archive a customer?
Yes. Archiving manages the customer record while protecting historical business records. Privacy erasure is a separate workflow.
How does NLDONA protect customer data?
Customer data is tenant-scoped, access-controlled, and subject to authorization versus disclosure rules. Contact data does not automatically equal identity.
Can NLDONA connect customer context across Voice, Chat and WhatsApp?
Yes, across supported channels when the business can safely resolve the customer — without inventing automatic universal matching.
Try NLDONA
See how NLDONA could keep customer context connected for your business.
Paste your public website to start a temporary demo under your review.
Public information only. Demo experiences stay isolated from Production.