How Clinqly behaves around your customers, your team and your systems.
Operating principles, written plainly. These are the rules the product follows, not marketing.
Approved business information
Clinqly answers customers only from information your business has approved: services, prices, hours, what to expect. It does not answer from the open internet, and when it does not know something it says so and hands the enquiry to your team.
Human judgement
Sensitive, specialist and uncertain situations reach a named person with the full context. Prepared is not sent: where a person should decide, Clinqly drafts and waits. Your team can read every conversation and take over at any point.
Specialist boundaries
Clinqly records what a customer says (“the boiler is making a banging noise”) for the person who will handle it. It never diagnoses, gives professional advice or decides what a customer needs. Industries with their own safety rules, such as health services, carry them in their industry pack. Urgent situations are signposted to your team on every channel.
Your system of record stays the record
Clinqly runs the operational layer around the software you already use and does not write specialist records to it. We do not claim two-way integrations with booking software, CRMs or industry systems.
Data handling principles
Customer data is used to run the journey the customer started. Access is limited to what a role needs, and each location's data stays with that location. We do not sell your data.
Auditability
Conversations, automated messages, handovers and state changes are recorded against the journey, so your team can see what happened and who owned it.
We do not list certifications, accreditations or compliance badges we do not hold. If you need a specific assurance, ask us and we will tell you exactly where we stand.
You are the data controller
For the enquiries your customers send, your business is the data controller and Clinqly is the processor. You decide what Clinqly can say and do, and we process that data only to run the service for you.
Our full policies set out what we collect, how we use it, and the sub-processors we rely on. We keep them plain enough to read.
If you need a DPA, ask before you go live
If your organisation requires a Data Processing Agreement, talk to us before going live. Our data-processing terms are being finalised and are subject to legal review, and we will work through your requirements with you directly.