Product details are displayed in English. Translations coming soon.
apps/plivo-sms-gatewayउदाहरणात्मक पूर्वावलोकन
Plivo SMS Gateway
- platform
- Odoo
- version
- —
- category
- SaaS Tools
- license
- ऑर्डर पर निर्मित
ऐप मैनिफ़ेस्ट
आपके वर्कफ़्लो के अनुरूप बनाया गया
Send bulk and transactional SMS through Plivo from any Odoo record — order confirmations, campaigns and two-way replies, all native.
प्रमुख सुविधाएँ
Native Plivo connection: an sms.plivo.account model holds your Auth ID, Auth Token and sender ID, with a built-in 'Test Connection' button that verifies credentials against the Plivo API before you send a single message.
Send SMS from any record: a 'Send SMS' action button is added to res.partner, sale.order, account.move, helpdesk.ticket and any additional models you specify, pre-filling the recipient number from the record.
Bulk SMS to contact groups: target Odoo mailing lists, tags, or any saved res.partner filter domain, with per-campaign batching and rate limiting to respect your Plivo account throughput.
Auto-SMS on order and business events: Odoo automated actions (base.automation) fire transactional messages on triggers like sale order confirmed, invoice posted, delivery validated or helpdesk ticket resolved.
Template management: reusable SMS templates with QWiB/Jinja-style placeholders (e.g. ${object.partner_id.name}, ${object.amount_total}) that render against the source record so every message is personalized and accurate.
Two-way inbound capture: an authenticated Plivo inbound webhook records replies back into Odoo, threads them onto the originating contact, and can auto-create a CRM activity or helpdesk follow-up.
Delivery status tracking: Plivo status callbacks update per-message fields (queued, sent, delivered, failed, undelivered) in near real time, with an @api.depends compute rolling up campaign totals.
Cost and segment visibility: each message logs its Plivo message UUID, segment count and reported cost, giving finance and marketing a clear per-campaign spend view via list and pivot reports.
Message history and reporting: dedicated list, form and pivot views over the sms.plivo.message model, filterable by user, model, campaign, status and date for auditing and analysis.
Security and access control: outbound sending is gated by ir.model.access.csv rules and dedicated security groups (SMS User vs SMS Manager), with record rules keeping messages scoped per company.
Multi-company and per-company sender IDs: each company can use its own Plivo sender ID / phone number, correctly attributed on both outbound sends and inbound replies.
API-accessible sending: because it is a standard Odoo model, external systems can queue and send SMS through Odoo's XML-RPC / JSON-RPC endpoints, using the same records and audit trail as the UI.
Opt-out and compliance handling: an unsubscribe/opt-out flag on the contact suppresses future marketing sends, keeping bulk campaigns aligned with consent requirements.
Failure logging and retry: failed sends are captured with the Plivo error code and reason, surfaced in the message log, and retryable so transient failures don't silently disappear.
Compatible with Odoo 17, 18 and 19, Community or Enterprise — built against your exact edition and version, not a generic build.
ऑर्डर पर निर्मित, पूरी तरह आपके लिए तैयार
स्वयं सेटअप की ज़रूरत नहीं — ECOSIRE द्वारा निर्मित, इंस्टॉल और समर्थित एक कार्यशील ऐप।
- 1
आप ऑर्डर करते हैं
एक बार के निर्माण मूल्य से शुरू करें। किकऑफ़ पर हम आपके साथ मिलकर दायरा तय करते हैं।
- 2
हम बनाते और इंस्टॉल करते हैं
ECOSIRE इसे आपके Odoo पर बनाता, कॉन्फ़िगर और इंस्टॉल करता है।
- 3
लाइव + समर्थन
आप लगभग 2–4 सप्ताह में लाइव हो जाते हैं, लॉन्च के बाद समर्थन अवधि के साथ।
तकनीकी विनिर्देश
- Odoo संगतता
- Odoo 17, Odoo 18, Odoo 19
- संस्करण
- Enterprise और Community
- लाइसेंस
- LGPL-3.0
- Python आवश्यकता
- Python 3.10+
- डेटाबेस
- PostgreSQL 12+
इस उत्पाद के बारे में
Your team already runs on Plivo. Your business already runs on Odoo. What's missing is the wire between them — so today SMS lives in a separate dashboard, disconnected from the sales orders, contacts and helpdesk tickets that should trigger it. The Plivo SMS Gateway closes that gap. It is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports specifically for your database, turning Plivo into a first-class Odoo messaging channel.
This is not an off-the-shelf download from the Odoo App Store. After purchase, ECOSIRE builds the module against your exact Odoo edition and version (Community or Enterprise, 17, 18 or 19), wires it to your Plivo Auth ID and Auth Token, and ships it as clean, standards-compliant code — a proper __manifest__.py, ORM models extending models.Model, security enforced through ir.model.access.csv and record rules, XML/OWL views, QWeb-ready message logging, and automated actions for event-driven sends. Typical delivery is 2 to 4 weeks.
Under the hood, an sms.plivo.account model stores your credentials and sender ID, and an sms.plivo.message model logs every outbound and inbound message with delivery-status fields kept current by Plivo's status callbacks (an @api.depends compute rolls per-campaign counts and cost). A "Send SMS" action is injected onto res.partner, sale.order, account.move, helpdesk.ticket and any other model you nominate, so a user can text a customer straight from the record they're already looking at. Templates use Odoo's QWeb/Jinja-style rendering, so ${object.partner_id.name} and ${object.amount_total} resolve against the source record — no copy-paste, no wrong numbers.
Bulk campaigns target contact groups, mailing lists or any filtered res.partner domain, batched and rate-limited to respect Plivo throughput and stay within your account limits. Transactional sends fire automatically from Odoo automated actions (base.automation) on the events you care about — order confirmed, invoice posted, delivery shipped, ticket resolved. And because Plivo supports two-way messaging, an authenticated inbound webhook captures replies back into Odoo, threading them onto the originating contact and, optionally, creating a CRM activity or helpdesk follow-up so nothing gets lost.
Everything respects Odoo's multi-company and multi-user model: access is gated by security groups, per-company sender IDs are supported, and every send is attributed to the user and record that triggered it for a full audit trail. You get native reporting, list and pivot views over message history, and the same JSON-RPC/XML-RPC surface as any Odoo model — so external systems can queue SMS through Odoo if you want them to.
ECOSIRE hands over the source, documents it, trains your team, and stands behind it with a support and warranty window. You keep the code.
What you get
- Complete, installable Odoo module source (a properly structured addon with __manifest__.py, models/, views/, security/ and data/) targeting your exact Odoo version and edition.
- Configured and tested Plivo connection in your environment: Auth ID / Auth Token wired in, sender ID(s) set, and a live send/receive verified end to end.
- Automated actions and templates set up for the specific order and business events you nominate (e.g. order confirmation, invoice, dispatch, ticket resolution).
- Inbound two-way webhook configured on your Plivo application and pointed at your Odoo instance, with reply-to-contact threading verified.
- Written documentation: an admin/config guide, a user 'how to send' guide, and a technical README covering the models, security groups and extension points.
- A live training session (recorded) for your admins and end users, covering sending, campaigns, templates and reading the delivery reports.
- A defined post-go-live support and warranty window for bug fixes and configuration adjustments, with a named ECOSIRE contact.
- Source-code ownership: you keep the module code and can maintain, extend or migrate it independently.
Who this is for
Existing Plivo customer moving to native Odoo sending
A team already paying for and sending through Plivo who is tired of switching between the Plivo console and Odoo. They want messages to fire from the sales orders, invoices and contacts that already live in Odoo, using their existing Plivo account and sender IDs — no new vendor, no re-platforming.
Sales / operations manager driving transactional SMS
Owns the customer experience around orders and service. Wants automatic, reliable SMS on key events — order confirmed, out for delivery, ticket resolved — triggered by Odoo automated actions rather than manual work, with delivery status they can trust and a clean audit trail per record.
Marketing lead running bulk campaigns
Runs promotions and announcements to segmented contact groups. Needs to target Odoo mailing lists and tags, personalize with templates, respect opt-outs, and see per-campaign delivery rates and cost in one place instead of exporting lists to an external tool.
Odoo administrator / IT owner
Responsible for the database, security and upgrades. Wants a clean, well-structured addon with proper ir.model.access.csv rules and security groups, multi-company awareness, and code they own so it can be maintained and carried across future Odoo upgrades.
How Plivo SMS Gateway Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Native Odoo sending (SMS from res.partner, sale.order, invoices, tickets) | Included | Partial support | Partial support | |
| Uses your existing Plivo account and sender IDs | Included | Partial support | Partial support | |
| Auto-SMS on order/business events via Odoo automated actions | Included | Partial support | Partial support | |
| Two-way inbound capture threaded onto contacts | Included | Partial support | Not included | |
| Template rendering against the source record (${object...}) | Included | Partial support | Partial support | |
| Per-message delivery status, segment count and cost logging | Included | Partial support | Partial support | |
| Security via ir.model.access.csv, record rules and dedicated groups | Included | Partial support | Partial support | |
| Built for your exact Odoo 17/18/19 edition (Community or Enterprise) | Included | Included | Not included | |
| Source ownership, documentation, training and warranty support | Included | Partial support | Not included |
Frequently Asked Questions about Plivo SMS Gateway
How long does delivery take, and what happens after I buy?
This is a build-to-order module, not an instant download. After purchase, ECOSIRE confirms your Odoo version and edition (Community or Enterprise, 17/18/19) and your Plivo account details, then designs, builds and tests the module for your database. Typical delivery is 2 to 4 weeks depending on the number of trigger events and custom models. We install it in your environment, verify a live send and inbound reply, and hand over the source, documentation and training.
What kind of support and updates do I get after go-live?
Every build includes a defined post-go-live support and warranty window for bug fixes and configuration adjustments, with a named ECOSIRE contact. Because you own the source code, you can maintain and extend it yourself, or engage ECOSIRE for ongoing support, new trigger events, or a version upgrade (for example moving the module from Odoo 17 to 18 or 19) as a follow-on engagement. If Plivo changes an API endpoint or callback format during your warranty window, we adjust the integration.
Do I need my own Plivo account?
Yes. This module connects your existing Plivo account to Odoo — it does not resell messaging. You provide your Plivo Auth ID, Auth Token and a registered sender ID or number, and all SMS traffic and billing run through your own Plivo account. That keeps you in control of throughput, pricing and number registration.
Which Odoo versions and editions does it support?
Odoo 17, 18 and 19, on both Community and Enterprise. We build against your exact version and edition rather than shipping a generic package, so the models, views and security rules match your database. If you are mid-upgrade, tell us the target version and we will build for that.
Can it send SMS automatically from events like a confirmed sales order?
Yes. Transactional sends are driven by Odoo automated actions (base.automation) on the events you nominate — for example sale order confirmed, invoice posted, delivery validated or helpdesk ticket resolved. Each uses a template that renders against the triggering record, so the customer name, order number or amount is filled in automatically. You can also send manually from any record via the 'Send SMS' action.
How does two-way messaging and reply capture work?
Plivo supports inbound SMS, and the module configures an authenticated inbound webhook on your Plivo application pointed at your Odoo instance. Incoming replies are recorded against the sms.plivo.message log and threaded onto the matching contact by phone number. Optionally, an inbound reply can create a CRM activity or a helpdesk follow-up so your team is prompted to respond.
Is this the same as an Odoo App Store module?
No. It is not an off-the-shelf apps.odoo.com download and there is no instant-download claim. ECOSIRE builds it for you as bespoke work, installs it, and supports it. You receive clean, standards-compliant Odoo code — manifest, ORM models, security CSV and record rules, XML/OWL views — that you own and can audit.
Related Modules
कोटेशन का अनुरोध करें
Plivo SMS Gateway
Send bulk and transactional SMS through Plivo from any Odoo record — order confirmations, campaigns and two-way replies, all native.
- Native Plivo connection: an sms.plivo.account model holds your Auth ID, Auth Token and sender ID, with a built-in 'Test Connection' button that verifies credentials against the Plivo API before you send a single message.
- Send SMS from any record: a 'Send SMS' action button is added to res.partner, sale.order, account.move, helpdesk.ticket and any additional models you specify, pre-filling the recipient number from the record.
- Bulk SMS to contact groups: target Odoo mailing lists, tags, or any saved res.partner filter domain, with per-campaign batching and rate limiting to respect your Plivo account throughput.
- Auto-SMS on order and business events: Odoo automated actions (base.automation) fire transactional messages on triggers like sale order confirmed, invoice posted, delivery validated or helpdesk ticket resolved.