Cendaro records customer and lead information so a workspace can recover missed revenue, follow up, book work, and keep an evidence trail. Customer data belongs to the workspace or customer, and Cendaro handles it to provide the service.
What customer data means in Cendaro
Customer data is the information a workspace uses to manage service inquiries, follow-up, bookings, and operational records.
It can include lead records, names, phone numbers, emails, service requests, booking details, notes, owner assignments, message history, communication consent records, AI summaries, and AI-suggested replies.
Why Cendaro records it
- To show which leads need attention.
- To help teams reply to missed calls, forms, voicemail, SMS, and email inquiries.
- To create bookings and preserve follow-up context.
- To enforce consent rules before customer communications are sent.
- To keep message events, audit logs, legal acceptances, and privacy request evidence when needed.
Workspace ownership and responsibility
The workspace owner controls the customer relationship. Cendaro helps record, organize, and enforce the workflow, but the business remains responsible for customer notices, consent, accurate instructions, and lawful use of customer information.
Team members should only access customer data needed for their role and should avoid adding unnecessary sensitive details to notes, messages, support tickets, or audit comments.
Cendaro's service provider role
For many workspace records, Cendaro acts as a service provider that processes information to deliver the platform. That includes storing records, showing them to authorized workspace users, supporting communications, logging compliance events, and helping with privacy request workflows.
Some requests may require Cendaro to confirm whether Cendaro controls the information directly or whether the workspace owner controls it and must provide instructions.
AI-assisted customer data
Cendaro can use customer context to generate AI-assisted summaries, suggested replies, follow-up recommendations, workflow suggestions, or lost reason suggestions.
AI output may be incomplete or inaccurate. Customer-facing AI suggestions should be reviewed by a human before sending unless the workspace has deliberately enabled a reviewed automation path.
Customer communication records
SMS and email activity can create message events, consent records, outbound send logs, blocked-send logs, and unsubscribe records. These records help the workspace understand what happened and why a message was allowed or blocked.
Good handling practices
- Keep customer-entered data as entered; do not translate customer names, service details, notes, or message history automatically.
- Use role-based access so only the right workspace users can view or act on customer records.
- Verify privacy request identity and scope before sharing, exporting, correcting, or deleting customer data.
- Review retention periods so operational records are kept only as long as needed for service, compliance, billing, security, or legal reasons.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.