Adding the feed to a record page

The most useful place for the Connect Feed is on the record page where your team already works — the Contact, Lead, Case or any custom object record. Placed there, the feed opens scoped to that record: the person's full conversation, with the composer ready. You place it with the Lightning App Builder, Salesforce's drag-and-drop page editor, and it works on any object's record page — standard or custom. This article walks through the placement, the three configuration properties, and a custom-object example end to end.

Step 1 — Open the page in the Lightning App Builder

Two routes to the same editor — use whichever you prefer:

• From a record: open any record of the object, click the gear icon (top right) and choose Edit Page.
• From Setup: go to Setup → Object Manager, click the object, click Lightning Record Pages, then open the page and click Edit (or click New if the object has no custom record page yet).

Expected result: the Lightning App Builder opens, showing the page layout in the middle and a list of components on the left.

The Lead record page open in Lightning App Builder — the components panel on the left is where you find REDA Connect Feed, and the canvas shows it placed in a side column of the page.

Step 2 — Drag the REDA Connect Feed onto the page

1. In the components panel on the left, scroll to the Custom (or Custom – Managed) section, or type REDA in the search box.
2. Find REDA Connect Feed — described as "WhatsApp-style messaging feed for REDA Connect."
3. Drag it onto the layout where you want it — a wide column or a dedicated tab within the page both work well.

Expected result: the feed appears on the canvas, and its three properties show in the panel on the right.

Step 3 — Set the three properties

Two things worth knowing:

• On a record page the conversation list is always hidden, whatever you set — the feed is already scoped to the one record, so there is nothing to list. The Hide conversation list switch matters on App pages and tabs (where the same component can show the full two-pane layout); on record pages you can leave it as is.
• A fixed height of 350 px suits a sidebar column; give it 500–700 px if the feed is the main content of its own tab on the page. When space is tight, users get a pop-out icon in the feed header that opens the conversation full-page in the Connect Feed tab.

Step 4 — Save and activate the page

1. Click Save (top right).
2. If this is a new page, Salesforce prompts you to Activate it. Choose the scope: Org Default (everyone), or assign by App, or by App, Record Type, and Profile.
3. Click Save on the activation dialog.

Expected result: open a record of the object — the feed is there, showing the record's messages, with the composer active at the bottom.

The feed once it is on the page. Outbound messages sit right in green with their delivery tick; inbound replies sit left in white under the sender’s name. The composer is live at the bottom — the two round buttons are the per-channel sends, so an agent picks WhatsApp or SMS at the moment of sending rather than up front. The record name and the sender are masked here; your own feed shows them in full.

Worked example — a custom object end to end

Suppose you manage rentals with a custom Booking object, and each Booking has a Tenant lookup to Contact, where the phone number lives.

1. Configuration first: create an object configuration for Booking__c per Configuring messaging for any object, pointing the phone field through the Tenant relationship (this related-record pattern is detailed in Messaging through a related record).
2. Open any Booking record → gear icon → Edit Page.
3. Drag REDA Connect Feed into the right-hand column. Keep the defaults (Use a fixed height on, 350 px).
4. Save, activate as Org Default.
5. Open a Booking whose tenant has messaged in — the conversation is there, and sending from the Booking reaches the tenant's WhatsApp.

What users see when the object is NOT configured

Placement always succeeds — the gap only shows at use:

• Messages already linked to the record still display.
• Instead of the send box, the composer area shows: "Sobject setup is not found." That exact sentence means the object has no active configuration — create one and the composer appears.
• If a configuration exists but no phone number or active Connect Account can be resolved for the record, the composer area shows: "No active connect account is found."

Troubleshooting

FAQ

Where to go next

• Configuring messaging for any object — the prerequisite that turns the composer on.
• The feed in the utility bar — the other placement admins set up.
• Using the Connect Feed — hand this to the users who'll work in it.