Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $249.00 USD
- Versions ERPNext
- —
- Temps d'installation
- 30 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
Twilio Programmable Messaging for ERPNext
A build-to-order Frappe app that wires Twilio's SMS, WhatsApp and voice APIs into ERPNext, with signed inbound webhooks, two-way conversation logging on CRM records, click-to-call and call recording. ECOSIRE scopes, builds, installs and supports it on your v15/v16 site.
$249.00USD
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
Outbound SMS and WhatsApp via `@frappe.whitelist()` methods calling the Twilio REST API, returning the Message SID for tracking
`Twilio Message Log` DocType persists every message with dynamic link back to its source Lead, Contact, Customer or Ticket
Signature-validated inbound webhooks (`X-Twilio-Signature` checked against your Auth Token) — no unauthenticated writes into ERPNext
Inbound SMS/WhatsApp auto-creates or updates a Lead or Helpdesk Ticket by configurable routing rules
Click-to-call button injected via client script on Contact and Lead forms, dialing through Twilio Voice
Call recording URL, duration and call SID written back onto the originating record after the call ends
Two-way conversation thread rendering the full SMS, WhatsApp and voice history on one timeline per CRM record
DocType doc events wired in `hooks.py` to send templated messages on `on_submit`, status change or custom triggers
`Twilio Settings` single DocType storing Account SID, messaging service SID and Auth Token encrypted via the password fieldtype
Scheduler event reconciles pending Twilio delivery statuses (queued/sent/delivered/failed) so the log matches Twilio's ledger
WhatsApp template message support with approved-sender configuration and variable substitution
Role-and-permission gating so only designated role profiles can send messages or place calls
Message templates as a DocType with Jinja variable rendering from the linked document's fields
Delivery-status and error-code capture for reconciliation, retries and failure reporting
Compatible with Frappe/ERPNext v15 and v16, installable via bench on self-hosted or Frappe Cloud private bench
À propos de ce produit
ERPNext ships CRM, Lead, Contact and Helpdesk DocTypes, but out of the box it can only reach customers by email. There is no native path to fire a transactional SMS on on_submit, to run a WhatsApp conversation against a Lead, or to place and record an outbound call from a Contact record. Teams end up copying phone numbers into a separate Twilio console, or bolting on a marketplace app that covers SMS only and leaves inbound replies, voice and call recordings stranded outside ERPNext — no audit trail, no delivery-status visibility, no single timeline of how you reached each customer.
Pourquoi choisir Twilio Programmable Messaging for ERPNext
Outbound SMS and WhatsApp via `@frappe.whitelist()` methods calling the Twilio REST API, returning the Message SID for tracking
`Twilio Message Log` DocType persists every message with dynamic link back to its source Lead, Contact, Customer or Ticket
Signature-validated inbound webhooks (`X-Twilio-Signature` checked against your Auth Token) — no unauthenticated writes into ERPNext
Inbound SMS/WhatsApp auto-creates or updates a Lead or Helpdesk Ticket by configurable routing rules
Click-to-call button injected via client script on Contact and Lead forms, dialing through Twilio Voice
Call recording URL, duration and call SID written back onto the originating record after the call ends
Twilio Programmable Messaging for ERPNext is a purpose-built Frappe app (proper hooks.py, a dedicated module and custom DocTypes) that makes Twilio a first-class channel inside your existing site. Outbound sends run through @frappe.whitelist() server methods that call the Twilio REST API and persist every message as a Twilio Message Log record, linked back to its source document via a dynamic link, with the returned Message SID, delivery status and error code stored for reconciliation. A Twilio Settings single DocType holds the Account SID, Auth Token (encrypted via Frappe's password fieldtype), messaging service SID and the WhatsApp-approved sender numbers.
Inbound SMS and WhatsApp messages arrive on Twilio status and message webhooks that are signature-validated with your Auth Token (X-Twilio-Signature) before ERPNext trusts them. A validated inbound message creates or appends to the matching conversation thread and, by configurable rules, auto-creates a Lead or a Helpdesk Ticket routed to the right team. Click-to-call adds a button via client script on the Contact and Lead forms that dials through Twilio Voice; when the call ends, the recording URL, duration and call SID are written back onto the record so the whole two-way history — texts, WhatsApp turns and calls — lives on one timeline. DocType doc events (configured in hooks.py) let you send templated notifications on state changes, and a scheduler event reconciles pending delivery statuses so the log never drifts from Twilio's ledger.
Because this is build-to-order, nothing ships as a blind download. ECOSIRE starts with a short scoping call to confirm your Twilio account setup, the DocTypes you want messaging on, your notification triggers and your Frappe/ERPNext version (v15 or v16). We build against a staging clone of your site, run UAT with your team, then install to production behind a rollback plan and hand over the git repository. Typical delivery is 2-4 weeks from confirmed scope, followed by a post-go-live support window.
Ce que vous obtenez
- Installable source code of the Frappe app built for your ERPNext version (v15 or v16)
- Installation and configuration on your site, including Twilio credentials, webhooks and sender numbers
- Technical documentation: DocType schema, whitelisted methods, hooks and webhook endpoints
- User guide plus a live training session for your CRM and support team
- UAT on a staging clone with a documented rollback plan before production cutover
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the git repository with commit history and README
- Configured message templates and DocType-event triggers matching your agreed scope
Pour qui c'est
Global CRM & Sales Operations Lead
Runs multi-country outbound on ERPNext and wants one provider for SMS, WhatsApp and voice so every touch is logged on the Lead and Contact, not scattered across Twilio consoles and WhatsApp phones.
Customer Support / Helpdesk Manager
Needs inbound SMS and WhatsApp to open or update Helpdesk Tickets automatically, with the full conversation and any call recordings attached to the ticket for audit and QA.
ERPNext System Administrator / Frappe Developer
Wants a properly structured Frappe app with clean `hooks.py` doc events, whitelisted methods, encrypted credentials and permission gating — not brittle client-side hacks — that they can maintain from the handed-over git repo.
Compliance & Revenue Operations Owner
Requires a defensible audit trail of every customer message and call, with delivery statuses and recordings retained inside ERPNext for dispute resolution and regulatory review.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le ZIP de l'application Twilio Programmable Messaging for ERPNext depuis le tableau de bord de votre compte.
Ajoutez l'application à votre banc
Extrayez le ZIP dans le dossier d'applications de votre banc ou exécutez « bench get-app » avec le chemin d'accès à l'application extraite.
Installer sur votre site
Exécutez `bench --site SITE_NAME install-app APP_NAME` suivi de `bench migrate` pour installer Twilio Programmable Messaging for ERPNext et appliquer son schéma.
Activez votre licence
Ouvrez les paramètres de licence ECOSIRE sur votre site et activez votre clé de licence. Nécessite les applications gratuites ecosire_connect et ecosire_license_client.
Comment Twilio Programmable Messaging for ERPNext se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Channels covered | SMS, WhatsApp and voice with call recording in one app | Whatever you scope and build yourself | Usually SMS only; WhatsApp/voice rarely included | |
| Two-way logging | Full inbound + outbound thread on the CRM record | Possible but must be designed and built | Often outbound-only, no inbound thread | |
| Inbound routing | Signed webhooks auto-create Lead/Ticket by rules | Build your own webhook and routing logic | Limited or manual | |
| Fit to your DocTypes | Built to your DocTypes, triggers and workflow | Fully bespoke, at full build cost | Generic; you adapt to its assumptions | |
| Security & credentials | Encrypted Auth Token, permission-gated, signature-validated | Depends on your team's rigor | Varies by vendor | |
| Delivery time | 2-4 weeks from confirmed scope | Months for equivalent scope | Instant install, but partial coverage | |
| Support & ownership | Post-go-live support + git repo handover | You own and maintain everything | Vendor support; source usually closed | |
| Upgrade path (v15/v16) | Built and tested for your version, upgrades available | You handle version compatibility | Depends on vendor release cadence |
Foire aux questions sur Twilio Programmable Messaging for ERPNext
+How long does delivery take?
This is build-to-order. After a scoping call to confirm your DocTypes, triggers and Twilio setup, typical delivery is 2-4 weeks from confirmed scope. We build against a staging clone, run UAT with your team, then install to production behind a rollback plan.
+Is this an instant download from a marketplace?
No. ECOSIRE builds, installs and supports the app for your specific ERPNext site and version. You receive the installable source and the git repository at handover — but the product is delivered as a scoped engagement, not a blind download.
+How do updates and ongoing support work?
Every engagement includes a post-go-live support window for defect fixes and configuration changes. Because you receive the full git repository, your team can maintain it, or you can retain ECOSIRE for future ERPNext upgrades (for example a v15 to v16 migration) and new features.
+Which ERPNext versions are supported?
Frappe/ERPNext v15 and v16, on self-hosted benches or a Frappe Cloud private bench. We confirm your exact version during scoping and build and test against it.
+Do I need my own Twilio account?
Yes. You bring your own Twilio account, phone numbers and, for WhatsApp, an approved sender and message templates. We configure the Account SID, Auth Token and webhooks inside a `Twilio Settings` DocType, with the token stored encrypted.
+Are inbound webhooks secure?
Inbound SMS, WhatsApp and status webhooks are validated against Twilio's `X-Twilio-Signature` using your Auth Token before ERPNext acts on them, so no unauthenticated request can create records or trigger routing.
+Can messages fire automatically from ERPNext events?
Yes. We wire DocType doc events in `hooks.py` so templated SMS or WhatsApp messages send on triggers you choose — such as `on_submit`, a status change or a scheduler event — with variables rendered from the linked document.
Modules associés
Demander un devis
Twilio Programmable Messaging for ERPNext
A build-to-order Frappe app that wires Twilio's SMS, WhatsApp and voice APIs into ERPNext, with signed inbound webhooks, two-way conversation logging on CRM records, click-to-call and call recording. ECOSIRE scopes, builds, installs and supports it on your v15/v16 site.
- Outbound SMS and WhatsApp via `@frappe.whitelist()` methods calling the Twilio REST API, returning the Message SID for tracking
- `Twilio Message Log` DocType persists every message with dynamic link back to its source Lead, Contact, Customer or Ticket
- Signature-validated inbound webhooks (`X-Twilio-Signature` checked against your Auth Token) — no unauthenticated writes into ERPNext
- Inbound SMS/WhatsApp auto-creates or updates a Lead or Helpdesk Ticket by configurable routing rules