Advanced Salesforce Email Cadence Automation for Guardian Service

Guardian Service, a U.S.-based insurance sales and digital insurance distribution company, needed a more reliable and personalized way to follow up with prospective insurance customers after an Agent shared a quote.

WebSolo designed and deployed an advanced Salesforce email cadence that sends follow-up messages using each assigned Agent’s verified business email identity, coordinates email activity with Call and Text Tasks, detects customer responses, stops remaining cadence actions, and updates the related Opportunity sales process.

Success Story

Personalized, Reply-Aware Salesforce Email Automation

Agent-specific email sending, Google Workspace mailbox support, reply detection, coordinated sales Tasks, Opportunity automation, and production-scale Apex processing.

Talk to us

Client Profile

Business Challenge

Guardian Service’s insurance sales process required Agents to follow up with prospective customers after sharing insurance quotes. The process depended heavily on each Agent remembering when to send another message, make a call, send a text, or update the Opportunity.

A basic shared-mailbox automation was not appropriate because a specific Agent had already been assigned to each Opportunity. Guardian Service wanted follow-up messages to come directly from that Agent’s real business email identity, allowing the customer to continue communicating with the same representative.

• Automatically begin a follow-up cadence when an Opportunity enters the quote-sharing stage.
• Send personalized emails using the assigned Agent’s verified business email identity.
• Support individual Google Workspace mailboxes for participating Agents.
• Use Salesforce email templates with customer and Agent merge fields.
• Schedule messages and follow-up activities on appropriate business days.
• Create coordinated Call and Text Tasks for the assigned Agent.
• Detect customer replies before sending another cadence message.
• Stop all remaining cadence actions after a customer responds.
• Connect inbound communication to the appropriate Salesforce sales process.
• Advance responsive Opportunities to the next sales stage.
• Handle non-responsive Opportunities after the sequence is complete.
• Support reliable production-scale processing without exceeding Salesforce governor limits.

Key Requirements

• Start the cadence automatically when an Opportunity reaches the applicable quote follow-up stage.
• Use the assigned Opportunity Agent as the visible sender.
• Match each Agent to a verified Salesforce Organization-Wide Email Address.
• Support Agent-specific Google Workspace email identities.
• Personalize messages using Salesforce email templates and merge fields.
• Configure cadence timing without requiring Apex code changes for every adjustment.
• Create email, Call Task, and Text Task steps on a coordinated schedule.
• Move weekend actions to the appropriate business day.
• Check for inbound customer communication before processing each future step.
• Associate response activity with the relevant Contact and Opportunity context.
• Cancel pending cadence actions after a response or Opportunity-stage change.
• Advance responsive Opportunities to the Finalize stage.
• Close non-responsive Opportunities using defined status and follow-up values.
• Provide safe test-mode controls and allowlisted test recipients.
• Support bulk processing, Queueable execution, monitoring, and production troubleshooting.

Delivered Solution

Salesforce-Triggered Cadence Enrollment

WebSolo created Salesforce automation that initiated the email cadence when an Opportunity entered the Guardian Service quote follow-up stage.

The production process used the Opportunity stage 25-Share Quote as the trigger point. Salesforce generated the required cadence records and scheduled the future email and Task steps associated with that Opportunity.

• Automatic enrollment based on Opportunity stage.
• Cadence records connected to the related sales process.
• Scheduled dates and times calculated for each follow-up step.
• Protection against duplicate or inappropriate cadence creation.
• Cancellation when the Opportunity no longer met cadence conditions.

Personalized Agent Email Sending

Guardian Service wanted customers to receive follow-up messages from the insurance Agent responsible for their Opportunity rather than from a generic company mailbox.

WebSolo designed the solution to use each Agent’s verified business email identity. Salesforce matched the assigned Agent with a configured Organization-Wide Email Address and used that identity when sending the cadence message.

• Agent-specific sender identity.
• Verified Salesforce Organization-Wide Email Addresses.
• Google Workspace business mailboxes.
• Sender validation before processing each message.
• Clear failure handling when an Agent sender mapping was unavailable.
• No silent fallback to an incorrect or generic sender.

Salesforce Email Templates and Personalization

The cadence used Salesforce email templates containing information from the customer, Opportunity, and assigned Agent.

This allowed Guardian Service to maintain approved messaging while still creating a personalized customer experience. Template and merge-field behavior was tested and refined during implementation and production rollout.

