Commission Auto Sync fires an Application Created event the instant a carrier acknowledges your submission.
TL;DR
The Application Created event fires the instant a carrier acknowledges an application submission via webhook. Use it as an automation trigger to send welcome SMS, create follow-up tasks, update pipelines, and notify managers — eliminating the 2–3 day client anxiety gap.
What Is Application Created Event?
A real-time webhook event fired by Commission Auto Sync when a connected insurance carrier acknowledges receipt of a new application, available as an automation trigger for client notifications, task creation, and pipeline updates.
Key Takeaways
- Fires instantly when carrier acknowledges application receipt
- Available as automation trigger for SMS, email, tasks, and pipeline updates
- Eliminates client anxiety from post-submission silence
- Works regardless of how the application was submitted
- Feeds into agency-level production analytics
- Duplicate detection prevents repeated automation triggers
Key Data Points
- Application Created events fire within seconds of carrier acknowledgment, enabling instant client welcome messages that eliminate the 2–3 day post-submission anxiety gap.
- Agencies using Application Created automations report zero reactive 'did you submit my application?' calls from clients.
The moment between submitting an insurance application and the client hearing back is a black hole. The client wonders if their application was received. The agent plans to follow up but gets busy. Days pass. The client feels forgotten.
Commission Auto Sync eliminates this gap with the Application Created event — a real-time trigger that fires the instant a carrier acknowledges receipt of an application.
How the Application Created Event Works
When you submit an application through a connected carrier, the carrier's system processes the submission and sends an acknowledgment. Commission Auto Sync captures this acknowledgment via webhook and fires an Application Created event in your CRM.
The event contains:
- Client name and contact information
- Carrier and product type
- Application date and submission method
- Coverage details (amount, premium, term)
- Submitting agent (for agency tracking)
This event is available as an automation trigger, meaning you can build workflows that execute automatically the moment the carrier confirms receipt.
The Client Experience Transformation
Without Application Created Automation
- Agent submits application on Monday
- Client waits with no confirmation
- Client calls agent on Wednesday: "Did you submit my application?"
- Agent checks carrier portal, confirms submission
- Client waits again for status updates
Result: 2–3 days of client anxiety. Agent spends time on reactive status calls.
With Application Created Automation
- Agent submits application on Monday at 2:00 PM
- Carrier acknowledges receipt at 2:02 PM
- Client receives SMS at 2:02 PM: "Hi Sarah, your life insurance application with [Carrier] has been submitted. We'll keep you updated on its progress."
- Follow-up task is created automatically for 48-hour check-in
- Pipeline stage updates to "Application Submitted"
Result: Client is informed within minutes. Agent has zero manual follow-up work.
Building Automations on Application Created
Welcome SMS
Trigger: Application Created
Action: Send SMS to client
Template: "Hi [First Name], your [Product Type] application with [Carrier] has been submitted successfully. I'll keep you updated as it moves through underwriting. Questions? Reply to this message or call me at [Agent Phone]."
Follow-Up Task
Trigger: Application Created
Action: Create task for submitting agent
Details: "Follow up with [Client Name] in 48 hours to confirm application receipt and answer any questions" — due date: 2 days, priority: medium
Pipeline Update
Trigger: Application Created
Action: Update client pipeline stage to "Application Submitted"
Agency Manager Notification
Trigger: Application Created
Condition: Application premium exceeds $5,000
Action: Send email to agency manager with application details
Multi-Step Welcome Sequence
Trigger: Application Created
Actions (in order):
- Send welcome SMS immediately
- Send welcome email with "what to expect" timeline
- Create 48-hour follow-up task
- Update pipeline stage
- Log activity in client timeline
Tracking Application Volume
For agency owners, Application Created events feed into production analytics:
- Daily/weekly/monthly application submissions per agent
- Product mix of applications — which products are being sold most
- Carrier distribution — which carriers receive the most applications
- Submission timing — when during the day/week applications are submitted
- Conversion funnel — applications submitted vs. eventually approved
This data helps managers identify production trends, coaching opportunities, and carrier relationship priorities.
FAQ
Which carriers support Application Created events?
Most major carriers across life, health, Medicare, and annuity product lines support webhook notifications for application receipt. The exact list depends on your Commission Auto Sync carrier connections.
Does this work for applications submitted outside the CRM?
Yes. The event is triggered by the carrier's acknowledgment, regardless of how the application was submitted — through the CRM, a carrier portal, or a third-party enrollment platform.
Is there a delay between submission and the event firing?
Typically seconds to minutes. The event fires when the carrier's system processes the webhook, which happens as part of their normal application intake workflow.
Can I use different automations for different product types?
Yes. Add conditions to your automation: "When Application Created AND product type = Life Insurance → [specific actions]." You can create separate workflows for each product line.
What if the carrier sends duplicate acknowledgments?
Commission Auto Sync includes duplicate detection. If the same application triggers multiple carrier acknowledgments, only the first event fires your automation.
Frequently Asked Questions
How fast does the event fire?
Seconds to minutes after carrier acknowledgment.
Works for external submissions?
Yes — triggered by carrier-side acknowledgment regardless of submission method.
Can I set different automations per product?
Yes — use conditions to filter by product type.