1. Sequence - Email Step Supports Adding CC and BCC Recipients
Business Context In B2B marketing scenarios, users need to achieve automated integration with third-party review tools (such as Trustpilot's Automatic Feedback Service, AFS) via the BCC function.
-
Current Pain Points: Due to the lack of CC/BCC fields in Sequence, Unibox, and contact panels, and the inability to display blind copy records in the email conversation flow, the automated review collection process cannot form a closed loop.
-
Core Requirement: By BCCing a dedicated Trustpilot address in the Sequence welcome email, the system triggers an automatic review invitation to the customer one day later, thereby improving brand ratings without disrupting the customer experience.
Comparison: Before vs. After Following the launch of this new feature, the professionalism and automation capabilities of email sending have improved significantly:
| Dimension | Before Update | After Update (CC/BCC Support) |
| Sending Flexibility | Only supported a single recipient (To); unable to silently notify third-party systems. | Supports Multi-recipient CC/BCC, enabling automated integration and multi-party collaboration. |
| Interaction Experience | Email addresses required manual input; lacked validation and management was chaotic. | Tokenized Input, supporting auto-encapsulation, validation, and batch pasting. |
| Record Traceability | Email detail pages could not view blind copy addresses; sending status was uncontrollable. | Thread Complete Display, clearly showing CC/BCC details for every email. |
| Automation Integration | Required developing complex APIs or manual operations in Trustpilot. | Zero-Code Integration; trigger AFS services simply via Sequence BCC. |
Key Changes & Feature Overview
🎨 Sending Side: Full Scenario Coverage
-
Sequence: Added CC/BCC entry points above the email Subject. Once saved, the step panel will visually display the configured address tags.
⌨️ Interaction Details: Tokenized Input
-
Quick Encapsulation: Press Enter, ; or , after entering an address to automatically convert it into an independent tag (Chip).
-
Auto-Validation: Incorrectly formatted email addresses are highlighted in red; supports quick deletion via clicking X or the Backspace key.
-
Deduplication & Limits: The system automatically filters duplicate emails. The limit is set to 10 addresses per field to prevent triggering anti-spam mechanisms.
🔍 Viewing Side: Email Thread Display Loop
-
Detail Display: When expanding an email in the conversation detail page, new CC/BCC detail rows are added below "To," ensuring sending records are traceable.
-
Reply Display: As long as the reply email's "To" field contains the original "From" address, the reply will be displayed in the Thread, ensuring the communication context is complete.
Core Value
-
Automation Loop: Achieve deep integration with third-party tools at minimal cost, boosting business conversion.
-
Professional Image: BCC keeps email content clean, allowing customers to focus on the business itself rather than backend tools.
-
Data Purity: Replies from CC/BCC do not contribute to core business statistics (such as Analytics or Sequence counts), ensuring the accuracy of marketing analysis data.
2. Fix: Predictive Dialer Outage During the Year-End Transition
Root Cause: When validating an Agent's online status, the system used an identifier based on "Month+Day" (e.g.,
Sam_1230_XXXX representing Dec 30th). The legacy logic only compared the magnitude of the "Month-Day" value when checking online time.-
New Year Conflict: Upon entering 2026, the newly generated identifier (e.g.,
0101) was numerically smaller than the identifier from the end of 2025 (e.g.,1230). This caused the system to incorrectly judge the Agent's status as expired, thereby blocking the dialing request.
Fix Content: Refactored the Agent online status recognition logic to incorporate full year validation.
Core Value: Ensures the stability of the Predictive Dialer during the yearly transition and eliminates the unresponsive ("frozen") dialing state caused by the timestamp comparison logic.