• Salesforce-managed email templates.
• Customer first-name personalization.
• Assigned Agent name and contact information.
• Opportunity-related merge data.
• Template mapping controlled through configuration.
• Production refinement of template rendering and dynamic content.

Coordinated Email, Call, and Text Follow-Up

The solution coordinated automated emails with Agent follow-up Tasks so the cadence supported more than email alone.

The expanded production sequence included:

• Day 1: automated email, Call Task, and Text Task.
• Day 2: automated email, Call Task, and Text Task.
• Day 3: automated email and Text Task.
• Day 5: automated email and Text Task.
• Day 7: automated email and Text Task.
• Day 8: final thank-you email.

Generated Tasks were assigned to the responsible Agent and configured with an appropriate open status so they appeared correctly in operational Salesforce views and Agent work queues.

Business-Day-Aware Scheduling

WebSolo implemented scheduling logic that considered business-day requirements instead of treating every calendar day as an appropriate communication day.

When a cadence action would otherwise fall on a weekend, the solution could move the activity to the next appropriate business day. This created a more predictable and professional customer follow-up experience.

• Configurable cadence-day intervals.
• Weekend-aware processing.
• Scheduled delivery times for individual steps.
• Twice-hourly processing of due cadence records.
• Consistent scheduling across email and Task activity.

Reply Detection and Cadence Cancellation

Before processing a future cadence step, Salesforce checked whether inbound customer communication had already been recorded.

When a response was detected, the automation stopped the due and remaining cadence actions. This prevented customers from continuing to receive automated follow-ups after they had already replied to the assigned Agent.

• Inbound communication detection before future sends.
• Reply-aware cancellation of pending cadence records.
• Protection against unnecessary follow-up messages.
• Connection of response activity to the related Contact and sales process.
• Opportunity advancement when the customer responded.

Google Workspace Reply Synchronization

Guardian Service used individual Google Workspace mailboxes for its insurance Agents. Replies returned through the Agent’s business email environment and were made available to the Salesforce activity model used by the cadence processor.

This allowed Salesforce to recognize that a prospective customer had responded, stop future cadence actions, and continue the sales process using the related Contact and Opportunity information.

Opportunity Stage and Outcome Automation

The cadence was connected to the Opportunity lifecycle rather than operating as an isolated email tool.

When Salesforce detected an appropriate customer response, the Opportunity could be advanced from the quote follow-up stage to 30-Finalize. When the full sequence completed without a response, the design supported closing the Opportunity with defined non-responsive and Smart Cycle values.

• Responsive Opportunity advancement.
• Cancellation of remaining cadence steps.
• Non-responsive Opportunity handling.
• Closed Lost reason automation.
• Smart Cycle field processing.
• Stage-based protection against unnecessary future sends.

Custom Metadata and Administrator Controls

WebSolo used Salesforce Custom Metadata to make the cadence easier to maintain and safer to test.

Configuration controlled important elements such as timing, template mappings, test-mode behavior, and permitted test recipients. This allowed project administrators and developers to adjust supported settings without rebuilding the core Apex architecture.

• Configurable cadence timing.
• Email template mappings.
• Test-mode activation.
• Allowlisted test recipient addresses.
• Safer sandbox and production validation.
• Reduced dependency on hard-coded values.

Scheduled Apex and Queueable Processing

The production cadence processor used Scheduled Apex and Queueable Apex to handle due records asynchronously.

The scheduler ran twice per hour and identified cadence records whose scheduled time had arrived. Queueable processing then handled response checks, template rendering, sender validation, email delivery, Task creation, and related Opportunity actions.

• Scheduled Apex execution at minute 00 and minute 30.
• Queueable Apex for asynchronous processing.
• Separate execution and response-detection services.
• Controlled processing of pending cadence records.
• Support for continued processing through chained Queueable jobs.

Production Scalability and Governor-Limit Optimization

After production processing began, WebSolo identified and corrected Salesforce governor-limit risks associated with higher record volumes, inbound response detection, and repeated email-template rendering.

The automation was redesigned and optimized to provide more reliable bulk processing.

• Bulkified inbound response retrieval.
• Reduced processing batch sizes.
• Self-chaining Queueable jobs.
• Reduced per-record query and template-rendering overhead.
• Improved handling of invalid or unverified sender identities.
• Separation of expected email delivery bounces from system failures.
• Improved monitoring and troubleshooting of asynchronous jobs.

