Odoo WhatsApp AI integration connects a WhatsApp Business API account to Odoo CRM, sales and support modules using AI intent classification to route messages, create leads, trigger workflow automations and send templated responses automatically. UK businesses using this integration reduce manual WhatsApp response time from 4 hours to under 2 minutes for routine enquiries.
Last updated: May 2026
Odoo WhatsApp AI integration is a bidirectional connection between your WhatsApp Business API account and your Odoo ERP, with an AI layer that classifies incoming messages, decides what action to take, and either responds automatically or creates the right Odoo record for human follow-up. It is not the same as Odoo's built-in WhatsApp module, which allows Odoo users to send template messages from within Odoo. The AI integration goes further: it listens to inbound messages, understands what the sender wants, and acts on that understanding inside Odoo without human intervention for routine message types.
The integration architecture has three layers. The first is the WhatsApp Business API connection - a webhook listener receives every inbound message from your WhatsApp Business number and passes it to the processing pipeline. The second is the AI intent classification layer - a large language model (OpenAI function calling or Anthropic Claude tool use) reads the message, determines the sender's intent (new enquiry, price request, appointment booking, order status query, complaint, or general conversation), and extracts any structured data present in the message (name, email, service interest, preferred time, order reference). The third is the Odoo integration layer - based on the classified intent, the system takes action in Odoo using the JSON-RPC API: creating a CRM lead, updating a contact record, triggering a sales workflow, querying an order, or creating a support ticket in Helpdesk.
The Odoo modules involved are Discuss (which provides the native Odoo WhatsApp thread interface if using Enterprise), CRM (for lead creation and pipeline management), Sales (for quotation triggering), Contacts (for contact creation and deduplication), and optionally Helpdesk (for complaint and support routing) and Calendar (for appointment booking). The integration is built on top of Odoo's official API, meaning it works alongside your existing Odoo setup without modifying core code and persists through Odoo version upgrades.
What messages are handled automatically vs. routed to a human:
The system is configured with a set of intent categories and associated automation rules during the implementation phase. Routine enquiries - requests for a quote, questions about services, requests to book a callback or appointment, order status queries - are handled with automatic responses and Odoo record creation. Complex or ambiguous messages, complaints, and any message the AI classifies with low confidence are routed to a human agent queue in the Odoo Discuss module or your preferred channel (email notification, internal message, or parallel webhook to a tool like GoHighLevel). The handover is smooth: the human agent sees the full conversation history, the AI-classified intent, and the Odoo records already created, rather than starting from scratch.
Template messages and session messages:
WhatsApp Business API distinguishes between two message types with different compliance requirements. Template messages (HSMs) are pre-approved by Meta for outbound use - you submit the template wording for approval before using it, and once approved it can be sent to any opted-in contact. Session messages are free-form replies within a 24-hour customer service window opened when a user messages you first. The AI integration uses template messages for outbound automated responses (confirmation messages, appointment reminders, quote follow-ups) and session messages for conversational responses within an active window. Understanding this distinction is important for compliance design.
AI intent classification is the core intelligence of the Odoo WhatsApp integration. When a message arrives from a WhatsApp contact, the LLM reads the full message text (and any conversation history to provide context) and performs a structured classification task: it identifies the primary intent, extracts any structured data present in the message, and returns a JSON object with the classified intent, extracted fields, and a confidence score.
The classification uses OpenAI function calling (or Anthropic Claude tool use), which is a technique that forces the model to return a structured JSON response rather than free-form text. This is critical for automation - the downstream Odoo integration needs clean structured data, not prose. The function definition specifies the intent categories your business uses, the fields to extract for each intent, and any validation rules (for example, a UK mobile number must match the 07XX pattern).
An example of the classification flow for a typical UK SME:
A contact messages: "Hi, I run a small restaurant in Harrow and I am interested in getting a chatbot for taking bookings. Can you tell me how much it costs and how long it takes to set up?"
The LLM classification returns: intent = new_lead, extracted fields = {business_type: "restaurant", location: "Harrow", service_interest: "chatbot", specific_question: ["pricing", "timeline"]}, confidence = 0.97.
The Odoo integration then: creates a new CRM lead with the contact's WhatsApp number, business type, location and service interest; tags the lead with the specific question topics; triggers an automated WhatsApp response with a pre-approved template that acknowledges the enquiry, states typical pricing and timeline, and asks for their name and the best time for a call; and notifies the assigned sales person via Odoo internal message that a new qualified lead has arrived, with the conversation pre-populated.
The sales person's first action is a phone call or follow-up WhatsApp message - they are not doing data entry, they are doing the high-value work. The 4-hour-to-2-minute improvement in response time is not because a human responded faster - it is because the AI sent a meaningful, personalised first response within seconds of the original message, and the human follow-up starts from a warm, already-qualified lead rather than a cold inbox message.
Handling conversation context:
The AI maintains conversation context across a WhatsApp session. If a contact sends multiple messages in a conversation, the classification engine reads the full thread to understand the evolving intent. A contact who starts by asking about pricing and then mentions they have an urgent project this week would be classified differently from a contact who mentioned the same query with no urgency signal. The context window for the LLM can be configured to include the last N messages, balancing accuracy against API cost.
Confidence thresholds and escalation:
Every classification returns a confidence score. Configurations typically set a threshold of 0.85 - messages classified with confidence above 0.85 proceed to automated handling; messages below the threshold are routed to a human agent queue with the AI's best-guess classification shown as context. This prevents the system from taking confident wrong actions on ambiguous messages, while still automating the clear-cut majority. In practice, 70-80% of inbound WhatsApp messages from a business context clear the 0.85 confidence threshold on day one; this rises to 85-90% after two to four weeks of calibration using the specific message patterns your contacts send.
| Intent Category | Example Message Signal | Data Extracted | Odoo Action Triggered | Automated or Human |
|---|---|---|---|---|
| New enquiry / lead | "I'm interested in your services, can you tell me more?" | Business type, service interest, location, contact name | CRM lead created, assigned to sales rep, tagged by service line | Auto response + human follow-up |
| Pricing request | "How much does X cost?" / "Do you have a price list?" | Service or product type, quantity, timeline | CRM lead created, draft quotation pre-populated if enough data | Auto response with pricing info |
| Appointment booking | "Can I book a call / consultation / appointment?" | Preferred date, time, service type | Calendar event created, confirmation template sent | Fully automated |
| Order status query | "Where is my order?" / "When will my delivery arrive?" | Order reference, customer number | sale.order + stock.picking queried, status returned via WhatsApp | Fully automated |
| Complaint or issue | "I have a problem with..." / "I'm not happy with..." | Order or service reference, nature of issue | Helpdesk ticket created, priority flagged | Human queue with context |
| General / ambiguous | Mixed intent or unclear request | Partial extraction only | Routed to human agent queue in Discuss | Human only (below 0.85 threshold) |
The most valuable use cases for Odoo WhatsApp AI in UK businesses fall into three categories: inbound lead capture for service businesses, order and booking management for transactional businesses, and customer service deflection for businesses with high inbound query volumes. The integration delivers the highest ROI in businesses where WhatsApp is already an active customer channel but the volume of messages has outgrown the capacity of a person to handle them manually.
Inbound lead capture for service businesses:
For UK SMEs offering professional or trade services - consultancies, law firms, accountancies, IT services, tradespeople, healthcare clinics - WhatsApp is increasingly used by prospective clients to make first contact. These businesses often have a team too small to staff a dedicated WhatsApp inbox, so messages sit unanswered for hours. The AI integration creates a CRM lead in Odoo within seconds of the enquiry arriving, sends an immediate acknowledgement, and classifies the lead by service interest and urgency so the sales or enquiries team can prioritise follow-up. The response time improvement from 4 hours to under 2 minutes applies to this use case and is directly measurable in conversion rate improvement.
Appointment booking for healthcare and professional services:
When connected to Odoo Calendar, the integration enables appointment booking via WhatsApp. A patient or client messages to book an appointment, the AI identifies available slots from the Odoo Calendar and presents them in a WhatsApp interactive message, the contact selects a slot, and the Calendar event is created in Odoo automatically. The contact receives a confirmation message. For practices and clinics handling 20-50 booking requests per week via WhatsApp, this eliminates an estimated 15-25 minutes of admin per booking.
Order status queries for product businesses:
For UK businesses with an Odoo Sales or eCommerce setup, a significant proportion of inbound WhatsApp messages from existing customers are order status queries: "Where is my order?", "When will my delivery arrive?", "Can I change the delivery address?". The AI integration queries the Odoo sale.order and stock.picking APIs in real time and returns the current order status, tracking information and expected delivery date in the WhatsApp reply - without any human intervention. Customer service agents are freed from handling repetitive status queries to focus on actual problems.
Post-sale follow-up and upsell sequences:
Using outbound template messages (PECR-compliant, sent only to opted-in contacts), the integration can trigger Odoo-driven WhatsApp sequences: a satisfaction check after a service delivery, a review request at the appropriate interval, a renewal reminder before a subscription expires, or a targeted upsell offer based on the customer's purchase history in Odoo. These sequences are triggered by Odoo automation rules - for example, when a sale order reaches the done state and the product category matches a specific service type, the WhatsApp follow-up sequence starts automatically.
Parallel GoHighLevel integration:
For businesses running both Odoo and GoHighLevel, the same WhatsApp webhook can deliver lead data to both platforms simultaneously. When a new lead intent is classified, the integration creates a CRM lead in Odoo and sends the same contact data to GoHighLevel via webhook, triggering GHL automation sequences in parallel. This is particularly useful during a transition period where some business functions are in GHL and others are in Odoo, or where the Odoo CRM handles the delivery team's work and GHL handles the marketing automation side.
Odoo WhatsApp AI integration costs from £4,000 for a focused CRM and lead routing implementation with intent classification. Full multi-flow implementations covering lead capture, booking, order queries and outbound sequence triggering cost £6,000-£12,000. The cost is driven by the number of intent categories and Odoo integrations in scope, the complexity of the response templates, and the number of workflow automations to configure in Odoo.
| Implementation Scope | Typical Cost Range | Timeline |
|---|---|---|
| CRM lead creation + intent routing + auto-response (2-3 intents) | £4,000-£5,500 | 5-6 weeks |
| CRM + Calendar booking + order status queries (4-6 intents) | £5,500-£8,000 | 6-7 weeks |
| Full multi-flow: CRM + Booking + Order + Helpdesk + GHL parallel (6+ intents) | £8,000-£12,000 | 7-9 weeks |
| Enterprise: multiple WhatsApp numbers + team routing + CRM pipeline rules | £10,000-£18,000 | 8-12 weeks |
Timelines include the Meta WhatsApp Business API approval process, which adds 1-2 weeks compared to a standalone AI chatbot implementation. If you already have an approved WhatsApp Business API account, the timeline reduces by one to two weeks.
Ongoing costs:
WhatsApp Business API message costs depend on message category and country. For the UK, conversation costs in 2026 are approximately $0.04-$0.08 per 24-hour conversation window (Meta pricing, paid in USD regardless of billing currency). LLM API costs for intent classification are approximately £0.001-£0.003 per message classified. For a business handling 500 inbound WhatsApp conversations per month, total variable costs are under £60 per month. There is no ongoing platform licence fee for the integration code - you own the implementation.
ROI for a service business handling 100 WhatsApp leads per month:
At 100 WhatsApp leads per month with a 30-minute average handling time per lead (reading, qualifying, responding, creating Odoo record, follow-up scheduling), manual processing costs 50 hours per month. At a staff cost of £25 per hour (loaded), that is £1,250 per month. The AI integration reduces this to approximately 10 hours per month (handling escalated and complex leads only). Monthly saving: approximately £1,000. A £4,000-£5,500 implementation recovers build cost in four to six months, after which the saving is recurring. Lead conversion improvements from faster response time (industry data: leads contacted within 5 minutes are 9x more likely to convert than those contacted after 30 minutes) are not included in this calculation and typically dwarf the staff cost saving in commercial impact.
UK GDPR and PECR compliance for Odoo WhatsApp AI integration requires careful design from the outset. The compliance obligations differ depending on whether messages are inbound (contact-initiated) or outbound (business-initiated marketing), and whether the business-to-consumer or business-to-business distinction applies.
Inbound messages - lawful basis:
When a contact messages your WhatsApp Business number, the lawful basis for processing that communication and the data it contains is generally legitimate interests (UK GDPR Article 6(1)(f)) for business enquiries, or contract performance (Article 6(1)(b)) for existing customers making service or order queries. The processing is expected: the contact chose to message your business number. The data collected - message content, WhatsApp number, any personal information voluntarily shared in the message - should be stored in Odoo only to the extent necessary for responding to the contact and managing the resulting business relationship.
Outbound marketing messages - PECR consent requirement:
The Privacy and Electronic Communications Regulations (PECR) govern electronic marketing messages, including WhatsApp. Under PECR, sending outbound WhatsApp marketing messages to UK individuals requires prior explicit consent - even to existing customers. This is a stricter rule than the soft opt-in that applies to email marketing under PECR. WhatsApp marketing messages require a clear opt-in mechanism: a checkbox on your enquiry form, a verbal opt-in recorded in Odoo, or a WhatsApp opt-in flow where the contact sends a specific keyword to confirm consent.
Outbound messages to business contacts (B2B) where the WhatsApp number is a business number (not a personal number) are outside the individual subscriber protection of PECR. In practice, distinguishing business from personal WhatsApp numbers is difficult - the same 07XX number may be the owner's personal and business phone. The safest approach for UK SMEs is to treat all contacts as requiring PECR consent for outbound marketing, regardless of B2B or B2C classification, unless you have clear evidence the number is a business landline or switchboard.
Data residency and Meta data processing:
WhatsApp processes message data on Meta's infrastructure, which includes servers in the United States and the European Union. Under UK GDPR, sending personal data to Meta's US infrastructure is a restricted transfer. Meta provides standard contractual clauses (SCCs) and a Data Processing Agreement for WhatsApp Business API users. You should review Meta's DPA, ensure SCCs are in place for UK-to-US transfers, and document this transfer in your Records of Processing Activities (ROPA). The message content itself is end-to-end encrypted in transit; Meta's servers see metadata (sender number, timestamp, message type) rather than the content of encrypted messages, though this distinction matters more for consumer WhatsApp than for Business API implementation.
Data retention in Odoo:
Message content and lead data created from WhatsApp conversations should be subject to your standard CRM data retention policy. For UK businesses, a reasonable retention period for CRM records is 3-5 years from last contact, with a review process for inactive contacts. Contacts who request erasure under UK GDPR Article 17 must have their WhatsApp-sourced CRM record deleted alongside any other personal data held in Odoo. The integration should include a documented process for handling erasure requests that covers the WhatsApp conversation logs, the Odoo CRM record, and any LLM API cache (confirm with your LLM provider that API-processed data is not retained beyond your DPA terms).
Privacy notice:
Your privacy notice should describe that WhatsApp is used as a communication channel, that messages may be processed using AI classification tools, and that message data is stored in your CRM. A brief statement on your website WhatsApp widget or business profile is sufficient for inbound enquiries. For outbound marketing sequences, the consent mechanism itself serves as the disclosure - the opt-in language should clearly describe what messages the contact will receive.
| Compliance Requirement | Applies To | Action Required | ICO / Legal Reference |
|---|---|---|---|
| Lawful basis for inbound processing | All inbound messages | Document legitimate interests or contract performance basis in ROPA | UK GDPR Article 6(1)(b) / 6(1)(f) |
| Explicit consent for outbound marketing | Outbound WhatsApp to UK individuals (B2C and ambiguous B2B) | Implement opt-in mechanism before sending any template marketing sequence | PECR Regulation 22; ICO direct marketing guidance |
| Meta DPA and SCCs for UK-to-US transfer | All WhatsApp Business API users | Accept Meta's DPA, confirm SCCs or UK IDTA are in place, document in ROPA | UK GDPR Chapter V; ICO international transfers guidance |
| Privacy notice disclosure | All contacts messaging via WhatsApp | Add WhatsApp + AI processing statement to privacy notice and business profile | UK GDPR Articles 13-14 (transparency) |
| Data retention and deletion | Conversation logs and CRM records | Apply retention policy (3-5 years); build erasure request process covering logs + CRM + LLM cache | UK GDPR Articles 5(1)(e), 17 |
| LLM API data processing agreement | AI classification layer (OpenAI / Anthropic) | Confirm DPA with LLM provider; verify no training on customer message data | UK GDPR Article 28 (processor contracts) |
Odoo WhatsApp AI integration takes 5-7 weeks from project start to go-live for a standard CRM + intent routing implementation. The timeline is longer than a comparable integration without WhatsApp (which would take 3-4 weeks) because of the Meta WhatsApp Business API approval process, which is outside our control and takes 1-2 weeks.
Week 1 - Discovery and Meta business verification initiation: We run a discovery workshop to define the intent categories, map the Odoo workflow actions, design the response templates, and confirm the PECR compliance approach for any outbound messages. Simultaneously, we begin the Meta business verification process. Meta requires: a verified Facebook Business account, your business registration number (UK Companies House number for limited companies), a business address matching Companies House records, and a verified business phone number. We guide you through the submission - businesses that have their Companies House details ready typically complete verification within 5-10 working days.
Weeks 2-3 - Development: While Meta verification is processing, we build the webhook integration, intent classification pipeline, Odoo API integration layer, and response template system. We configure the Odoo CRM lead creation logic, contact deduplication rules, and any workflow automation triggers that fire based on classified intents.
Week 3-4 - Internal testing and template submission: We test the full pipeline with a test WhatsApp Business number. Simultaneously, we submit your approved response templates to Meta for review. Meta template approval takes 1-5 business days for standard business templates; templates with promotional content take longer. We advise on template wording to maximise the likelihood of first-submission approval.
Week 5-6 - Supervised go-live and calibration: Once Meta verification and template approvals are complete, we switch the integration to your live WhatsApp Business number. Your team monitors inbound classification results for the first two weeks, flagging any misclassifications. We refine the intent classification prompts and confidence thresholds based on the patterns in your real message data. After two weeks of supervised operation, most teams are comfortable moving to exception-only monitoring.
Week 6-7 - Handover and documentation: We produce operational documentation covering how to add new intent categories, how to submit new template messages, how to handle the exception queue in Odoo Discuss, and how to extract WhatsApp lead data from the Odoo CRM for reporting. We provide a three-month support SLA for integration issues and any changes arising from Meta API updates.
The most common cause of timeline extension is delayed Meta business verification - particularly for businesses whose Facebook Business account was set up informally without matching the Companies House business name exactly. We recommend starting the Meta verification process as the first step in the project, even before contract signature, to prevent it from becoming a critical path blocker.
| Week | Phase | Key Deliverables | Dependencies / Blockers | Who Acts |
|---|---|---|---|---|
| 1 | Discovery + Meta verification start | Intent category map, Odoo workflow design, response template drafts, Meta verification submission | Client provides Companies House number, Facebook Business account access, trading address | Softomate + client |
| 2-3 | Development | Webhook listener, AI classification pipeline, Odoo JSON-RPC integration layer, CRM lead logic, deduplication rules | Meta verification in progress (parallel track - no dependency) | Softomate |
| 3-4 | Internal testing + template submission | End-to-end test on test WhatsApp number, template messages submitted to Meta for approval | Meta template review: 1-5 business days for standard templates | Softomate |
| 5 | Meta approvals complete + cutover | Business verification confirmed, templates approved, live WhatsApp number connected | Meta verification outcome (critical path if delayed) | Meta + Softomate |
| 5-6 | Supervised go-live and calibration | Live classification monitoring, misclassification log, prompt and threshold refinements | Client team available to flag edge-case messages daily | Softomate + client |
| 6-7 | Handover and documentation | Operational runbook, intent management guide, template submission guide, 3-month support SLA activated | Calibration phase complete | Softomate |
You need a WhatsApp Business API account. The WhatsApp Business app (available free from the App Store or Google Play) does not support webhooks, automated responses or third-party integrations. The Business API is a separate product accessed through a Business Solution Provider (BSP) or directly via Meta. It requires Meta business verification and a phone number not already registered to the Business app. Some BSPs include a monthly fee of £30-£80; direct API access via Meta is free aside from per-conversation message costs. We guide you through BSP selection or direct API setup as part of the implementation.
The AI handles text messages, which covers the majority of inbound WhatsApp business enquiries. It can also process voice messages (using OpenAI Whisper to transcribe audio to text before classification), images with text descriptions (product photos sent by a contact with a query), and document attachments (PDF quotes or invoices a contact sends for review). Interactive message responses - when you send a contact a list of options and they tap a selection - are handled natively by the integration and do not require AI classification. The system does not handle video messages in the initial implementation scope.
Yes. When a contact's message is classified as a pricing or quotation request and they provide sufficient information (product or service type, quantity, delivery requirements), the integration can create a draft Odoo sales quotation pre-populated with the extracted information and assigned to the relevant sales person for review and sending. The draft quotation appears in the Odoo Sales module in the existing customer's or new lead's record. This works best for businesses with relatively standard products or service packages where the key quotation variables can be extracted from a WhatsApp message reliably.
Meta business verification confirms that your WhatsApp Business API account is associated with a legitimate registered business. You provide your legal business name (must match official registration), business registration number, website URL, and a business phone or email for verification. Meta cross-references this against public business records. For UK businesses, Companies House registration details are the most reliable data source. Verification typically takes 5-10 business days for straightforward cases. Businesses where the Facebook Business account name differs from the Companies House name, or where the business address is a registered office rather than a trading address, sometimes experience longer review times. Start the process early.
Messages where the AI classification returns a confidence score below the configured threshold (typically 0.85) are routed to the human agent queue in Odoo Discuss with a notification to the assigned team member. The agent sees the message, the AI's best-guess classification and a brief explanation of why confidence was low (ambiguous intent, unusual phrasing, mixed intents in a single message). The agent handles the message manually and their response is logged for calibration. Over time, repeated message patterns that initially scored low confidence are added to the intent training data, improving the system's handling of your specific contact base.
Yes, using pre-approved Meta template messages. Outbound messages triggered from Odoo (appointment reminders, order confirmations, follow-up sequences) are sent using Meta-approved templates, which can include personalisation variables such as the contact's name, appointment time or order number drawn from Odoo records. The trigger is an Odoo automation rule - for example, when a Calendar event status changes to confirmed, send a WhatsApp confirmation template to the attendee's contact number. Outbound session messages (free-form, within a 24-hour window) can also be sent by team members directly from the Odoo Discuss interface on Enterprise.
Contact information and lead data extracted from WhatsApp conversations is stored in Odoo CRM and Contacts, subject to your existing Odoo data retention and access control policies. Conversation history is stored in Odoo Discuss (if using Enterprise) or in your webhook log database. Raw message logs should be retained only as long as operationally necessary and deleted per your retention policy - typically 12-24 months for CRM conversation logs. Meta's WhatsApp Business API DPA covers the transfer and processing of message metadata on Meta's infrastructure. You must ensure SCCs or the UK IDTA are in place for any UK-to-US data transfer via the API, and document this transfer in your ROPA.
Yes. If you are on Odoo Enterprise and using the native Odoo Discuss WhatsApp feature (which allows sending template messages from within Odoo), this AI integration complements rather than replaces it. The AI integration adds inbound processing intelligence - reading and classifying incoming messages, creating CRM records, triggering automations - which the native Discuss WhatsApp feature does not provide. The integrations coexist at the API level: both use the same WhatsApp Business API account, with the webhook router directing inbound messages to the AI pipeline and the Odoo Discuss module handling outbound messages initiated by your team.
Odoo WhatsApp AI integration addresses one of the most persistent friction points in UK SME sales and customer service: the gap between customers who want instant responses on WhatsApp and businesses that cannot staff a real-time WhatsApp inbox. The 4-hour-to-2-minute response time improvement is the headline figure, but the deeper value is in lead quality - every classified WhatsApp enquiry arrives in the Odoo CRM with context, intent data and conversation history, so your team can follow up faster and more relevantly than if they were responding to a raw message. The compliance framework for UK GDPR and PECR is manageable with proper consent design for outbound messages and a DPA in place with Meta. Five to seven weeks from project start to go-live, including the Meta verification overhead that most businesses underestimate. See our Odoo AI integration London page to start scoping your implementation, or our Odoo ERP implementation London page if you are also considering a broader Odoo rollout.
Softomate delivers Odoo AI integration for London businesses from £3,000. Book a free discovery workshop to scope your use case.
Deen Dayal Yadav is the founder of Softomate Solutions, a London AI automation agency based in Stanmore. He has delivered over 200 AI automation and Odoo integration projects for UK businesses.
Softomate also builds standalone AI chatbots that integrate directly with Odoo CRM, Helpdesk, and Sales modules. See our AI chatbot development service for pricing from \xc2\xa33,000.
Softomate also builds standalone AI chatbots that integrate directly with Odoo CRM, Helpdesk, and Sales modules. See our AI chatbot development service for pricing from \xc2\xa33,000.
We protect the real names of all clients featured in examples and case studies. Every testimonial is from a real client.
More from the blog
Work with us
Book a free 30-minute discovery call with DD and get a personalised automation roadmap.
Softomate Solutions Limited
Deen Dayal Yadav
Online
We use essential cookies to keep the site running. With your permission, we also use analytics cookies to understand how visitors use our site so we can improve it. No data is sold. Privacy Policy
