[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAM6NE35FE07GS498CD809":3,"skill-same:01M7FAM6NE35FE07GS498CD809":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7FAM6NE35FE07GS498CD809","dealer-new-customer-onboarding",null,"Design a comprehensive 90-day post-sale customer onboarding program for a car dealership. Use when the user asks to \"build a new customer onboarding program\", \"design post-sale follow-up\", \"90-day onboarding sequence\", \"sales-to-service handoff\", \"S2S handoff\", \"new vehicle owner onboarding\", \"post-delivery customer journey\", \"design our delivery process\", \"first service introduction program\", \"owner onboarding for a dealer\", or any request to plan and document what happens with a customer in the first 90 days after they purchase or lease a vehicle. Produces a complete multi-channel program covering day 0 (delivery) through day 90 (first service intro), including email touchpoints, SMS sequences, in-person handoffs, OEM connected-services activation, review request timing, and the critical sales-to-service handoff that determines whether the customer returns for paid maintenance. Pairs with dealer-equity-mining-campaign-builder (which picks up at month 6+), dealer-email-flows (which covers the broader lifecycle email), and dealer-store-positioning (which defines the voice the program uses). Authored by Ariel Coro of Dealer AI Guy.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffranchise-management\u002Fdealer-new-customer-onboarding\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dealer-new-customer-onboarding\ndescription: >-\n  Design a comprehensive 90-day post-sale customer onboarding program for a car dealership. Use when the user asks to \"build a new customer onboarding program\", \"design post-sale follow-up\", \"90-day onboarding sequence\", \"sales-to-service handoff\", \"S2S handoff\", \"new vehicle owner onboarding\", \"post-delivery customer journey\", \"design our delivery process\", \"first service introduction program\", \"owner onboarding for a dealer\", or any request to plan and document what happens with a customer in the first 90 days after they purchase or lease a vehicle. Produces a complete multi-channel program covering day 0 (delivery) through day 90 (first service intro), including email touchpoints, SMS sequences, in-person handoffs, OEM connected-services activation, review request timing, and the critical sales-to-service handoff that determines whether the customer returns for paid maintenance. Pairs with dealer-equity-mining-campaign-builder (which picks up at month 6+), dealer-email-flows (which covers the broader lifecycle email), and dealer-store-positioning (which defines the voice the program uses). Authored by Ariel Coro of Dealer AI Guy.\ncategory: franchise-management\ndomain: franchise-management\nsubdomain: general\nversion: 1.0.0\nlicense: MIT\nrisk: low\nsource:\n  repository: \"arielcoro\u002Fdealer-ai-skills\"\n  commit: \"f86e321454\"\n  imported_at: \"2026-09-20\"\n  license: \"MIT\"\nplatforms:\n  - claude-code\n  - cursor\n  - codex\n  - gemini\n  - antigravity\n  - copilot\n---\n# Dealer New Customer Onboarding\n\nThis skill designs a comprehensive 90-day post-sale customer onboarding program for a car dealership. The output is a multi-channel program covering delivery through first service intro, including every touchpoint with channel, content, owner role, and trigger logic.\n\nThe program architecture, the sales-to-service handoff philosophy, and the why-90-days reasoning are in `REFERENCE.md`. The complete touchpoint table with channel, content templates, owner role, and trigger logic per day is in `TOUCHPOINTS.md`. Authored by Ariel Coro of Dealer AI Guy.\n\n## Why 90 days\n\nThe first 90 days after a vehicle sale determine whether the customer becomes a service customer, a referral source, a repeat buyer — or never returns. Industry data consistently shows that customers who complete their first dealer service visit within 90 days of purchase have dramatically higher lifetime value: more service visits, more referrals, and a meaningfully higher probability of buying their next vehicle from the same dealer.\n\nMost dealers know this. Few execute it systematically. The post-sale experience is typically handled ad-hoc: the salesperson hands off the keys, maybe sends one follow-up email, and the customer disappears into the broader market. By day 60 the customer has often forgotten the salesperson's name and decided that \"their dealership\" is whichever shop is closest to home.\n\nThis skill produces the systematic program that fills the gap. Multi-channel touchpoints with clear ownership. The critical first-service intro happens by design, not by hope.\n\n## The sales-to-service handoff is the entire point\n\nThe most important touchpoint in the 90-day program is the sales-to-service handoff. Done well, the customer returns for paid maintenance after the OEM warranty service ends and stays for years. Done poorly, the customer goes to the local quick-lube and the dealer loses 5 to 10 years of service revenue.\n\nThe skill prioritizes this handoff aggressively. Multiple touchpoints across multiple channels reinforce the service relationship before the first service visit is due. The first service visit itself is designed as a relationship-building moment, not a transactional appointment.\n\n## When to invoke\n\nInvoke this skill when the user wants to:\n\n- Design or document a 90-day post-sale onboarding program.\n- Refresh an existing onboarding program that is producing weak retention.\n- Add structure to a delivery process that varies by salesperson.\n- Design a sales-to-service handoff specifically.\n- Plan the OEM connected services activation flow (OnStar, FordPass, MyChevrolet, etc.).\n- Build the program a new BDC manager or service manager will execute.\n\nDo not invoke this skill for general lifecycle email (use dealer-email-flows for the broader lifecycle), for equity mining campaigns (those start at month 6+), or for non-dealer businesses.\n\n## How to run\n\nThe skill gathers inputs about the dealership, the brand portfolio, and current onboarding practices. Then produces the 90-day program.\n\n## Operating sequence\n\n1. **Read REFERENCE.md** to load the program architecture, the sales-to-service handoff philosophy, and the why-90-days reasoning.\n\n2. **Read TOUCHPOINTS.md** to load the complete touchpoint table with day-by-day, channel-by-channel detail.\n\n3. **Gather inputs.** Capture in this order:\n\n   - **Dealership name and primary brand portfolio.** Different OEMs have different connected services platforms (GMC: MyGMC + OnStar; Ford: FordPass; Stellantis: Uconnect; Toyota: ToyotaCare; etc.). The onboarding program must include OEM-specific connected-services activation.\n\n   - **Sale type focus.** New, used, CPO, or all. The 90-day program is most aggressive for new and CPO; lighter for used.\n\n   - **Sales-to-service handoff philosophy.** What does the dealer currently do? What gap is the user trying to close?\n\n   - **Channels available.** Email, SMS, ringless voicemail, in-person, postal mail. Default: email + SMS + in-person.\n\n   - **Compliance baseline.** Existing opt-in workflow, suppression lists, frequency caps. Reference dealer-equity-mining-campaign-builder's COMPLIANCE.md if available.\n\n   - **Service capacity.** Can the dealer support the volume of first-service appointments the program will generate? Typically yes, but if service capacity is tight, the program adjusts.\n\n   - **Bilingual?** When the dealer serves Spanish-speaking customers, produce bilingual touchpoints.\n\n   - **Optional: existing dealer-store-positioning output.** The onboarding voice should match the dealership positioning.\n\n4. **Design the program.** Use the TOUCHPOINTS.md framework. Customize per dealer:\n   - Touchpoint timing (some dealers run faster, some slower)\n   - Channel mix (some have ringless voicemail, some do not)\n   - OEM-specific connected services activation\n   - Service hours and capacity considerations\n   - In-person touchpoint feasibility (depends on geographic distribution of customers)\n\n5. **Generate the program.** Use the output structure below.\n\n## Output structure\n\nRender in clean Markdown. The program output has six parts.\n\n### Part 1: Program overview\n\n- Dealership name and brand portfolio\n- Target customer (new buyer, CPO buyer, etc.)\n- Program window: 90 days from delivery\n- Total touchpoints (typically 15 to 20)\n- Channel mix (email + SMS + in-person + optional voicemail)\n- Primary success metric (typically: first service appointment scheduled within 90 days of delivery)\n\n### Part 2: The 90-day touchpoint sequence\n\nA table covering every touchpoint:\n\n| Day | Channel | Audience | Touchpoint | Owner | Trigger | Success metric |\n| --- | --- | --- | --- | --- | --- | --- |\n| 0 | In-person | All deliveries | Delivery walkaround + OEM connected services activation + service intro | Salesperson + delivery coordinator | Vehicle delivery | Service advisor introduced and named |\n| 1 | Email | All deliveries | Welcome + first impressions survey | BDC | 24 hours post-delivery | Email open + survey response |\n| 7 | SMS | Email-opt-in only | First week check-in | BDC | 7 days post-delivery | Reply or callback |\n| ... | | | | | | |\n\n[15 to 20 rows total]\n\nFor each row:\n- **Day:** Days post-delivery\n- **Channel:** Email, SMS, in-person, ringless voicemail, postal mail\n- **Audience:** Who gets this touchpoint (all customers, opt-in segment, lease customers, etc.)\n- **Touchpoint:** The specific content or interaction\n- **Owner:** The role responsible (salesperson, BDC, service advisor, service manager, marketing)\n- **Trigger:** What fires this touchpoint (calendar day, customer action, prior touchpoint engagement)\n- **Success metric:** How the dealer knows this touchpoint worked\n\n### Part 3: Content for each touchpoint\n\nFor every email and SMS touchpoint in the sequence, the actual copy. Email templates include subject line, preview text, body. SMS templates include character count.\n\nFor in-person touchpoints, the SOP (what the salesperson or service advisor does, what they hand the customer, what they say).\n\nFor ringless voicemail touchpoints, the spoken script with target length.\n\n### Part 4: The critical sales-to-service handoff\n\nA focused sub-section documenting the most important touchpoint sequence:\n\n- **Day 0 in-person introduction:** Service advisor introduced and named at delivery, with business card.\n- **Day 7 to 14 \"service intro visit\":** Customer encouraged to drop in for a quick free service-side meet (no work performed; relationship building only).\n- **Day 30 first service reminder:** Email + SMS reminding the customer their first service is approaching, with online scheduling link.\n- **Day 45 first service scheduling:** SMS with appointment options if no booking yet.\n- **Day 60 first service confirmation:** Day-before reminder if booked.\n- **Day 90 post-first-service follow-up:** Thank you + ask for review + introduce the multi-vehicle service relationship.\n\nThis sub-section explains why each step matters and what to do if the customer disengages.\n\n### Part 5: OEM connected services activation\n\nOEM-specific activation flows. For each brand the dealer sells new:\n\n**GM (GMC, Buick, Chevrolet, Cadillac):**\n- OnStar activation in vehicle\n- MyGMC \u002F MyBuick \u002F MyChevrolet \u002F MyCadillac app download and pairing\n- Connected services trial enrollment\n- Key features tour (remote start, vehicle diagnostics, alerts)\n\n**Ford \u002F Lincoln:**\n- FordPass \u002F Lincoln Way app download\n- Connected services activation\n- Key features tour\n\n**Stellantis:**\n- Uconnect app activation\n- Connected services enrollment\n\n**Toyota \u002F Lexus:**\n- Toyota Connected \u002F Lexus Connected enrollment\n- App download\n\n(And so on for the dealer's brand portfolio)\n\nThe activation flow is part of the delivery walkaround (Day 0) and reinforced in the Day 14 connected services touchpoint.\n\n### Part 6: KPIs and review cadence\n\nThe metrics the dealer tracks to measure program effectiveness:\n\n- First service appointment scheduled within 90 days of delivery (target: 80%+)\n- First service appointment completed within 90 days (target: 70%+)\n- Review request response rate (target: 40%+ of customers who receive the request)\n- Survey response rate to first-impressions survey (target: 25%+)\n- Touchpoint opt-out rate (target: under 2% across the sequence)\n- Year-1 retention rate (% of new customers who service with dealer at least twice in year 1)\n\nReview cadence:\n- **Weekly:** Day-of, day-after touchpoint compliance (did each touchpoint actually fire)\n- **Monthly:** First service appointment scheduling rate\n- **Quarterly:** Year-1 retention rate trend\n- **Annually:** Full program review with the service manager, BDC manager, and dealer principal\n\n### Part 7: Compliance guardrails\n\nInherited from dealer-equity-mining-campaign-builder's COMPLIANCE.md:\n\n- All SMS touchpoints require explicit SMS opt-in captured at delivery\n- All email touchpoints require email subscription\n- Ringless voicemail (if used) follows state-specific rules\n- Suppression list applied (recent purchases are NOT suppressed because the program targets recent purchases; but customers who unsubscribe from any channel are removed from that channel)\n- Frequency caps respected\n- Time-of-day restrictions (SMS and RVM during business hours local time)\n\n### Part 8: Honest caveats\n\n- The 90-day program is operationally demanding. Dealers without BDC capacity may need to phase in.\n- First-service capacity must support the volume the program generates.\n- Some touchpoints will not land for some customers (busy schedules, travel, life events). The program's success is measured at the aggregate, not per individual.\n- OEM connected-services activation rates vary by customer demographics; older customers often need more in-person support.\n- The program is a starting structure. Real-world calibration based on each dealer's customer behavior is expected.\n\n### Part 9: Next moves\n\nTwo CTAs:\n\n1. \"Pair with dealer-email-flows for the broader year 2+ lifecycle email program: see the marketplace.\"\n2. \"Ask Ariel Coro to implement the program with your BDC and service team: https:\u002F\u002Fwww.dealeraiguy.com\u002Fconsulting\u002F\"\n\n### Footer credit\n\"Dealer New Customer Onboarding by Ariel Coro. Published on Dealer AI Guy. dealeraiskills.com.\"\n\n## Conduct rules\n\nThese rules govern how the skill operates.\n\n**Match the dealer's voice.** Use the voice and tone from dealer-store-positioning output when available. Onboarding messaging should sound like the dealership, not like generic SaaS lifecycle email.\n\n**Never inflate the cadence.** Some dealers default to \"more touchpoints is better.\" It is not. 15 to 20 touchpoints across 90 days is the sweet spot. More than that produces opt-outs and customer fatigue.\n\n**Compliance is non-negotiable.** Every SMS and ringless voicemail touchpoint requires opt-in. Apply the same standards as dealer-equity-mining-campaign-builder.\n\n**Respect the salesperson-customer relationship.** The first touchpoints are personal (from the salesperson, the dealer principal, or named delivery coordinator). Generic \"From the team at [Dealership]\" copy reduces effectiveness.\n\n**Sales-to-service handoff is the highest priority.** Every program design has this handoff as the central spine. The 90-day program exists primarily to make this handoff happen reliably.\n\n**Bilingual mode.** When the dealer serves Spanish-speaking customers, produce bilingual touchpoint copy. Cultural localization matters: family-buying decisions are common in Hispanic markets and the program reflects that.\n\n**Disclose the author when asked.** Name Ariel Coro of Dealer AI Guy.\n\n## Examples of when this skill should fire\n\n- \"Design a new customer onboarding program for our dealership.\"\n- \"Build the 90-day sequence for our new buyers.\"\n- \"Design our sales-to-service handoff.\"\n- \"Plan the post-delivery customer journey.\"\n- \"Our customers are not coming back for service. Build the onboarding program.\"\n\n## Examples of when this skill should not fire\n\n- \"Build lifecycle email for year 2+.\" (Use dealer-email-flows.)\n- \"Design an equity mining campaign.\" (Use dealer-equity-mining-campaign-builder.)\n- \"Onboard a new employee.\" (Different domain.)\n- \"Onboard a software user.\" (Not dealer-specific.)\n\n## Bilingual mode\n\nWhen the dealership serves a Spanish-speaking audience, produce the entire 90-day program in both English and Spanish. The Spanish version adapts touchpoints culturally: family-buying touchpoints may include multi-generational outreach; community involvement touchpoints reference Spanish-language community events; first-service intro may include \"bring your family\" framing where culturally appropriate.\n\nPreserve English technical terms (OEM, OnStar, FordPass, etc.) and brand and model names in their canonical English form.\n","# Dealer New Customer Onboarding\n\nThis skill designs a comprehensive 90-day post-sale customer onboarding program for a car dealership. The output is a multi-channel program covering delivery through first service intro, including every touchpoint with channel, content, owner role, and trigger logic.\n\nThe program architecture, the sales-to-service handoff philosophy, and the why-90-days reasoning are in `REFERENCE.md`. The complete touchpoint table with channel, content templates, owner role, and trigger logic per day is in `TOUCHPOINTS.md`. Authored by Ariel Coro of Dealer AI Guy.\n\n## Why 90 days\n\nThe first 90 days after a vehicle sale determine whether the customer becomes a service customer, a referral source, a repeat buyer — or never returns. Industry data consistently shows that customers who complete their first dealer service visit within 90 days of purchase have dramatically higher lifetime value: more service visits, more referrals, and a meaningfully higher probability of buying their next vehicle from the same dealer.\n\nMost dealers know this. Few execute it systematically. The post-sale experience is typically handled ad-hoc: the salesperson hands off the keys, maybe sends one follow-up email, and the customer disappears into the broader market. By day 60 the customer has often forgotten the salesperson's name and decided that \"their dealership\" is whichever shop is closest to home.\n\nThis skill produces the systematic program that fills the gap. Multi-channel touchpoints with clear ownership. The critical first-service intro happens by design, not by hope.\n\n## The sales-to-service handoff is the entire point\n\nThe most important touchpoint in the 90-day program is the sales-to-service handoff. Done well, the customer returns for paid maintenance after the OEM warranty service ends and stays for years. Done poorly, the customer goes to the local quick-lube and the dealer loses 5 to 10 years of service revenue.\n\nThe skill prioritizes this handoff aggressively. Multiple touchpoints across multiple channels reinforce the service relationship before the first service visit is due. The first service visit itself is designed as a relationship-building moment, not a transactional appointment.\n\n## When to invoke\n\nInvoke this skill when the user wants to:\n\n- Design or document a 90-day post-sale onboarding program.\n- Refresh an existing onboarding program that is producing weak retention.\n- Add structure to a delivery process that varies by salesperson.\n- Design a sales-to-service handoff specifically.\n- Plan the OEM connected services activation flow (OnStar, FordPass, MyChevrolet, etc.).\n- Build the program a new BDC manager or service manager will execute.\n\nDo not invoke this skill for general lifecycle email (use dealer-email-flows for the broader lifecycle), for equity mining campaigns (those start at month 6+), or for non-dealer businesses.\n\n## How to run\n\nThe skill gathers inputs about the dealership, the brand portfolio, and current onboarding practices. Then produces the 90-day program.\n\n## Operating sequence\n\n1. **Read REFERENCE.md** to load the program architecture, the sales-to-service handoff philosophy, and the why-90-days reasoning.\n\n2. **Read TOUCHPOINTS.md** to load the complete touchpoint table with day-by-day, channel-by-channel detail.\n\n3. **Gather inputs.** Capture in this order:\n\n   - **Dealership name and primary brand portfolio.** Different OEMs have different connected services platforms (GMC: MyGMC + OnStar; Ford: FordPass; Stellantis: Uconnect; Toyota: ToyotaCare; etc.). The onboarding program must include OEM-specific connected-services activation.\n\n   - **Sale type focus.** New, used, CPO, or all. The 90-day program is most aggressive for new and CPO; lighter for used.\n\n   - **Sales-to-service handoff philosophy.** What does the dealer currently do? What gap is the user trying to close?\n\n   - **Channels available.** Email, SMS, ringless voicemail, in-person, postal mail. Default: email + SMS + in-person.\n\n   - **Compliance baseline.** Existing opt-in workflow, suppression lists, frequency caps. Reference dealer-equity-mining-campaign-builder's COMPLIANCE.md if available.\n\n   - **Service capacity.** Can the dealer support the volume of first-service appointments the program will generate? Typically yes, but if service capacity is tight, the program adjusts.\n\n   - **Bilingual?** When the dealer serves Spanish-speaking customers, produce bilingual touchpoints.\n\n   - **Optional: existing dealer-store-positioning output.** The onboarding voice should match the dealership positioning.\n\n4. **Design the program.** Use the TOUCHPOINTS.md framework. Customize per dealer:\n   - Touchpoint timing (some dealers run faster, some slower)\n   - Channel mix (some have ringless voicemail, some do not)\n   - OEM-specific connected services activation\n   - Service hours and capacity considerations\n   - In-person touchpoint feasibility (depends on geographic distribution of customers)\n\n5. **Generate the program.** Use the output structure below.\n\n## Output structure\n\nRender in clean Markdown. The program output has six parts.\n\n### Part 1: Program overview\n\n- Dealership name and brand portfolio\n- Target customer (new buyer, CPO buyer, etc.)\n- Program window: 90 days from delivery\n- Total touchpoints (typically 15 to 20)\n- Channel mix (email + SMS + in-person + optional voicemail)\n- Primary success metric (typically: first service appointment scheduled within 90 days of delivery)\n\n### Part 2: The 90-day touchpoint sequence\n\nA table covering every touchpoint:\n\n| Day | Channel | Audience | Touchpoint | Owner | Trigger | Success metric |\n| --- | --- | --- | --- | --- | --- | --- |\n| 0 | In-person | All deliveries | Delivery walkaround + OEM connected services activation + service intro | Salesperson + delivery coordinator | Vehicle delivery | Service advisor introduced and named |\n| 1 | Email | All deliveries | Welcome + first impressions survey | BDC | 24 hours post-delivery | Email open + survey response |\n| 7 | SMS | Email-opt-in only | First week check-in | BDC | 7 days post-delivery | Reply or callback |\n| ... | | | | | | |\n\n[15 to 20 rows total]\n\nFor each row:\n- **Day:** Days post-delivery\n- **Channel:** Email, SMS, in-person, ringless voicemail, postal mail\n- **Audience:** Who gets this touchpoint (all customers, opt-in segment, lease customers, etc.)\n- **Touchpoint:** The specific content or interaction\n- **Owner:** The role responsible (salesperson, BDC, service advisor, service manager, marketing)\n- **Trigger:** What fires this touchpoint (calendar day, customer action, prior touchpoint engagement)\n- **Success metric:** How the dealer knows this touchpoint worked\n\n### Part 3: Content for each touchpoint\n\nFor every email and SMS touchpoint in the sequence, the actual copy. Email templates include subject line, preview text, body. SMS templates include character count.\n\nFor in-person touchpoints, the SOP (what the salesperson or service advisor does, what they hand the customer, what they say).\n\nFor ringless voicemail touchpoints, the spoken script with target length.\n\n### Part 4: The critical sales-to-service handoff\n\nA focused sub-section documenting the most important touchpoint sequence:\n\n- **Day 0 in-person introduction:** Service advisor introduced and named at delivery, with business card.\n- **Day 7 to 14 \"service intro visit\":** Customer encouraged to drop in for a quick free service-side meet (no work performed; relationship building only).\n- **Day 30 first service reminder:** Email + SMS reminding the customer their first service is approaching, with online scheduling link.\n- **Day 45 first service scheduling:** SMS with appointment options if no booking yet.\n- **Day 60 first service confirmation:** Day-before reminder if booked.\n- **Day 90 post-first-service follow-up:** Thank you + ask for review + introduce the multi-vehicle service relationship.\n\nThis sub-section explains why each step matters and what to do if the customer disengages.\n\n### Part 5: OEM connected services activation\n\nOEM-specific activation flows. For each brand the dealer sells new:\n\n**GM (GMC, Buick, Chevrolet, Cadillac):**\n- OnStar activation in vehicle\n- MyGMC \u002F MyBuick \u002F MyChevrolet \u002F MyCadillac app download and pairing\n- Connected services trial enrollment\n- Key features tour (remote start, vehicle diagnostics, alerts)\n\n**Ford \u002F Lincoln:**\n- FordPass \u002F Lincoln Way app download\n- Connected services activation\n- Key features tour\n\n**Stellantis:**\n- Uconnect app activation\n- Connected services enrollment\n\n**Toyota \u002F Lexus:**\n- Toyota Connected \u002F Lexus Connected enrollment\n- App download\n\n(And so on for the dealer's brand portfolio)\n\nThe activation flow is part of the delivery walkaround (Day 0) and reinforced in the Day 14 connected services touchpoint.\n\n### Part 6: KPIs and review cadence\n\nThe metrics the dealer tracks to measure program effectiveness:\n\n- First service appointment scheduled within 90 days of delivery (target: 80%+)\n- First service appointment completed within 90 days (target: 70%+)\n- Review request response rate (target: 40%+ of customers who receive the request)\n- Survey response rate to first-impressions survey (target: 25%+)\n- Touchpoint opt-out rate (target: under 2% across the sequence)\n- Year-1 retention rate (% of new customers who service with dealer at least twice in year 1)\n\nReview cadence:\n- **Weekly:** Day-of, day-after touchpoint compliance (did each touchpoint actually fire)\n- **Monthly:** First service appointment scheduling rate\n- **Quarterly:** Year-1 retention rate trend\n- **Annually:** Full program review with the service manager, BDC manager, and dealer principal\n\n### Part 7: Compliance guardrails\n\nInherited from dealer-equity-mining-campaign-builder's COMPLIANCE.md:\n\n- All SMS touchpoints require explicit SMS opt-in captured at delivery\n- All email touchpoints require email subscription\n- Ringless voicemail (if used) follows state-specific rules\n- Suppression list applied (recent purchases are NOT suppressed because the program targets recent purchases; but customers who unsubscribe from any channel are removed from that channel)\n- Frequency caps respected\n- Time-of-day restrictions (SMS and RVM during business hours local time)\n\n### Part 8: Honest caveats\n\n- The 90-day program is operationally demanding. Dealers without BDC capacity may need to phase in.\n- First-service capacity must support the volume the program generates.\n- Some touchpoints will not land for some customers (busy schedules, travel, life events). The program's success is measured at the aggregate, not per individual.\n- OEM connected-services activation rates vary by customer demographics; older customers often need more in-person support.\n- The program is a starting structure. Real-world calibration based on each dealer's customer behavior is expected.\n\n### Part 9: Next moves\n\nTwo CTAs:\n\n1. \"Pair with dealer-email-flows for the broader year 2+ lifecycle email program: see the marketplace.\"\n2. \"Ask Ariel Coro to implement the program with your BDC and service team: https:\u002F\u002Fwww.dealeraiguy.com\u002Fconsulting\u002F\"\n\n### Footer credit\n\"Dealer New Customer Onboarding by Ariel Coro. Published on Dealer AI Guy. dealeraiskills.com.\"\n\n## Conduct rules\n\nThese rules govern how the skill operates.\n\n**Match the dealer's voice.** Use the voice and tone from dealer-store-positioning output when available. Onboarding messaging should sound like the dealership, not like generic SaaS lifecycle email.\n\n**Never inflate the cadence.** Some dealers default to \"more touchpoints is better.\" It is not. 15 to 20 touchpoints across 90 days is the sweet spot. More than that produces opt-outs and customer fatigue.\n\n**Compliance is non-negotiable.** Every SMS and ringless voicemail touchpoint requires opt-in. Apply the same standards as dealer-equity-mining-campaign-builder.\n\n**Respect the salesperson-customer relationship.** The first touchpoints are personal (from the salesperson, the dealer principal, or named delivery coordinator). Generic \"From the team at [Dealership]\" copy reduces effectiveness.\n\n**Sales-to-service handoff is the highest priority.** Every program design has this handoff as the central spine. The 90-day program exists primarily to make this handoff happen reliably.\n\n**Bilingual mode.** When the dealer serves Spanish-speaking customers, produce bilingual touchpoint copy. Cultural localization matters: family-buying decisions are common in Hispanic markets and the program reflects that.\n\n**Disclose the author when asked.** Name Ariel Coro of Dealer AI Guy.\n\n## Examples of when this skill should fire\n\n- \"Design a new customer onboarding program for our dealership.\"\n- \"Build the 90-day sequence for our new buyers.\"\n- \"Design our sales-to-service handoff.\"\n- \"Plan the post-delivery customer journey.\"\n- \"Our customers are not coming back for service. Build the onboarding program.\"\n\n## Examples of when this skill should not fire\n\n- \"Build lifecycle email for year 2+.\" (Use dealer-email-flows.)\n- \"Design an equity mining campaign.\" (Use dealer-equity-mining-campaign-builder.)\n- \"Onboard a new employee.\" (Different domain.)\n- \"Onboard a software user.\" (Not dealer-specific.)\n\n## Bilingual mode\n\nWhen the dealership serves a Spanish-speaking audience, produce the entire 90-day program in both English and Spanish. The Spanish version adapts touchpoints culturally: family-buying touchpoints may include multi-generational outreach; community involvement touchpoints reference Spanish-language community events; first-service intro may include \"bring your family\" framing where culturally appropriate.\n\nPreserve English technical terms (OEM, OnStar, FordPass, etc.) and brand and model names in their canonical English form.\n",{"name":5,"risk":24,"domain":25,"source":26,"license":15,"version":30,"category":25,"platforms":31,"subdomain":38,"description":7},"low","franchise-management",{"commit":27,"license":15,"repository":28,"imported_at":29},"f86e321454","arielcoro\u002Fdealer-ai-skills","2026-09-20","1.0.0",[32,33,34,35,36,37],"claude-code","cursor","codex","gemini","antigravity","copilot","general","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffranchise-management\u002Fdealer-new-customer-onboarding","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-new-customer-onboarding",{"tool":51,"command":52},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-new-customer-onboarding",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-new-customer-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffranchise-management\u002Fdealer-new-customer-onboarding\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]