How is customer data collected during an estimate call stored and protected?

For Moving Companies

When Voksha handles an inbound call, it captures information like the caller's name, phone number, email if provided, origin and destination addresses, move date, and inventory details such as room count or specialty items. That data is encrypted in transit (TLS 1.3) and at rest (AES-256), Voksha is SOC 2 and ISO 27001 compliant on every plan, and the data is only used to complete the lead capture and booking workflow you configured, then sent to your team by email and SMS alert and, on Premium or Enterprise, your connected calendar or CRM. For a moving company, this data is meaningfully sensitive in a practical sense even without falling under a formal regulatory regime like HIPAA: knowing someone's move date and new address is exactly the kind of information that, if leaked or mishandled, could be misused, so security practices matter even though moving is not classified as a regulated healthcare or financial industry. Only Voksha's Enterprise plan adds GDPR for moving companies that serve customers in the EU or UK, relevant for movers handling international relocations or corporate accounts with EU-based employees, and HIPAA compliance for the smaller subset of movers who handle healthcare facility relocations where patient-adjacent information might come up during the intake conversation. If Voksha support connects a CRM like Salesforce or HubSpot for you on Premium or Enterprise, data moves through that connection rather than manual data entry, which also reduces the risk of a staff member mishandling a spreadsheet of customer addresses and move dates. If you have specific security requirements from a corporate relocation client, that is worth confirming directly against the Enterprise plan's documentation before signing that contract.