Sending Email from REDA

You can email a tenant, buyer, owner, or vendor without leaving REDA — straight from a contact or deal record — and every send is logged automatically to that record's timeline, so the whole team can see the correspondence. This article covers sending an email from a record, inserting a template, choosing the From address, and understanding where the email goes afterward. This is the one-to-one, record-level email guide; sending to many people at once (the council mass-email path) is covered separately and linked at the end.

What sending email from REDA does

The point of emailing from within REDA is context and memory. You email people from the record that's about them, and REDA keeps a copy on that record. Nobody has to dig through a personal inbox to find out what was said — the send lands on the timeline for everyone with access to see.

Sending an email from a record

From a record's Activity composer, the Send Email tab lets you compose against Contact, Account, Inquiry, and Opportunity records:

See The Calendar & Activity Timeline for how the sent email appears afterward.

Using an email template

Insert a template from the composer's template picker; the subject and body pre-fill, with merge fields replaced by values from the record — the contact's first name, the property address, the lease start date, and so on. Always review the result before sending: if a source field on the record is empty, its merge field can show as blank or a placeholder, so fill it on the record (or type the value) first.

Templates are admin-managed — they live on the Email Templates tab in REDA Admin, and their access is org-side. As an end user you insert existing templates; you don't build them. If you need a new template, ask your administrator (see Managing Email Templates).

The From address

By default, email sends from your own address — the email on your Salesforce profile. If your administrator has configured org-wide email addresses (a shared team address like a leasing inbox), you can pick one of those as the From address instead.

Where the email goes afterward

Every send logs as a completed activity on the record's timeline, with the full body available on expansion. What happens to replies depends on your org: capturing inbound replies back onto the record is an org-side setting (Enhanced Email or activity capture). If your org hasn't configured it, replies arrive in your own inbox only — that's a platform-level choice, not a REDA feature.

Sending to many recipients

The Send Email composer is for one-to-one correspondence. For a bulk send, REDA provides a separate path: the Mass Email action on a Council Event record, which emails the event's participants at once. It's covered separately because it's backed by its own configuration and needs different access:

Worked example: emailing David

Leasing agent Nadia Khan opens David Okafor's contact and clicks Send Email. She inserts the "Lease renewal reminder" template — merge fields fill his name and the Meridian Court #101 unit address — reviews it for any blanks, attaches the renewal-terms PDF from the deal's Files, and sends. The email logs to David's and the lease's Activity History for the whole team to see. Because this org hasn't set up a shared leasing@ address, it sends from Nadia's own address — there's no From dropdown to choose from. When the community's HOA later needs to notify all residents of a meeting, that's a Mass Email from the Council Event — a different path.

The Send Email composer on a contact — From and To are pre-filled (To set to the contact), with the Subject field, the body area, and the attach, template and merge-field controls along the bottom.

Where to go next

1. The Calendar & Activity Timeline — where the sent email appears.
2. Tasks, Events & Activities in REDA — the other activity types.
3. Mass-Emailing Council Participants — the bulk-email path.
4. Managing Email Templates — how templates and merge fields are built.

Frequently asked questions