Haboo Tata WhatsApp Integration
by Haboo Technologies Pvt Ltd https://www.habootechnologies.com$ 1.00
Tata WhatsApp Sessions,
Dual Line â One CRM
Manage two independent Tata WhatsApp Business lines from a single Odoo interface â with session states, template message dispatch, SLA tracking, and direct CRM opportunity linkage.
tata.whatsapp.session) and Line 2 (tata.whatsapp.session.2) operate as separate models â each with its own sessions, state machine, and agent assignment.
retail_product_inquiry, abandoned_cart_enquiry_) directly from a session record without leaving Odoo.
sla.whatsapp.session model links a Line 1 and Line 2 session together â enabling cross-line SLA measurement and reporting.
opportunity_id linking it to a CRM lead â so WhatsApp conversations are tied to the correct sales pipeline record.Two Tata WhatsApp lines managed from one Odoo install
The Tata Communications WhatsApp Business API lets enterprises send and receive WhatsApp messages at scale. This module brings that capability inside Odoo with a dual-line architecture â Line 1 and Line 2 each have their own session model, state machine (New / Running / Close), and agent assignment, so different teams or use cases can operate independently on separate numbers.
Agents dispatch approved WhatsApp templates (retail product inquiry and Shopify abandoned cart) directly from session records. A dedicated SLA Session model links a Line 1 and Line 2 session together for cross-line tracking. All sessions link to CRM opportunities, keeping WhatsApp conversations part of your sales pipeline.
Dual-line session models (Line 1 + Line 2)Template dispatch: retail inquiry + abandoned cartSLA session model linking both linesCRM opportunity linkage on all sessionsSession opens, agent dispatches, SLA tracked
An inbound WhatsApp on either line creates a session record with customer name, number, agent assignment, state, and CRM opportunity link â ready for the assigned agent.
From the session form, agents dispatch a retail product inquiry or abandoned cart WhatsApp template with one click â no separate Tata dashboard needed.
The SLA session model links both lines for a single conversation â enabling accurate response time reporting across the full customer journey regardless of which line handled each leg.
Everything the module gives you
Line 1 (tata.whatsapp.session) and Line 2 (tata.whatsapp.session.2) are independent models â each with its own session list, form, state machine, and agent field.
Three states â New, Running, Close â on both lines. The is_close_visible flag controls when the Close button shows, preventing premature session closure.
Two outbound template methods: retail_product_inquiry for standard enquiries and abandoned_cart_enquiry_ for Shopify cart recovery â both sent via the Tata API from the session form.
Each session has a send_message field and product image/file name fields â so agents can share product visuals and documents directly from the session record.
sla.whatsapp.session links a Line 1 session and a Line 2 session in a single SLA record â enabling response-time reporting across the complete conversation regardless of which line handled each leg.
Each session carries an agent_user_id and opportunity_id â so every WhatsApp conversation is owned by a specific agent and tied to the corresponding CRM lead.
The remarks and is_gen_con fields let agents annotate sessions with context flags and free-text notes visible to the whole team.
Who needs this module
Large teams with two dedicated WhatsApp numbers â e.g. sales and support â can manage both lines from a single Odoo install without mixing up conversations.
Teams using this alongside the Haboo Shopify Integration can trigger the abandoned_cart_enquiry_ template directly from a session for real-time cart recovery via WhatsApp.
Operations and QA teams can use the SLA Session model to measure response time across both lines â identifying bottlenecks without building any custom tooling.
Every capability, listed plainly
tata.whatsapp.session (Line 1) and tata.whatsapp.session.2 (Line 2)is_close_visible guard on both linessla.whatsapp.session model linking Line 1 and Line 2 sessions for cross-line SLA measurementagent_user_id and opportunity_id on every session â agent ownership + CRM linkis_gen_con) for agent annotations on every sessionbase, crm, and mail. Requires a Tata Communications WhatsApp Business API account.Our Odoo Services
Need Help?
Questions about installation, configuration, or customisation? We're here â just write to us.
habootechnologies@gmail.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Discuss (mail) • Calendar (calendar) • Contacts (contacts) |
| Lines of code | 1882 |
| Technical Name |
haboo_tata_whatsapp_integration |
| License | OPL-1 |
| Website | https://www.habootechnologies.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module