Dedicated Automation User Planning

WebSolo also reviewed ownership of Scheduled and Queueable Apex jobs. The recommended production model used a dedicated Salesforce API Integration or automation user rather than depending on an individual employee account.

This improved operational continuity, job ownership, error notification management, and long-term maintainability.

Testing, Deployment, and Production Support

The project included structured sandbox testing, end-to-end Agent mailbox testing, production deployment, monitoring, and post-deployment refinements.

• Dedicated Google Workspace test mailbox.
• Salesforce Producer-user testing.
• Test Opportunities and cadence records.
• Validation of each email and Task step.
• Reply testing to confirm cancellation of future steps.
• Custom Metadata test controls.
• Sandbox implementation and review.
• Production deployment and validation.
• Post-deployment template and Task corrections.
• Production error analysis and performance optimization.

Project Timeline

Results and Benefits

The solution helped Guardian Service create a more consistent and personalized insurance quote follow-up process inside Salesforce.

• Automated cadence enrollment when an Opportunity entered the quote-sharing stage.
• Preserved the assigned Agent as the visible sender of customer communications.
• Supported individual Google Workspace business mailboxes.
• Created a consistent multi-step follow-up process across the sales team.
• Coordinated emails with Call and Text Tasks.
• Reduced the risk of Agents missing required follow-up activities.
• Stopped future communications after Salesforce detected a customer response.
• Connected customer communication to Contact and Opportunity context.
• Advanced responsive Opportunities through the sales process.
• Supported defined handling for non-responsive Opportunities.
• Allowed timing, templates, and test behavior to be managed through Custom Metadata.
• Provided structured test-mode controls for safe validation.
• Improved production scalability through bulk processing and governor-limit optimization.
• Created an architecture that could support additional cadence use cases in the future.

Platform and Technologies

• Salesforce Platform
• Salesforce Opportunities
• Salesforce Contacts
• Salesforce Tasks
• Salesforce EmailMessage activity
• Salesforce Email Templates
• Salesforce Organization-Wide Email Addresses
• Apex triggers and Apex classes
• Scheduled Apex
• Queueable Apex
• Custom Metadata
• Google Workspace mailboxes
• Personalized Agent sending
• Inbound reply detection
• Business-day scheduling
• Opportunity-stage automation
• Call and Text Task creation
• Batch and asynchronous processing
• Governor-limit optimization
• API Integration and automation-user planning
• Sandbox testing
• Production deployment and monitoring

WebSolo Services Provided

• Salesforce Consulting
• Salesforce Implementation and Enhancements
• Custom Salesforce Development
• Salesforce Integration and Data Migration
• Salesforce Support and Training

Frequently Asked Questions

What type of Salesforce solution did WebSolo build for Guardian Service?

WebSolo built a custom Salesforce email cadence for insurance quote follow-up. The solution used Agent-specific sending identities, Salesforce email templates, Google Workspace mailboxes, reply detection, Scheduled Apex, Queueable Apex, Call and Text Tasks, and Opportunity-stage automation.

Were the emails sent from one generic mailbox?

No. The architecture was designed so the cadence email could be sent using the verified business email identity of the Agent assigned to the Opportunity.

What happened when a customer replied?

Salesforce checked for inbound customer communication before processing future cadence steps. When a response was found, the remaining cadence actions were cancelled and the related Opportunity could advance to the Finalize stage.

Did the cadence only send emails?

No. The solution also created coordinated Call and Text Tasks for the assigned Agent, allowing Salesforce to manage a broader follow-up process.

Did Salesforce automatically send text messages?

No. The implemented cadence created Text Tasks for Agents. It did not automatically send SMS messages.

How was the cadence configured?

Salesforce Custom Metadata controlled supported configuration such as cadence timing, email-template mappings, test mode, and permitted test recipients.

How did WebSolo support production scale?

WebSolo used Scheduled Apex, Queueable Apex, bulk response detection, controlled batch sizes, chained asynchronous processing, and governor-limit optimization to support reliable production processing.

Can WebSolo create similar email cadences for other sales teams?

Yes. WebSolo can design Salesforce cadences using shared or representative-specific sending models, email templates, reply detection, sales Tasks, Opportunity automation, Google Workspace or Microsoft 365 environments, and scalable Apex processing.