FAQ
Frequently Asked Questions
Answers about Ragger, how it works, compliance, and deployment.
Ragger is AI customer support trained on your website. It learns your approved website pages and documents and answers customer questions instantly using only that content. It does not use the internet. It does not guess. It stays aligned with your published information.
You connect your website and approved documents. Ragger indexes that content. It generates responses using only approved material. When required, conversations can be escalated to your team. No complex setup. No training cycles.
Ragger can answer questions about: Pricing and fees; Policies and terms; Booking and cancellations; Schedules and availability; General enquiries. It works best where answers already exist in written content.
Ragger works particularly well in industries with clear written rules and documentation, including: Travel Insurance — Coverage queries, Claims guidance, Emergency procedures, Policy wording. Ecommerce — Delivery and returns, Product details, Order processes, Terms and conditions. Healthcare — Appointment information, Patient guidance, Policies and procedures. Sensitive or regulated queries can be escalated.
No. Ragger only uses approved website pages and documents provided by the customer.
No. If Ragger cannot find a confident answer in approved content, it will not guess. The query can be escalated.
No. Ragger supports your team by handling repeat and high-volume questions. Your team remains in control.
Pricing depends on: Website traffic; Interaction volume; Deployment model; Integration complexity. We provide tailored pricing after a short discovery call. To receive a quote, please book a demo.
Ragger can be deployed in two ways: Integrated within your existing infrastructure (including Azure environments). Hosted within secure enterprise-grade cloud platforms. Deployment is aligned with your security and compliance requirements.
Yes. Ragger can integrate with: Azure-hosted environments; Umbraco CMS; API-based architectures; Enterprise web platforms. Integration can be configured to align with your infrastructure and security policies.
Yes. Ragger is designed to operate in line with UK GDPR and EU GDPR principles. It supports: Data minimisation; Purpose limitation; Secure processing; Configurable retention policies; Access controls. A Data Processing Agreement (DPA) can be provided where required.
Ragger can be deployed within secure cloud environments appropriate for regulated industries. Hosting location and architecture can be aligned with your data residency and compliance requirements. Please contact us to discuss specific hosting preferences.
Yes. Ragger supports encryption: In transit (HTTPS/TLS); At rest within secure hosting environments. Security configurations can be aligned with enterprise requirements.
Ragger stores only the data required to operate the chatbot service. This may include: Chat interaction content; Anonymous session identifiers; Configuration settings. It does not use marketing or behavioural tracking cookies. A temporary anonymous session ID may be generated to maintain an active conversation. This ID: Is randomly generated; Does not identify the individual user; Is not used for advertising. Retention policies can be configured to meet compliance requirements.
Operational purposes refers strictly to technical functionality required to provide the chatbot service, including: Maintaining a live chat session; Ensuring system stability; Preventing misuse or abuse; Supporting compliance and audit requirements; Improving service reliability. It does not include advertising or marketing profiling.
Chatbot interactions may be monitored in real time or retrospectively for: Compliance and regulatory requirements; Quality assurance; Service performance monitoring; Abuse prevention; Audit requirements. Monitoring is limited to operational and compliance purposes. Chat data is not used for advertising profiling or sold to third parties. Monitoring configurations can be aligned with your legal and compliance policies.
You do. Customers retain ownership of their content and chatbot interaction data. Ragger acts as a service provider and processes data in accordance with agreed contractual terms.
No. Ragger generates responses based only on approved website and document content. It does not approve claims, override policy rules, or make binding decisions. Business decisions remain with the organisation.
Yes. Ragger can be configured to: Escalate sensitive topics; Restrict certain categories; Apply compliance-specific handling rules; Route conversations to human agents. This is particularly important for travel insurance claims and healthcare scenarios.
If Ragger cannot confidently answer using approved content, it will not guess. You can contact us directly here.
Ragger is a product of Recognise Design Limited. Company number: 08633423. Registered in England and Wales.
Can't find what you need? Get in touch.