tutaco

Tuta AI provides an AI-powered chat solution that integrates with your online store. It’s like having ChatGPT available to your customers through web chat and WhatsApp, helping you sell products and provide support services.
<h4>Key Features</h4>
<ul>
<li>AI-Powered Chat Assistant: Engage customers with an AI that understands your products and can answer questions 24/7</li>
<li>Product Knowledge: The AI assistant learns about your products to provide accurate information</li>
<li>WhatsApp Integration: Connect with customers on their preferred messaging platform</li>
<li>Sales Analytics: Track conversations that lead to sales</li>
<li>Multilingual Support: Communicate with customers in multiple languages</li>
<li>Customizable Appearance: Match the chat widget to your brand</li>
<li>Easy Setup: Get started in minutes with a simple configuration</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8 or higher</li>
<li>PHP 7.4 or higher</li>
<li>WooCommerce 5.0 or higher</li>
</ul>
<h3>External Services</h3>
IMPORTANT: This plugin requires external services to function properly.
Tuta AI is a Software-as-a-Service (SaaS) platform that provides advanced Artificial Intelligence capabilities for customer support and sales automation. Running sophisticated AI models for natural language understanding, real-time conversation management, and product knowledge inference directly within a standard WordPress hosting environment is not feasible due to the immense computational resources required. Such tasks would overwhelm typical web servers, leading to poor site performance and an unreliable user experience.
Therefore, this plugin must connect to Tuta’s dedicated cloud-based API infrastructure, which is optimized for AI workloads and hosted on Supabase (https://supabase.com). This connection is essential for the plugin to operate and deliver high-quality AI-powered chat and support functionalities.
Service Provider Information: 
* Service Name: Tuta AI Platform 
* Service Provider: Tuta AI (https://tuta.co) 
* Infrastructure: Hosted on Supabase cloud platform (https://supabase.com) 
* API Base Domain: Secure cloud-hosted API endpoints (domain varies by deployment)
Why External Services are Required:
<ol>
<li>AI Inference Power: AI models require significant processing power (CPUs, GPUs, specialized hardware) that far exceeds typical WordPress hosting capabilities.</li>
<li>Scalability and Reliability: Cloud infrastructure ensures responsive and reliable AI chat during peak traffic.</li>
<li>Continuous Improvement: Centralized AI engine allows continuous updates without plugin updates.</li>
<li>Specialized Features: WhatsApp integration, analytics, and product knowledge synchronization require optimized external services.</li>
</ol>
Complete List of External API Endpoints Used:
Important Note: All endpoints listed below are relative paths that are appended to the secure API base domain. The plugin connects to Tuta’s cloud-hosted API infrastructure to access these endpoints.
1. Store Registration & Authentication 
* Endpoint: <code>/register-store</code> 
* Purpose: Register your WooCommerce store with Tuta service during plugin activation 
* Data Sent: Store URL, WordPress admin email, store name, platform versions, locale, country, timezone, currency, business hours 
* When: During plugin activation (one-time)
<ul>
<li>Endpoint: <code>/token</code></li>
<li>Purpose: Obtain short-lived (15 minutes) secure access tokens (JWT) for API authentication</li>
<li>Data Sent: Store URL, platform identifier, API key</li>
<li>
When: Before most API calls and when tokens need refresh
</li>
<li>
Endpoint: <code>/rotate-api-key</code>
</li>
<li>Purpose: Securely rotate store’s API key for enhanced security</li>
<li>Data Sent: Store ID, store URL, new API key</li>
<li>
When: When admin triggers API key rotation
</li>
<li>
Endpoint: <code>/verify-token</code>
</li>
<li>Purpose: Verify token validity for incoming API requests</li>
<li>Data Sent: Token, store URL</li>
<li>When: For incoming webhook/API requests validation</li>
</ul>
2. Chat & Conversation Management 
* Endpoint: <code>/messages</code> 
* Purpose: Send customer messages to AI engine and receive AI responses 
* Data Sent: Customer message text, session ID, customer identifier, store ID, conversation context 
* When: Every customer chat interaction
<ul>
<li>Endpoint: <code>/get-or-create-conversation</code></li>
<li>Purpose: Initialize or retrieve existing conversation sessions</li>
<li>Data Sent: Session ID, customer information, store ID</li>
<li>
When: When starting new chat sessions or retrieving existing ones
</li>
<li>
Endpoint: <code>/get-conversation</code>
</li>
<li>Purpose: Retrieve conversation details and history</li>
<li>Data Sent: Session ID or conversation ID</li>
<li>
When: When displaying conversation history in admin
</li>
<li>
Endpoint: <code>/check-conversation-response</code>
</li>
<li>Purpose: Check for new AI responses in ongoing conversations</li>
<li>Data Sent: Conversation UUID</li>
<li>
When: Polling for new responses in active conversations
</li>
<li>
Endpoint: <code>/conversations</code>
</li>
<li>Purpose: Retrieve filtered list of conversations for admin dashboard</li>
<li>Data Sent: Date filters, channel filters, pagination parameters</li>
<li>When: When admin views conversation lists</li>
</ul>
3. AI Agent Configuration 
* Endpoint: <code>/update-agent</code> 
* Purpose: Save and retrieve AI agent configuration (personality, business details, FAQs) 
* Data Sent: Agent settings, business information, product knowledge instructions 
* When: When admin saves AI configuration or plugin fetches current settings
4. Product & Content Synchronization 
* Endpoint: <code>/product-update</code> 
* Purpose: Sync individual product updates to AI knowledge base 
* Data Sent: Product ID, product data (name, description, price, attributes) 
* When: When products are created, updated, or deleted
<ul>
<li>Endpoint: <code>/upsert-products</code></li>
<li>Purpose: Bulk synchronization of product catalog to AI knowledge base</li>
<li>Data Sent: Complete product data in structured format</li>
<li>
When: During initial setup or bulk product synchronization
</li>
<li>
Endpoint: <code>/upsert-pages</code>
</li>
<li>Purpose: Sync website pages/content to AI knowledge base</li>
<li>Data Sent: Page content, URLs, metadata</li>
<li>When: When syncing website content for AI training</li>
</ul>
5. Order & Sales Integration 
* Endpoint: <code>/order-status</code> 
* Purpose: Update order status information for AI context 
* Data Sent: Order ID, status, customer information 
* When: When order status changes
<ul>
<li>Endpoint: <code>/new-order</code></li>
<li>Purpose: Notify AI system of new orders for analytics and context</li>
<li>Data Sent: Order details, customer information, products purchased</li>
<li>When: When new orders are placed</li>
</ul>
6. Analytics & Statistics 
* Endpoint: <code>/get-stats</code> 
* Purpose: Retrieve general chat and AI performance statistics 
* Data Sent: Date ranges, filter parameters 
* When: When admin views analytics dashboard
<ul>
<li>Endpoint: <code>/conversation-stats</code></li>
<li>Purpose: Retrieve detailed conversation analytics and credit usage</li>
<li>Data Sent: Date ranges, conversation filters, breakdown parameters</li>
<li>
When: When admin views conversation analytics and credit usage statistics
</li>
<li>
Endpoint: <code>/stats/ai-sales</code>
</li>
<li>Purpose: Retrieve AI-generated sales revenue and order statistics</li>
<li>Data Sent: Period parameter (month, week, etc.)</li>
<li>When: When admin views AI sales performance metrics</li>
</ul>
7. Subscription & Billing Management 
* Endpoint: <code>/get-plans</code> 
* Purpose: Retrieve available subscription plans and pricing 
* Data Sent: Language preference for localized pricing 
* When: When admin views subscription options
<ul>
<li>Endpoint: <code>/plans</code></li>
<li>Purpose: Retrieve subscription plans (alternative endpoint)</li>
<li>Data Sent: Store identification</li>
<li>
When: When admin accesses plan information
</li>
<li>
Endpoint: <code>/plans/current</code>
</li>
<li>Purpose: Retrieve current active subscription plan details</li>
<li>Data Sent: Store identification</li>
<li>
When: When admin views current plan status
</li>
<li>
Endpoint: <code>/select-plan</code>
</li>
<li>Purpose: Process subscription plan selection</li>
<li>Data Sent: Selected plan details, store information</li>
<li>
When: When admin selects a subscription plan
</li>
<li>
Endpoint: <code>/change-plan</code>
</li>
<li>Purpose: Change existing subscription plan</li>
<li>Data Sent: New plan details, store information</li>
<li>
When: When admin upgrades or downgrades subscription
</li>
<li>
Endpoint: <code>/terminate-subscription</code>
</li>
<li>Purpose: Cancel or modify subscription</li>
<li>Data Sent: Subscription details, cancellation reason</li>
<li>
When: When admin cancels subscription
</li>
<li>
Endpoint: <code>/get-paypro-config</code>
</li>
<li>Purpose: Retrieve payment configuration for subscription management</li>
<li>Data Sent: Store ID for account identification</li>
<li>When: When accessing billing/payment sections</li>
</ul>
8. WhatsApp Integration 
* Endpoint: <code>/get-whatsapp-config</code> 
* Purpose: Retrieve WhatsApp integration configuration and status 
* Data Sent: Store ID for account identification 
* When: When accessing WhatsApp settings or checking connection status
<ul>
<li>Endpoint: <code>/sync-whatsapp-contacts</code></li>
<li>Purpose: Synchronize WhatsApp contacts with Tuta system</li>
<li>Data Sent: Store ID, contact synchronization parameters</li>
<li>
When: When admin triggers WhatsApp contact synchronization
</li>
<li>
Endpoint: <code>/sync-whatsapp-history</code>
</li>
<li>Purpose: Synchronize WhatsApp conversation history</li>
<li>Data Sent: Store ID, history synchronization parameters</li>
<li>When: When admin triggers WhatsApp history synchronization</li>
</ul>
Data Privacy and Security: 
* All communication uses HTTPS encryption 
* Short-lived JWT tokens (15 minutes) for enhanced security 
* No sensitive customer data stored permanently on external servers 
* Conversation data used only for AI response generation and analytics 
* Compliance with data protection regulations
Legal Information: 
* Terms of Service: https://tuta.co/terms 
* Privacy Policy: https://tuta.co/privacy
By using the Tuta AI plugin, you acknowledge and agree to these data transfers and the use of our external services as necessary for the plugin’s functionality and the provision of advanced AI features.

Tuta AI

Integrate advanced AI-powered customer support chat for free. Tuta AI helps you sell products and provide support services.

cognitiveclass

Add this plugin to your site and let IBM watsonx Assistant help you better support your customers. In a few minutes, you can train watsonx Assistant to answer frequently asked questions, provide useful information and help them navigate your website. And if they want to talk to a human, the plugin can connect them to a real operator via telephone.
This plugin uses IBM watsonx Assistant (formerly Watson Conversation) on the IBM Cloud. You can use it with an IBM Cloud Lite account free of charge and without a need to provide a credit card.
Currently supported features:
<ul>
<li>Take advantage of <a href="https://console.bluemix.net/docs/services/conversation/dialog-overview.html#multimedia" rel="nofollow ugc">Rich responses</a> to add images, pauses, and clickable responses to your chatbot</li>
<li>Use user’s account data such as name in chatbot dialog</li>
<li>Easy VOIP calling powered by Twilio for users to contact a real person if they wish</li>
<li>Simple plugin setup to get your watsonx Assistant chatbot available to users as soon as possible</li>
<li>Control usage of the watsonx Assistant service directly from the plugin settings page</li>
<li>Choose the pages and posts you want the visitors to see the chat bot on</li>
<li>Customize the appearance of the chat box to your preference</li>
</ul>

Chatbot with IBM watsonx Assistant

This plugin allows you to easily add chatbots powered by IBM watsonx Assistant to your website.

Tuta AI vs Chatbot with IBM watsonx Assistant