Approved business knowledge
Penny is designed to answer from the services, pricing records, FAQs, hours, policies, and booking rules approved in each workspace.
PennyReply trust center
This page explains the operational safeguards behind AI replies, customer messages, booking, payments, and business data without making promises the product cannot prove.
Penny is designed to answer from the services, pricing records, FAQs, hours, policies, and booking rules approved in each workspace.
Low-confidence requests, complaints, refunds, custom quotes, and configured exceptions can stop the automated flow and request a person.
Operational and marketing messages remain distinct. Opt-outs, quiet hours, recipient eligibility, and delivery history are part of the messaging workflow.
Business data is loaded by tenant-scoped server paths. Private provider credentials and service-role access are not exposed to public widget code.
Connected calendar access is used to check eligible times and manage requested appointments. Penny should not invent availability that is not stored.
When a deposit is required, Penny can share the link configured by the business. Card details are handled by the payment destination, not collected in chat.
Business-owner control
PennyReply is automation software, not a replacement for professional judgment or a business's responsibility to review its own policies and customer communications.
Privacy policy
What information is collected and how it is used.
AI safety policy
Where AI replies should stop and a person should step in.
SMS policy
Operational messaging, consent, opt-outs, and support.
Still have a data or safety question?
Contact the PennyReply team before putting a workflow live.