Skip to main content

SMS Chatter Conversations

Purpose​

SMS Chatter Conversations adds an SMS Inbox view to record chatter. It groups SMS history by sender number, provides an Internal discussion tab, and adds an AI Helper for summaries and suggested replies. Back to Chatter returns to ordinary record communication. It extends existing records rather than adding a standalone application menu. The reviewed 19.0 package is not presented as operational: this guide is a settings and control reference pending package and access validation.

Before you start​

Install the matching version of corvus_sms_chatter_tabs with corvus_sms_workspace, crm, mail and web. Workspace brings the inbound, media and gateway dependencies. The manifest has no Enterprise-only dependency. Configure sender numbers and routing through Two-Way SMS & CRM Inbox.

The workflow below describes the reviewed 19.0 source. Its workspace dependency and some loaded templates require a corrected, validated package before the interface can be relied upon. Check the installed package version with your administrator; do not treat the catalogue listing as installation verification. Conversation access also needs administrator review before deployment. No runtime or external service test was performed.

Access and setup​

This addon introduces no special operator group. Existing record access and the messaging dependencies apply. Internal Users have read access to saved AI summary records; Settings administrators have full access to that model. These permissions do not establish private ownership of every conversation or summary.

Administrators configure Settings → SMS Routing → AI SMS Suggestions. Select AI Provider as ChatGPT or Gemini, then supply that provider's approved API key and model. A visible AI control alone does not prove a model is configured. Whisper API Key supports transcription when the Suite extension is installed; it is not needed for ordinary SMS history.

Review the context switches: Include Record Notes / Description, Include Sent SMS, and Include Received SMS default on; Include Emails defaults off. Defaults for Max GSM Chars for Suggestion, AI Response Temperature, and Max Tokens per Response are 160, 0.5, and 150. Limit context to information the organisation permits the selected AI service to receive. AI actions make external requests; browsing the existing conversation does not require them.

Control reference pending validation​

  1. SMS Inbox is the record-level view, with sender-number tabs determining conversation context and the reply composer. Its operational availability depends on the validated package.
  2. The conversation displays inbound and outbound history. Customer phone and From number are the fields to review when preparing a local draft. Missing sender choices require administrator review of number configuration and assignments.
  3. Internal provides a team-note control. This is a record discussion, not an outbound SMS to the customer's phone. It can be included in AI context when the relevant option is selected.
  4. AI Helper has number-tab and Internal-context selectors. Generate would request a summary and suggested actions/replies; Copy would copy a proposed reply. These calls remain unavailable under this reference until package and conversation-access validation. Neither control establishes SMS delivery.
  5. A local draft can be reviewed for accuracy, recipient, tone and SMS length. Send is an external provider action through the shared composer and remains outside this reference scope until operational validation. An AI suggestion is not a delivery receipt.

The source also offers rerouting for an inbound SMS attached to a business record. The target must exist and belong to the same customer where a customer relationship is known. SMS Inbox timeline messages cannot be rerouted by this action. Treat rerouting as changing record association, not resending the message. Rerouting remains unavailable under this reference pending validation of the installed access boundary.

Practice scenario​

In an approved training database after package validation, use fictional customer Pine House and sender +12025550123. Compare a sample received question with a draft answer and identify which sender tab and record should own the discussion. Write the reply locally without pressing Send or Generate. This is a source-derived exercise and was not executed.

Limits and troubleshooting​

Missing provider, key or model settings, empty SMS context, and an empty AI response can prevent suggestions. Record context and generated summaries can be incomplete; review them before sharing. The GSM character target is a suggestion setting, not a guarantee of one billed segment, especially for Unicode text.

Some rewriting actions use Odoo's native editor generation service. They should not be assumed to use the provider selected for Corvus summaries. Odoo 17 uses the older web-editor integration; the reviewed 19 implementation uses the HTML editor route. Selected 20 comparisons also change configuration/access APIs and template declarations; they do not certify the entire workflow.

For sender and composer behavior, see SMS Inbox & Composer. Floating SMS Chat reuses these conversations from a floating panel, and SMS Language Translation supplies separate language controls.

The catalogue lists Odoo 17.0–20.0. This guide reviews 19.0 source and selected differences in the other versions; it is not a runtime qualification. Choose the exact installed major version in the Corvus app catalogue for purchase and available live-test options. No individual marketplace or running demo was verified for this guide.