Is it safe to have the AI take a customer's payment or card information over the phone?

For Auto Repair Shops

On Starter and Premium, Voksha doesn't take payments at all, so it isn't collecting or storing card numbers as part of a normal call. Taking payments, and texting callers things like payment links, are Enterprise-only features. For most independent shops, keeping card handling out of the phone answering tool is actually the safer setup: PCI-DSS requirements around card data get complicated fast once you introduce a new system that touches payment card information, and most shops don't want that liability sitting on a phone answering tool. If a caller wants to put down a deposit or pay for a repair, Voksha captures the request and flags it for your team, who can call the customer back, take payment at the counter when they pick up the vehicle, or use whatever point-of-sale system you already run. That keeps your card data handling exactly where it already lives today, inside your existing payment processor, rather than adding a new system that needs its own review. For the information Voksha does collect, name, phone number, vehicle details, and appointment specifics, that data is encrypted with AES-256 at rest and TLS 1.3 in transit, and Voksha is SOC 2 compliant and ISO 27001 compliant on every plan. It reaches your team in a structured call summary, or on Premium and Enterprise in a shop system like Shop-Ware or Mitchell 1 set up with Voksha support, rather than sitting on a sticky note at the front counter, which is a meaningful upgrade over how a lot of independent shops currently manage phone-in customer information.