Configuring messaging on any object

Nothing about REDA Connect is limited to Contacts and Leads. Any object whose records relate to a person you can text — a custom Booking, Property Inquiry, Case, or anything else — can carry a Connect Feed and its own conversations. The recipe is the same one used for Contacts and Leads: create one object configuration per channel under your Connect Account, pointing at the object's phone and name fields. The only new work is looking up your object's system name first.

This walkthrough uses a realistic example: a custom Booking object where each booking record stores the guest's name in Guest Name and their mobile number in Guest Phone.

Step 1 — Find the object's API name

The configuration identifies your object by its API name — simply the object's system name, which for custom objects differs from its display label (it ends in __c). This is admin-facing information Salesforce shows you directly:

1. Click the gear icon (top right) and choose Setup.
2. Open Object Manager (the tab next to Home in Setup).
3. Find your object in the list — the API Name column shows the value you need. For our example, the label Booking has the API name Booking__c.

Expected result: you have the exact API name noted, including the __c ending and any prefix.

Where the two values you need actually live. Object Manager → Booking → Details shows the Singular Label (Booking) and the API Name (reda1__Booking__c) together — the object configuration needs the API name, not the label.

Step 2 — Find the phone and name field API names

Still in Object Manager:

1. Click your object, then Fields & Relationships.
2. Note the Field Name (the API name) of the field that holds the phone number — for our example, Guest Phone is Guest_Phone__c.
3. Note the API name of the field that should appear as the person's name in the feed — Guest Name is Guest_Name__c. If your object's standard Name field is the right label, use Name.

What if the object has no phone field? Two options:

• The phone number genuinely belongs on this object (e.g. the guest's number is entered per booking) → create a Phone-type field on the object, then continue here.
• The phone number really lives on a related record — for example the Booking looks up to a Contact who owns the number → don't duplicate the number. Use the related-record setup instead: Messaging through related records.

Step 3 — Create the configuration

1. Open the REDA Connect app → Connect Accounts tab → your account.
2. In the Connect Account Configs related list, click New.
3. Fill in:

1. Click Save, then repeat for SMS if the object should message on that channel too.

Expected result: the configuration is listed under the account. Remember the product's rule for the Object API Name field: "You must define only one setup for one type of sObject for a communication channel" — exactly one configuration per object per channel.

A saved configuration for the custom Booking object

Step 4 — Add the feed to the object's record page

The configuration alone doesn't change the object's page. Add the Connect Feed component to the Booking record page in Lightning App Builder — the click-by-click is in Adding the feed to a record page, and it works the same for custom objects as for standard ones.

Step 5 — Verify

1. Open a Booking record whose Guest Phone holds your own number, digits-only international.
2. Send a message from its Connect Feed. Expected result: it arrives on your phone.
3. Reply from your phone. Expected result: the reply appears in the same Booking's feed — provided the Booking's priority position means it wins the match for that number (details in inbound record matching).

Troubleshooting

FAQ

Where to go next

• Adding the feed to a record page — the other half of putting messaging on your object.
• Messaging through related records — when the phone number lives one lookup away.
• How incoming messages find their record — choose priorities with the full picture.