Two-Way SMS & CRM Inbox

Turn provider callbacks into organized Odoo conversations

Receive replies through tokenized webhooks, match the destination number, route each message to the right business context, and keep unmatched traffic visible in SMS Inbox.

What breaks without an inbound layer?

Outbound messages may leave Odoo correctly, but customer replies arrive in provider-specific formats. Multiple receiving numbers complicate ownership, delivery callbacks can be confused with messages, and an unmatched reply can disappear into a technical log.

1. Define where replies belong

Settings expose primary target, fallback target, CRM lead strategy, missing-record actions, inbox policy and the global fallback sender number. Administrators can make routing predictable instead of embedding one client-specific assumption.

• Continue the last outbound conversation.
• Choose the latest or designated SMS lead.
• Post to contact chatter.
• Use SMS Inbox or discard explicitly.

2. Map the provider webhook

Enable inbound support, copy the generated callback URL, and map the provider's sender, recipient, text, media and message identifiers. A shared endpoint can classify inbound messages and delivery-status events through configured discriminator values.

Webhook token: identifies the gateway without exposing an Odoo login. Rotate it if the URL is disclosed.

3. Register every business number

The number registry connects inbound destination matching with outbound sender continuity. Give each number a useful label and color, control eligible users, set defaults and country preferences, and optionally enforce hourly or daily limits.

Companion chatter and floating interfaces reuse this identity so operators know which number owns each conversation.

4. Diagnose the full callback trail

Inbound logs keep the gateway, raw numbers, payload and headers, provider IDs, duplicate relation, processing state and routing note. The parser wizard lets administrators test a sample payload before enabling live callbacks.

5. Never lose an unmatched reply

SMS Inbox stores one conversation per normalized phone identity, tracks unread and total messages, links a contact when available, and preserves activity that cannot safely be assigned to another record.

How the inbound engine works

Gateway compatibility and provider responsibility

Important: Inbound SMS is not supported through Odoo IAP. Inbound messages require a third-party provider that explicitly supports inbound webhooks and inbound callbacks, plus an active inbound-capable package, sender/receiver setup, and sufficient provider balance.

There is absolutely no warranty that a custom gateway will work out of the box. APIs differ in authentication, payload paths, signatures, delivery statuses, media formats and regional rules; minor adjustments may be required.

Telnyx and LoopMessage have been tested for inbound and outbound SMS/MMS workflows. Corvus Nexus Technologies LTD is not an official partner, reseller or representative of any SMS/MMS provider and does not sell carrier service, phone numbers or delivery guarantees.

After purchase, you may ask us to configure one specific gateway without an additional service charge. Provider fees, custom provider development, telecom compliance and third-party guarantees are excluded.

Dedicated inbound SMS demo

This video is for Two-Way SMS & CRM Inbox only. It explains how inbound SMS is configured, how webhooks are secured, how payload mapping and routing are set, and how inbound conversations are handled in Odoo.

Use this after reading the module guide for a complete end-to-end setup and verification flow.