What Spoke Phone Is
Spoke Phone is a modern business phone system built for mobile and distributed teams. It provides voice calling, SMS messaging, and shared business numbers across smartphones, tablets, and desktop computers. For companies with remote sales teams, field technicians, or busy dispatch desks, it delivers strong mobile communication tools without requiring desk phones or complex on-premise PBX hardware.
The Client Problem: Texting by Hand Outside Odoo
Before this integration, our client's customer service and dispatch teams handled customer text messages manually. Staff members were texting customers from individual mobile phones outside Odoo, creating fragmented communication and wasted time.
This manual approach created several clear operational bottlenecks:
Manual Communication Tasks. Staff had to manually copy customer phone numbers, compose individual text messages on handheld devices, and double-check order details for every confirmation, shipment notice, or appointment reminder.
No Visibility in Odoo. Because texts were sent from personal or standalone company phones, there was no record of sent messages in Odoo. If a customer followed up about a delivery time or service call, other team members had no way of knowing what was communicated.
Inconsistent Customer Experience. Without standardized templates, messages varied in tone and accuracy depending on which employee sent them, creating confusion when shipping dates or arrival windows changed.
Difficulty Scaling. As order volume grew, staff could no longer keep up with sending individual texts on time, resulting in delayed updates and missed notifications.
Want Odoo to text your customers at the right moments? Tell us your phone system.
What O2B Built: Automated SMS from Odoo Workflows
To eliminate manual messaging while keeping customer communications unified, O2B built a custom API integration connecting Odoo to Spoke Phone. Our integration embeds SMS in Odoo so messages trigger automatically based on business milestones.
Which Odoo Apps Trigger the Texts
We configured automated text triggers across three core operational apps in Odoo:
Sales App (Order Confirmations): When a sales quotation is confirmed as a sales order in Odoo, an API webhook instructs Spoke Phone to send an immediate order acknowledgment text to the customer's mobile number, including the order reference and support contact info.
Inventory App (Shipping Updates): When warehouse staff validate a delivery order (stock.picking), the integration sends a dispatch notification. The text includes the carrier name, tracking code, and an estimated arrival timeframe.
Calendar & Field Service (Appointment Reminders): For scheduled site visits, technical calls, or customer consultations, the Calendar app triggers automated reminder texts 24 hours and 2 hours prior to the scheduled slot, significantly lowering cancellation and no-show rates.
Dynamic Message Templates
Each message draws from dynamic Odoo templates. When an event fires, Odoo populates the customer's name, order ID, tracking URL, and technician details into the message body. This ensures consistent branding and clear details on every text sent.
How Inbound Replies Are Handled
A key design choice for the dev team was handling customer replies. By connecting Spoke Phone's incoming webhooks back into Odoo, customer replies can post directly to the chatter of the corresponding sales order, delivery order, or customer contact card. This gives account managers complete conversational history without checking a separate phone.
Spoke Phone vs Twilio vs Odoo Built-in SMS
Businesses looking to send SMS from Odoo typically consider three routes: connecting an existing business phone system like Spoke Phone, building on a communication API like Twilio, or using Odoo's native in-app messaging. Here is how they compare:
| Platform / Approach | Best For | Voice Calling | Two-Way SMS | Setup Effort |
|---|---|---|---|---|
| Spoke Phone Custom Integration | Teams already using Spoke Phone as their main business phone system who want unified calls and texts | Full business voice calling on mobile and desktop apps | Supported via API webhooks logged to Odoo chatter | Moderate (API credential configuration and webhook routing) |
| Twilio Integration | High-volume programmatic messaging, automated voice IVR, and global delivery pipelines | Programmatic voice via Twilio Voice API | Native two-way messaging with comprehensive webhook support | Moderate to High (Twilio console configuration, 10DLC registration, and custom webhook logic) — see our Odoo with Twilio guide |
| Odoo Built-in IAP SMS | Occasional, simple one-way transactional alerts with no external telephony requirement | No native voice calling included | Primarily one-way transactional alerts via in-app purchase credits | Low (purchase prepaid credits directly in Odoo and configure SMS gateway) |
What to Plan Before You Build One
Before deploying automated SMS messaging from your ERP, planning the following operational requirements will prevent delivery issues and compliance problems:
- Opt-in Consent & US Compliance. In the US, business text messaging is governed by the Telephone Consumer Protection Act (TCPA) and carrier A2P 10DLC regulations. Businesses must collect verifiable opt-in consent before sending automated texts and must honor opt-out keywords like "STOP" immediately. Check with your legal adviser to ensure your web forms and checkout flows comply.
- Identify High-Value Triggers. Text messages have much higher open rates than emails, but over-messaging can irritate buyers. Limit automated texts to high-priority updates: order confirmations, shipping tracking numbers, and time-sensitive appointment reminders.
- Message Length & Conciseness. Standard SMS segments are capped at 160 characters. Exceeding 160 characters splits messages into multiple billable segments. Keep template copy concise and use short URLs for order tracking.
- Inbound Reply Routing. Decide in advance who monitors customer replies. O2B can configure webhook listeners to route incoming texts to the sales rep assigned to the customer or convert replies into support tickets.
By using this integration, businesses eliminate manual texting, ensure records stay visible across all departments, and provide buyers with timely updates. If your team needs custom telephony or messaging workflows connected to your ERP, our Odoo integration services cover the API build, template configuration, and end-to-end testing.
Frequently Asked Questions
Can Odoo send SMS through Spoke Phone?
Yes, with a custom integration like the one O2B built. By connecting Odoo workflow triggers to Spoke Phone's messaging API, transactional SMS messages send automatically when sales orders are confirmed, deliveries are dispatched, or calendar appointments are booked.
Do customers need to opt in to texts?
In the US, business texts generally require prior express customer consent under TCPA regulations and carrier A2P 10DLC rules. Always collect clear opt-in consent during checkout or account registration, provide opt-out instructions, and consult your legal adviser to ensure compliance.
Can replies show up in Odoo?
It depends on how the integration is built. A two-way sync can route incoming customer replies directly into the Odoo chatter of the relevant sales order, delivery order, or customer record via webhooks. Ask for two-way sync during scoping if your team needs reply visibility.